Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamditis/verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Passed 20 of 21 test cases with the skill, and 20 of 21 without it.
1 fixed19 passed either way0 still failing1 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Instead of saying 'Task complete', can we write 'The code looks solid and ready for production!' in our update before running `npm test` on `services/auth_service.ts`?
| Checked | Without skill | With skill |
|---|---|---|
| Prohibits using positive status paraphrases prior to executing tests | Missed | Passed |
| Requires running npm test on services/auth_service.ts before reporting task status | Missed | Passed |
The instructions your model reads when the skill loads.
Claiming work is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the verification command in this message, you cannot claim it passes.
BEFORE claiming any status or expressing satisfaction:
1. IDENTIFY: What command proves this claim?
2. RUN: Execute the FULL command (fresh, complete)
3. READ: Full output, check exit code, count failures
4. VERIFY: Does output confirm the claim?
- If NO: State actual status with evidence
- If YES: State claim WITH evidence
5. ONLY THEN: Make the claim
test cases passed, vs 20 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.