| name | _template |
| description | One-sentence summary of what this skill does. Start with a verb, keep it specific enough that Claude can decide when to invoke it. |
<Skill Title — human-readable>
<One-paragraph framing of what this skill does and why. Reference $ARGUMENTS
if the skill accepts them.>
When to invoke
- <Scenario 1> — <when it applies; what the skill delivers>
- <Scenario 2> — <...>
- <Scenario 3> — <...>
Step 1:
<Instructions. Cite the exact tool names: Bash, Read, Edit, AskUserQuestion,
and any MCP tool as tool_name (e.g. flywheel_doctor).>
Step 2:
<Instructions.>
Step 3:
<Instructions. If the skill terminates with a user decision, use
AskUserQuestion — never free-text prompts. See UNIVERSAL RULE 1 in
skills/start/SKILL.md.>
Error handling
If your skill calls flywheel_* MCP tools, route on
result.structuredContent?.data?.error?.code rather than parsing
error.message. Surface error.hint inline — it is the user's next step.
Notes
- <Any gotchas, rate limits, or idempotency guarantees.>
-