verify-this
From the author
Use when a measurable claim needs before/after proof. Not for fact-checking or done-claim gating: use verify-both-ways or verification-before-completion.
Install
npx skills add OutlineDriven/outline-driven-development --skill verify-this -a claude-code
Installs to .claude/skills/verify-this/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
Security100
Provenance61
Maintenance100
Licence100
Adoption31
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- verificationa5c-ai/babysitterVerification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.Testing★ 1.9K
- verification-before-completionmvschwarz/openrigUse when about to claim work is complete, fixed, or passing, or before committing or creating PRsOther★ 8.2K
- verify-before-claimMark393295827/third-brain-v7-skillsUse when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.DevOps★ 141
- verifycodeaholicguy/ai-devkitAI DevKit · Enforce evidence-based completion claims — require fresh command output before reporting success. Use when completing any task, fixing a bug, finishing a phase, running tests, building, deploying, or making any "it works" claim.Testing★ 1.7K
- verifying-results-before-claimingK-Dense-AI/science-superpowersUse when about to claim a result, effect, significance, or that an analysis reproduces, before reporting or writing it up - requires running the analysis fresh and reading the actual output first; evidence before claims alwaysWriting★ 362
- completion-verificationcbrock84/headcountVerifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.Engineering★ 2.1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in