Individual skill
verification-before-completion
Assess nontrivial completion evidence.
skills/verification-before-completion/SKILL.md
Source commit 9922fa0af0aea32443cf7365ef5024dc7797382d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 137
- Repository last updated
- Oct 22, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- codex Repository topic
- codex-skills Repository topic
- frontend Repository topic
- motion Repository topic
- nextjs Repository topic
- react Repository topic
- tailwind Repository topic
- web-design Repository topic
- agent-skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,695 bytesSKILL.mdcore · 2,695 bytesagents/openai.yamlasset · 262 bytes
Read excerpt
# Verification Before Completion
## Core principle
Evidence before claims. Verification should be fresh, decisive, and proportionate to the result being asserted. For an obvious low-impact local edit, apply the direct check without loading this skill or creating a formal verification artifact. Use this fuller workflow when the evidence choice, failure interpretation or completion boundary is nontrivial, or when explicitly invoked.
## Lightweight gate
Before claiming that work is complete, fixed, passing, deployed, sent, published, or otherwise in a verified state:
1. Name the exact claim and its consequence.
2. Choose the smallest fresh check that can actually prove it.
3. Run the check and read the exit status, failures, and material output.
4. Report the result with exact coverage and anything not verified.