Verification skill
A verification skill is a guide made for your project. It teaches the AI to start your app and use it the way a user would.
An analogy
Like an onboarding guide for a new tester: how to start it, which account, where to click, what to screenshot. Once it exists, anyone can test.
In pstack
Generate it with /pstack:create-verification-skill. It mostly reads your code to learn how the app starts and how to drive it. Before handing it over, it does a full run itself. The files go in your project: .cursor/skills/verify-<app-name>/ in Cursor, .claude/skills/verify-<app-name>/ in Claude Code. From then on you can say "verify with /verify-<app-name> and give me screenshots".
The author says this is the highest-payoff thing in the whole guide. An AI that can check its own work keeps going until the check passes. One that can't hands every result back to you. When /pstack:setup-pstack asks at the end whether to generate one, say yes.
Common misconceptions
- "Generate it once and you're set": apps change, and the guide goes stale. Run
/pstack:maintain-verification-skillregularly, ideally daily. It only fixes the verification skill and never touches product code. - "My project is too small for this": the sooner the better. With it, checking isn't your job anymore; any AI can do it.
Try it: Full guide step 6: Verify and ship, Give your project a verification skill, so the AI checks its own work
Related: Evidence (not "should be fixed"), Formal verification