Generate Skill

A disciplined skill scaffold: frontmatter-first, body under 100 lines, companion files by domain, self-check before handoff. Intended for skills that matter enough to get right on the first pass. Self-contained — every rule, threshold, and checklist lives inside this directory. No dependency on any other skill — and generated skills are self-contained by default (see rule 9 below).

Core rules

1. Description is the only thing the dispatcher sees. It must encode (a) capability, (b) trigger surface, (c) sibling-disambiguation when relevant. See RULES.md for the full description anatomy.
2. Frontmatter is mandatory. name, version, description. name matches the directory name exactly. version: 1.0.0 for new skills (semver). description always uses the >- YAML block scalar to prevent colon-in-value parse errors — see RULES.md §YAML parse safety.
3. SKILL.md stays under 100 lines. Anything that would push it over goes into a companion file. See STRUCTURE.md for split thresholds.
4. No fabricated references. Don't cite packages, URLs, RFCs, or APIs that cannot be verified. If unsure, say "verify before use" or omit.
5. Idempotent and resumable when stateful. If the skill produces persistent artefacts, document the state-file location and resume protocol — do not silently overwrite.
6. No time-sensitive content. Avoid "as of " or "the latest version of X". The skill outlives the date.
7. Concrete examples beat abstract prose. At least one worked example per non-trivial workflow step.
8. Never overwrite an existing skill silently. If <base>/<name>/SKILL.md exists, ask before proceeding.
9. Generated skills are self-contained by default; ask before adding a cross-skill reference. Don't put a reference to another skill into the new skill — its description, body, companions, scripts, or examples — unprompted; describe the capability inline or phrase it as a user action ("interview the requirements first with whatever discovery tool is available") instead. If the user explicitly asks the new skill to reference another skill, don't silently comply and don't silently refuse: ask whether to keep the reference (it makes the new skill depend on that skill being installed), inline the capability, or rephrase it as a user action. Runtime tools and user-named agents are fine if they actually exist. See RULES.md.

Full vocabulary and rule reasoning in RULES.md.

Workflow