claim-evidence-audit
Skill4 starsChanged 32 days agoMITView on GitHub
Audit whether manuscript claims follow from supplied evidence, especially causal attribution, historical provenance, citation entailment, and generalization. Use for substantive claim review, not a grammar-only request.
In this repository17 other files it gives its agents.
- academic-prose-editingSkill
- academic-writing-auditSkill
- experiment-comparison-auditSkill
- figure-caption-auditSkill
- latex-bibliography-auditSkill
- manuscript-release-checkSkill
- method-definition-auditSkill
- nondefensive-writingSkill
- reference-authenticity-auditSkill
- related-work-synthesisSkill
- research-manuscript-writingSkill
- results-interpretationSkill
- reviewer-comment-triageSkill
- reviewer-response-writingSkill
- revision-integrity-auditSkill
- scientific-story-auditSkill
- word-citation-auditSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 17
If sources conflict, identify the conflict rather than silently privileging the newest file or an old review marked “resolved.” Missing …
- Distinctive: line 28
When multiple factors change together, keep the system-level comparison and remove unsupported component attribution.
- Distinctive: line 46
Read the worked examples when provenance, attribution, or citation support is ambiguous.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Evidence Audit
Keep the strongest conclusion the evidence supports. Distinguish an incorrect claim from an unresolved one, and an unsupported interpretation from a valid observation. Work with the user's supplied material and requested scope; this skill does not require a particular model, tool, or empirical research design.
Establish the question and sources
Identify the passage and whether the user wants findings, suggested wording, or edits. A review request does not itself request rewriting. Preserve an intentional definition, sound assumption, and supported result unless a concrete problem justifies a change.
Determine what each relevant source can establish. The manuscript establishes its current claims; an author clarification establishes intended meaning; current code establishes inspected behavior. A historical execution claim needs records linking the relevant version, configuration, inputs, and outcome. A later diagnostic or passing test cannot supply that link by itself. Do not demand full provenance for an editorial question that does not depend on it.
If sources conflict, identify the conflict rather than silently privileging the newest file or an old review marked “resolved.” Missing evidence does not prove the claim false.
Test the inferential link
For each consequential claim, recover the precise subject, endpoint, conditions, and supporting evidence. Separate four levels:
- Observation: What the experiment, source, or analysis directly reports.
- Interpretation: What that observation is consistent with, given alternatives.
- Attribution: What the design or argument isolates as responsible.
- Generalization: Where the result extends beyond the studied cases or assumptions.
When multiple factors change together, keep the system-level comparison and remove unsupported component attribution. A working configuration that lacks a component does not automatically show the component is unnecessary in all settings. A selected result does not alone establish why selection helped.
Changing “proves” to “suggests” is insufficient if the causal story still has no evidential link. Repair the proposition, not just its confidence word. Conversely, retain a supported numerical difference without weakening it into vague possibility merely because significance was not evaluated.
Adapt the standard to the evidence. Check assumptions and derivation for a theorem. Distinguish participants' accounts from measured prevalence or causal effects in qualitative work. Do not impose an experimental ablation on every discipline.
When an actual cited source is available, check whether it entails the attached proposition at the relevant level: background, association, mechanism, or result. Distinguish bibliographic validity from claim support. If the source is unavailable, mark entailment unverified; do not invent its contents or expand a bounded audit into an unsolicited literature search.
Prose when drafting or revising
When drafting or revising prose, including audit explanations, read prose editing rules. Preserve scientific meaning, necessary reasoning and valid technical terms. Keep sound passages, do not add unreported properties, and limit edits to the requested scope. The local reference covers concept accuracy, clear sentences, repetition and punctuation, including the required exceptions.
Return a usable decision
Give prioritized findings with the claim location, evidence, consequence, and smallest justified repair. Use a compact claim-to-source table only when several claims would otherwise be confused. Identify supported passages worth keeping. If editing is requested, retain the endpoint, numbers, conditions, and author terminology while correcting the unsupported inference.
Keep uncertainty close to the affected claim rather than appending a blanket disclaimer. State what was actually inspected. Stop when material claims are supported, proportionally narrowed, or explicitly unresolved within the requested scope; missing evidence need not prevent completing the supported portion. Do not invent measurements, significance, records, or verification status to close a gap.
Read the worked examples when provenance, attribution, or citation support is ambiguous.
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.

