Verification before completion
Skill Tsurai7/agentic-playbook/skills/verification-before-completion
Require evidence before claiming work is complete, fixed, or tests pass. Use before commits, PRs, or any "done", "fixed", "works now", "should work", or "tests pass" statement.From its SKILL.md
npx -y skills add Tsurai7/agentic-playbook --skill verification-before-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 256 tokens by cl100k_base, as published. Nobody here has run it
Verification before completion
No assertions without fresh verification evidence.
Gate
Do not claim completion until you have run the relevant check and seen successful output in this session.
Required evidence
| Claim | Minimum evidence |
|---|---|
| Tests pass | Test command output showing pass |
| Build succeeds | Build command exit 0 + output |
| Bug fixed | Reproduction steps pass after fix |
| Lint clean | Linter output on changed files showing zero errors |
Process
- Identify the command that proves the claim
- Run it (fix failures; do not lower the bar)
- Read output — confirm success, not absence of errors
- Only then state completion
Red flags — stop and verify
- Using "should", "probably", "seems to"
- Reporting success before running the command
- Trusting a prior run after code changed
- "I'm confident" without command output
Short form
CLAIM: [what you want to assert]
EVIDENCE: [command just run]
OUTPUT: [relevant success lines]
VERDICT: [claim supported only if output matches]
Keep this gate for every "done" statement.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.