write-new-skill

# Writing Skills ## Process 1. **Gather requirements** - ask user about: - What task/domain does the skill cover? - What specific use cases should it handle? - Does it need executable scripts or just instructions? - Any reference materials to include? 2. **Draft the skill** - create: - SKILL.md with concise instructions - Additional reference files if content exceeds 100 lines - Utility scripts if deterministic operations needed 3. **Review with user** - present draft and ask: - Does this cover your use cases? - Anything missing or unclear? - Should any section be more/less detailed? ## Skill Structure ``` skill-name/ ├── SKILL.md # Main instructions (required) ├── REFERENCE.md # Detailed docs (if needed) └── scripts/ # Utility scripts (if needed) ``` ## SKILL.md Template Frontmatter fields: `name`, `description`, `allowed-tools`. Body: opening directive, optional live state injection, instructions, output template. Optional sections: `## Anti-Rationalization` (3–5 skill-specific rows: an excuse an agent uses to skip a key step, paired with a factual rebuttal — never generic filler) and `## Verification` (exit-criteria checklist requiring observable evidence before claiming done). ## Shell injection To inject live state before Claude sees the skill, open a fenced code block with three backticks immediately followed by `!` (no space). The command output replaces the block at skill load time. Always add `|| echo...