write-a-skilllisted

> Source: [mattpocock/skills — productivity/write-a-skill](https://github.com/mattpocock/skills/tree/main/skills/productivity/write-a-skill) # Writing Skills ## Process **why-not-mechanizable:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). 1. **Gather requirements** - ask user about: `(review-time: see section note)` - What task/domain does the skill cover? `(review-time: see section note)` - What specific use cases should it handle? `(review-time: see section note)` - Does it need executable scripts or just instructions? `(review-time: see section note)` - Any reference materials to include? `(review-time: see section note)` 2. **Draft the skill** - create: `(review-time: see section note)` - SKILL.md with concise instructions `(review-time: see section note)` - Additional reference files if content exceeds 500 lines `(review-time: see section note)` - Utility scripts if deterministic operations needed `(review-time: see section note)` 3. **Review with user** - present draft and ask: `(review-time: see section note)` - Does this cover your use cases? `(review-time: see section note)` - Anything missing or unclear? `(review-time: see section note)` - Should any section be more/less detailed? `(review-time: see section note)` ## Skill Structure ```text skill-name/ ├── SKILL.md # Main instructions (required) ├── REFERENCE.md # Detailed docs (if needed) ├──