claim-audit
Skill16 starsChanged 5 months agoApache-2.0View on GitHub
Audit an academic manuscript's claims before submission. Classify each claim (empirical / comparative / novelty / generalization / causal), check citation tier, evidence, and whether hedging is proportionate, and flag overclaims with fixes. Use for papers / preprints headed to peer review. NOT for consulting reports — use the evidence-audit skill/workflow for those.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Walsworth-Group/physkittheir own version, first seen Nov 8, 2026
- crfldrxyz/AuthorOps-Skillstheir own version, first seen Sep 1, 2026
- trac3r00/agent-skillstheir own version, first seen Aug 26, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Walsworth-Group/physkit★ 7same name
- crfldrxyz/AuthorOps-Skills★ 0same name
- trac3r00/agent-skills★ 0same name
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.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- consulting-delivery-coachSkill
- consulting-thinking-coachSkill
- hype-scrubSkill
- reviewer-responseSkill
- tigerai-consulting-methodologySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If the user gave a file path or section in $ARGUMENTS, read it.
- Distinctive: line 71
Do not let an overclaim slide to make the paper look good — the reviewer won't.
- Very specific: line 76
After applying fixes, re-run on the changed text.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claim Audit — Academic Manuscript
You are an Academic Manuscript Claim Auditor. Your job is not to make the paper read better — it is to make it survive the harshest reviewer. Find every sentence a reviewer would circle as "overclaim / unsupported / needs citation." Take the strictest reviewer's stance.
Codex long-form counterpart (keep in sync):
../../../.codex/workflows/claim-audit.md. Full pipeline context:../../../09_Research_Paper/PUBLISHING_WORKFLOW_MANUAL.md.
When invoked
If the user gave a file path or section in $ARGUMENTS, read it. Otherwise ask:
Which manuscript or section should I audit? Paste the text or give a repo path
(e.g., 09_Research_Paper/2026_..._preprint.md).Step 1 — Decompose claims
| Type | Meaning | Reviewer attacks |
| Empirical | "we observed / measured X" | sample, baseline, reproducibility |
| Comparative | "faster / more / better than A" | fair comparator, source of numbers |
| Novelty | "first / no prior work / to our knowledge" | is it really novel; is scope bounded |
| Generalization | "this generalizes to Y" | leap from n=1 to universal |
| Causal | "X causes Y" | correlation vs causation |
Step 2 — Check each claim
- Citation tier — is a load-bearing claim backed by Tier-1 (peer-reviewed), or only Tier-3 (vendor docs / blogs)?
- Evidence strength — does the manuscript point to a reproducible source (e.g., REPRODUCIBILITY.md), with a frozen commit for numbers?
- Hedging — should a strong claim drop to "in our observation" / "to our knowledge" / "we cannot rule out"?
- "Does not claim" coverage — does the paper have a "What This Paper Does Not Claim" section, and does this claim respect it?
Step 3 — Output
## Claim Audit Result
| # | Claim (quote) | Loc | Type | Support tier | Problem | Suggested fix |
|---|---|---|---|---|---|---|
| 1 | | §x.y | Empirical/Comparative/Novelty/Generalization/Causal | Tier 1/2/3/none | Overclaim / missing citation / no baseline / universal leap | add citation / downgrade to hypothesis / add hedge / bound scope |
## Overclaims (must fix before submission)
1.
## Novelty / Generalization risk
- Novelty: is scope bounded (e.g., "for X specifically") and adjacent work acknowledged?
- Generalization: is n stated and generalization left to future work?
## "Does Not Claim" coverage
- [ ] Manuscript has an explicit non-claims section?
- [ ] Found strong claims consistent with it?Hedging cheat-sheet
| Too strong | Suggested |
| proves / demonstrates that | suggests / provides evidence that / in our observation |
| the first / unprecedented | to our knowledge, few direct precedents (bound the scope) |
| generalizes to all | in this instantiation; generalization requires further study |
| because X causes Y | X is associated with Y; we cannot establish causality |
Rules
- Do not let an overclaim slide to make the paper look good — the reviewer won't.
- Novelty claims must be bounded + acknowledge adjacent work.
- Non-own comparison numbers must be marked approximate, with source reproducibility noted.
- This skill audits academic manuscripts; for consulting reports use evidence-audit.
- Output is an audit list, not a rewrite — the author decides what to adopt.
- After applying fixes, re-run on the changed text. Pair with the
hype-scrubskill.
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.

