Build a Verification Skill So Claude Checks Its Own Work — Transcript

Full transcript

1. 0:02As your project continues to grow and grow, you want to automate the work that's constantly repeated.
2. 0:06You already know that skills are great for this, but here are some tips on how you can use skills to help you verify your work.
3. 0:14So this example is the skill that's worth building first.
4. 0:17Ask Claw to refactor something and when it finishes, the description matches, task that edited code and the skill fires.
5. 0:22It runs a suite, reads a diff, checks that no test has weakened to pass, and reports pass or fail with the evidence attached.
6. 0:29Checking the work no longer depends on you remembering to ask for it.
7. 0:34The same shape carries any procedure your team repeats, a release checklist or a migration recipe.
8. 0:39If you've typed the same multi-step instruction twice, well, that's a skill.
9. 0:44Now a skill folder can hold more than just a skill.md file.
10. 0:48Drop a reference.md beside it for detailed material and link it from that skill.
11. 0:53Cloud reads it only when it needs the depth.
12. 0:55Cloud executes scripts in the folder rather than loading them.
13. 0:58So a skill can carry its own tooling.
14. 1:00So keep your skill.md file itself lean and push the heavy material into those side files.
15. 1:06So a quick way to keep the three instruction surfaces straight, conventions that apply all the time go into your Cloud.md file and procedures or reference materials tied to a kind of task go into a skill.
16. 1:17A rule Cloud must not be able to skip belongs in a hook because Cloud.md and skills are both instructions that Cloud follows rather than code that runs.
17. 1:27A skill is a folder with a skill.md, a name, a description that triggers it, and the procedure itself.
18. 1:33Only descriptions load until a skill is needed, so package every procedure you repeat.
19. 1:38Start with verification and check it into the Claude skills, and your team inherits the same move.