prove-it
Skill0 starsChanged 51 days agoMITView on GitHub
Use when someone claims a change works and you need to exercise the real behavior, then finish with PASS, FAIL, or PARTIAL and the evidence — not a code-reading summary.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- peaknr35/shark-Tank-prooftheir own version, first seen Nov 15, 2026
- dundas/thinkruntheir own version, first seen Nov 9, 2026
- ryanda9910/prove-ittheir own version, first seen Nov 8, 2026
- decebal/chief-of-staff-v2their own version, first seen Nov 8, 2026
- SaudSatopay/bullseyetheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use root-cause, grill and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Ingramradical235Skillroot-cause
Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.
Also in 3 projects that use this
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
GoogleSkilltdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Also in 3 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- nagi-studio/skills★ 470same name
- AlemTuzlak/skills★ 45same name
- Neko-Catpital-Labs/Invoker★ 21same name
- anotherben/claude-harness★ 7same name
- nadirali1350/vetted★ 5same name
- Xnadir/vetted★ 5same name
- SaudSatopay/bullseye★ 4same name
- peaknr35/shark-Tank-proof★ 3same name
- drewdrewthis/claude-skills★ 2same name
- dundas/thinkrun★ 2same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Do not rely only on reading the code or saying it looks correct.
- Distinctive: line 12
Test the real behavior.
- Distinctive: line 16
Use the actual application or executable path when practical.
- Distinctive: line 17
Run relevant existing tests first when they help.
- Distinctive: line 19
Prefer the same path a real user would take.
- Distinctive: line 21
Keep the verification focused on the work that changed.
- Distinctive: line 22
If something fails, say exactly what failed.
- Distinctive: line 23
Do not quietly work around failures just to produce a passing result.
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Prove It
Prove that the thing you just built or changed actually works.
Do not rely only on reading the code or saying it looks correct.
Test the real behavior.
Verify
- Use the actual application or executable path when practical.
- Run relevant existing tests first when they help.
- Exercise the specific feature or change that was just made.
- Prefer the same path a real user would take.
- Capture clear evidence such as output, test results, screenshots, responses, or application state.
- Keep the verification focused on the work that changed.
- If something fails, say exactly what failed.
- Do not quietly work around failures just to produce a passing result.
Core Rule
Don't tell me it works. Prove it.
Finish with a concise result:
PASS — the requested behavior was verified and the evidence.
FAIL — the behavior failed and the evidence.
PARTIAL — some behavior was verified, but clearly state what remains unverified.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

