Verification before completion
Skill kimtth/agent-skill-100-lines-or-less/skills/verification-before-completion
Use when: about to claim work is complete, fixed, passing, or ready for commit or PR.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill verification-before-completionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 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.1 KB, 212 tokens by cl100k_base, as published. Nobody here has run it
Goal: make completion claims only after fresh evidence.
Gate:
- Identify the exact claim being made.
- Choose the command or inspection that proves it.
- Run the full check now, not from memory.
- Read output and exit code.
- State the result with evidence or report the actual failure.
Examples:
- tests pass: test command exits 0 with failure count checked
- build succeeds: build command exits 0
- bug fixed: original symptom is reproduced as passing
- lint clean: linter output has no errors
- requirements met: checklist is matched against the request
Red flags:
- "should pass"
- "looks good"
- "probably fixed"
- claiming success after partial output
- relying on an earlier run after new edits
Output:
- command run
- result
- evidence summary
- residual risk or skipped checks
Rules:
- no completion claim without current verification
- do not summarize success before reading output
- if verification cannot run, say why and what risk remains
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.