Skill Claude CodeCodex
A bare-minimum Logion course example. Use as a starting template when authoring a new skill that needs no tools, no network, no filesystem writes, and no env vars. Demonstrates the smallest valid SKILL.md plus capabilities.yaml pairing.
Skill Claude CodeCodex
Reviews code diffs against a structured checklist covering security (sql-injection, hardcoded-secret, unvalidated-input), reliability (missing-error-handling, resource-leak), and correctness (off-by-one, wrong-comparison). Use when reviewing PRs, audit diffs, or any code change where you want a categorised…
Skill Claude CodeCodex needs its repo
Paid-course example showing how to package a self-contained Logion bundle with the marketplace paid license. Use as a starting point when you want a benign course that reads local artifacts, produces a structured report, and exercises the paid publication path end to end.
Skill Claude CodeCodex
Logion course example that bundles a runnable script and a reference doc. Use as a starting template when your skill executes a small subprocess (terminal tool) and produces output files. Demonstrates progressive disclosure across SKILL.md, references/, and scripts/.
Skill Claude CodeCodex
Bundled Gmail CLI example demonstrating the scripts/ entrypoint + src/ implementation split. Use as a template when your course ships real code that goes beyond a single shell script. Shows how to organize a course bundle that owns its codebase — no runtime package installation, all dependencies stdlib-only. Replaces…
Skill Claude CodeCodex
Compact bootstrap skill for recall-first Logion discovery, inspection, install, update, and creator-course-management routing without loading the whole marketplace.
Skill Claude CodeCodex
Compact bootstrap skill for recall-first Logion discovery, inspection, install, update, and creator-course-management routing without loading the whole marketplace.
Skill Claude CodeCodex
Turn a requirement into machine-checkable policy for the software factory — gates, activation paths, required assertions, and new catalog rules. Use when starting a phase of work that needs a completion gate, when a convention keeps being re-explained in review, or when someone asks "how do we stop this from happening…
Skill Claude CodeCodex
Create or run the proof behind a software-factory L3 gate and seal evidence that survives re-verification. Use when a feature needs its first gate, when a gate is red for missing or stale evidence, or when asked to prove a change actually works end to end.
Skill Claude CodeCodex
Interview someone about their project's architecture and stack, then generate the software-factory rules those answers imply. Use when setting up sf in a repository for the first time, when someone asks what rules their project should have, or when an architectural decision changes and the policy should follow it.
Skill Claude CodeCodex
Read a software-factory report, explain what actually broke, and fix it. Use when sf check or sf verify is red, when CI fails on a factory rule, or when someone asks whether a rule is worth keeping.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: