Skill Authoring

A skill is a workflow contract, not a knowledge dump. If you cannot define the outcome, evidence, and authorization boundary before writing step one, you are documenting a vague intention, not authoring a skill.

Outcome Contract

• Outcome: A valid, portable, and trigger-ready SKILL.md file that passes all quality gates.
• Done when: The file exists at skills/<name>/SKILL.md, frontmatter validates against length/trigger/exclusion rules, no cross-skill file references exist, and no portability red lines are violated.
• Evidence: File content inspection; frontmatter character count; grep for forbidden patterns (skills/*/SKILL.md, /Users/, bare bash repo-relative invocations).
• Output: A single SKILL.md file plus optional scripts/ or references/ directories only when justified.
• Authorization: Drafting and structuring only. Do not execute scripts, install dependencies, or modify project code unless the current turn explicitly asks to test the new skill.

Mode Picker