Skill name

• What it does: one line
• When to use it: one line, including when to re-run it
• Dependencies: other skills, CLIs, MCP servers, config fields it reads. "none" is a fine answer.
• How to call it: Claude Code /skill-name, Codex $skill-name, Kiro CLI /skill-name.
• Input: what the user or the calling skill supplies
• Output: files written, tracker state changed, what the next skill can expect

One line of standing behaviour that applies to every step, when the skill has any. setup uses "Idempotent: safe to re-run; never overwrite existing files without asking." Delete this paragraph when it does not.

1. First step

Numbered sections in the order the skill runs, one job each. Say what to read before deciding anything, so the skill does not guess.

2. Next step