| name | skill-name |
| description | Brief description of when to use this skill |
[Skill name]
Overview
[What this skill does and when to use it. Commands and agents should reference this skill directly.]
Context
[Prerequisites, user input expected, and how context will be provided.
Keep this delivery-agnostic: describe what inputs the skill needs (files, parameters), not where they come from. The app layer (CLI, web UI, API) handles how files arrive — the skill should work with whatever file paths are provided.]
Sub-skills
[Optional - only for parent skills that have sub-skills]
CRITICAL: You MUST load the appropriate sub-skill from the sub-skills/ directory when routing is needed.
- [sub-skill-1.md]: [When to use this sub-skill]
- [sub-skill-2.md]: [When to use this sub-skill]
Process
- [Step 1]
- [Step 2]
- [Step 3]
- Verification: [Confirm expected outcome was achieved]
Resources
[Optional - if skill has supporting files. These are read on demand, not loaded with the skill.]
- sub-skills/: [Sub-skill files for specific operations or workflow patterns]
- references/: [Condensed reference docs and/or upstream documentation directories]
- templates/: [Template files for generating output]
- scripts/: [Executable scripts]
Guidelines
[Principles to follow when executing this skill]
- [Guideline 1]
- [Guideline 2]
- [Guideline 3]
Appendix
[Optional - for domain-specific information that doesn't fit above]
[Use this section for additional detailed information such as architecture patterns, naming conventions, integration patterns, or reference commands.]