| name | add-skill |
| description | Scaffold a new skill in THIS repo — correct folder, valid frontmatter, README row, credits, and validation. (For the authoring craft, use the global skill-creator.) |
| disable-model-invocation | true |
Add a skill to this repo
Place a new skill so it satisfies the repo's invariants and installs cleanly. This handles
placement and bookkeeping.
Steps
-
Choose the location (grouping below the domain is for humans; only the leaf matters):
- Atomic skill →
<domain>/<group>/<name>/ (e.g. software-development/review/<name>/).
- Playbook composing atomic skills →
workflows/<name>/.
- Domain-agnostic →
meta/<name>/.
- A brand-new top-level domain must be added to
install.conf or it
won't install (default-deny).
-
Pick a kebab-case leaf name unique across the entire repo (all domains, all depths) —
the installer flattens leaves into one dir. The step-6 validator enforces this.
-
Create <location>/<name>/SKILL.md from docs/skill-template.md:
name: must equal the folder name exactly.description: is the trigger — lead with WHAT it does, then Use when … with concrete
cues.
-
If adapted from another source: add a row to CREDITS.md, and if the
license requires attribution (MIT/BSD/Apache) keep a license: line in the frontmatter.
-
Add a one-line row to the area's README.md table (software-development/, workflows/,
or meta/). Keep it thin.
-
Validate, then preview the install:
./scripts/validate-skills.sh
./install.sh --dry-run
