Video: Verification Skills
1. Video: Verification Skills
As your project continues to grow and grow, you want to automate the work that's constantly repeated. You 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. So this example is the skill that's worth building first. Ask Claude to refactor something, and when it finishes, the description matches, task that edited code, and the skill fires. It runs the suite, reads the diff, checks that no test has weakened to pass, and reports pass or fail with the evidence attached. Checking the work no longer depends on you remembering to ask for it. The same shape carries any procedure your team repeats. A release checklist or a migration recipe. If you've typed the same multi-step instruction twice, well, that's a skill. Now a skill folder can hold more than just a SKILL.md file. Drop a reference.md beside it for detailed material and link it from that skill. Claude reads it only when it needs the depth. Claude executes scripts in the folder rather than loading them, so a skill can carry its own tooling. So keep your SKILL.md file itself lean and push the heavy material into those side files. So a quick way to keep the three instruction surfaces straight, conventions that apply all the time go into your CLAUDE.md file, and procedures or reference materials tied to a kind of task go into a skill. A rule Claude must not be able to skip belongs in a hook because CLAUDE.md and skills are both instructions that Claude follows rather than code that runs. A skill is a folder with a SKILL.md, a name, a description that triggers it, and the procedure itself. Only descriptions load until a skill is needed, so package every procedure you repeat. Start with verification and check it into the Claude skills, and your team inherits the same move.2. Let's practice!
Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.