skill-creatorlisted

## When to Create a Skill Create a skill when: - A pattern is used repeatedly and AI needs guidance - Project-specific conventions differ from generic best practices - Complex workflows need step-by-step instructions - Decision trees help AI choose the right approach **Don't create a skill when:** - Documentation already exists (create a reference instead) - Pattern is trivial or self-explanatory - It's a one-off task --- ## Skill Structure Choose `{skill-root}` as `domains/{domain}/skills` for one owner or `skills` for multiple owners. ``` {skill-root}/{skill-name}/ ├── SKILL.md # Required - main skill file ├── assets/ # Optional - generated templates, schemas, fixtures, examples │ ├── template.py │ └── schema.json └── references/ # Optional - longer guidance, edge cases, explanatory docs └── guidance.md ``` --- ## SKILL.md Template ```markdown --- name: {skill-name} description: > {One-line description of what this skill does}. Trigger: {When the AI should load this skill}. license: Apache-2.0 metadata: author: {author} version: "1.0.0" status: backlog --- ## When to Use {Bullet points of when to use this skill} ## Critical Patterns {The most important rules - what AI MUST know} ## Code Examples {Minimal, focused examples} ## Commands ```bash {Common commands} ``` ## Resources - **Templates**: See [assets/](assets/) for {description} - **Documentation**: See [references/](references/) for local docs `