claim-check
Skill2 starsChanged 6 days agoMITView on GitHub
Use before telling the user that work is done, fixed, deployed or passing, or that something does not exist or is not used. Requires proof from this turn, or an honest "not verified".
11 other projects use a version of this.
Adopted by
Most recently taken up by
- mbalazy/claude-skillstheir own version, first seen Nov 16, 2026
- adithyanraj03/dsh-skills-packtheir own version, first seen Nov 15, 2026
- Job-Yang/jobbyang-ai-skillstheir own version, first seen Nov 8, 2026
- Job-Yang/jobyang-ai-skillstheir own version, first seen Nov 8, 2026
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- duu261/agent-skillstheir own version, first seen Oct 25, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- RyanAlberts/best-of-Agent-Harnesses★ 1.5ksame name
- microsoft/cat-agent-skills★ 108same name
- Job-Yang/jobbyang-ai-skills★ 100same name
- Job-Yang/jobyang-ai-skills★ 100same name
- tansuasici/claude-research-kit★ 4same name
- duu261/agent-skills★ 2same name
- NotRedFox/NotRedFoxs-Claude-skills★ 1same name
- 8TrafficAI/8traffic-marketing-skills★ 0same name
- adithyanraj03/dsh-skills-pack★ 0same name
- mbalazy/claude-skills★ 0same name
1 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
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
6
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 12
After your last code or config edit, run the thing that proves it: the tests, the build, the command, a request to the live URL.
- Distinctive: line 13
Put the result in your answer: how many tests passed, the status code, the commit, the exit code.
- Distinctive: line 14
If you edited again after that run, run it again.
- Distinctive: line 16
If you can't run the check, say so: "changed, not verified yet".
- Distinctive: line 20
Look at least twice, in different ways: search for the name, then search for a likely alias or read the place it would be registered.
- Distinctive: line 30
Cleanup: No temporary files, debug output or backup copies left behind.
“Common” is measured: kept by at least 6 in 10 of the 8 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
claim-check
Two kinds of sentence cause most of the damage when they are wrong: "it's fixed" and "it isn't there". Before you write either one, have the proof in this turn.
Before you say it's done, fixed, deployed or passing
- After your last code or config edit, run the thing that proves it: the tests, the build, the command, a request to the live URL.
- Put the result in your answer: how many tests passed, the status code, the commit, the exit code.
- If you edited again after that run, run it again. A check from before the last edit proves nothing about the code now.
- Re-reading the file you just edited is not a check.
- If you can't run the check, say so: "changed, not verified yet". That's an acceptable answer.
Before you say something doesn't exist or isn't used
Look at least twice, in different ways: search for the name, then search for a likely alias or read the place it would be registered. If you only looked once, call it a guess.
When "done" means a real fix
A real fix covers five things. Say which ones you did, and which you skipped:
- Cause. You found why it broke, not only where.
- Prevention. Something now stops the same failure, such as a test, a check or a guard.
- Same bug elsewhere. You looked for the same bug in similar places.
- Verification. You ran the real thing and saw it work.
- Cleanup. No temporary files, debug output or backup copies left behind.
A workaround that stops the symptom is fine. Call it a workaround, not a fix.
If a hook blocked you
The claim-check hook found a claim without proof. Run the check and show the result, cite proof you already have (a commit hash, a line like "14 passed" or "HTTP 200") if you changed no code this turn, or rewrite the sentence as "not verified yet". Do one of these before you stop again.
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.

