Exercise: Debug a broken Skill
Time: 15–20 minutes
In this exercise you'll apply the systematic troubleshooting approach from the previous lesson to diagnose and fix a real broken skill. Work with an existing skill of your own, or deliberately break one (vague description, SKILL.md at the wrong level, missing directory) and fix it step by step.
Step 1—Run the Validator
Install the skills validator via uv if you don't already have it, then run it against one of your skills. If the skill passes clean, create a deliberately broken version — for example, remove the description field or move SKILL.md out of its directory — and run the validator again to see what it catches.
Paste the output below and note the issues.
Run the skills validator on your skill. Paste the output below. What issues (if any) did it find?
You now have a repeatable debugging process for any skill issue — validator first, then description, structure, and runtime checks in order.