agentleFS
youyu-codeyouyu-code/research-pipeline-skills/skills/evidence-audit/SKILL.md

evidence-audit

Skill1 starsChanged 12 days agoApache-2.0View on GitHub

Scope: one claim, not one paper. Reviewing or grading a paper is out of scope, even with its numbers quoted. Adjudicate one specific claim: is it supported, unsupported, or undecidable given the numbers actually available. Use when the input is a claim rather than a paper — a quoted sentence plus its reported figures — and the answer must be a verdict with a stated evidence boundary. Applies three ordered tests (claim anchoring, counter-evidence, availability), a four-tier reversal scale (rank flip / strength collapse / scope narrowing / not a reversal), and the rule that a second number in the same table does not by itself license a second reading. Input: claim text, available numbers with provenance, and the material boundary stating what was and was not read. Output: verdict, tier, attribution as defect versus ambiguity, and the exact citation form allowed. It does not build cards, matrices or proposals; given a whole paper to document rather than a claim to rule on, use paper-card.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    When later evidence changes a claim's standing, the change has a tier, and the tier is not a matter of emphasis:

    line 47
  2. Distinctive:

    Every non-trivial ruling also says what kind of problem it is.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 5 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

evidence-audit

One claim in, one verdict out, with the boundary of the evidence stated in the same breath.

The discipline is entirely in refusing to rule on the cases where the material does not permit it. A verdict of undecidable is a success, not a failure to try.

The three tests, in this order

OrderTestQuestionIf it fails
1anchoringwhich sentence, in the paper, states this claimno verdict — the claim is your paraphrase
2counter-evidencedoes the paper itself contain something that refutes itunsupported, with the quote
3availabilitycould the available material distinguish the claim from its negationundecidable, with the missing artefact named

The order matters: a claim with no anchor cannot be audited at all, and a claim with an anchor plus a direct refutation does not need the availability test.

→ references/three-tests.md

Two rules that decide most cases

  • A numeric anchor is not an anchor. If the same table reports another number that would support a second reading, the claim is still a claim: only the paper's own sentence counts as the anchor. Otherwise every paper that reports a full table is automatically immune, and the undecidable category becomes structurally empty.
  • "Not discussed" is not "not claimed". An absence of discussion is not ambiguity. A factual statement that the paper can be seen to contradict is a defect, not an ambiguity, no matter how little the authors say about it.

→ references/counter-examples.md for the ten rulings that look correct and are not.

Reversal tiers

When later evidence changes a claim's standing, the change has a tier, and the tier is not a matter of emphasis:

TierNameTest
T1rank flipthe ordering of two methods reverses
T2strength collapsethe direction holds, the effect falls inside the noise band
T3scope narrowingholds inside a stated boundary, fails outside
T0not a reversalrestated, re-measured, or re-scoped without changing the claim

Count after defining, never before. A count of "reversals" produced before the tiers exist overstates: in the one corpus where this has been checked, five of twelve findings moved out of the reversal column (12 → 7).

→ references/reversal-tiers.md

Attribution

Every non-trivial ruling also says what kind of problem it is. Four names, used verbatim:

NameMeans
defect-self-datathe paper contradicts its own reported data
defect-external-factthe paper contradicts a checkable outside fact
ambiguity-two-readingsone sentence supports two anchored readings
ambiguity-term-overloadone term carries two meanings

The first word decides who fixes it: a defect needs new data or a correction, an ambiguity needs one sentence. Confusing them sends a defect to the authors as a wording question, and an ambiguity back as an error.

→ references/attribution.md

What this skill refuses

  • Refuses to rule on a paper. That is paper-card: a card documents, this rules on one claim.
  • Refuses to rule without an anchor. A paraphrase is not auditable, and rewriting the claim until it is auditable is how audits produce their own answers.
  • Refuses to convert its output into a blocker level or a repair priority. Verdicts live here; stopping decisions and repair order belong to the pipeline's operating layer.

Output contract

claim:     "<quoted, with §>"
anchor:    "<the sentence that states it, with §>"
verdict:   supported | unsupported | undecidable
basis:     <the test that decided it, and its result>
tier:      T1 | T2 | T3 | T0 | n/a
attribution: defect-self-data | defect-external-fact | ambiguity-two-readings | ambiguity-term-overload | n/a
boundary:  <material read, and what was not>
allowed:   "<the exact citation form this verdict permits>"

The boundary line is not optional: a verdict without its evidence boundary reads as absolute.

Routing

TaskGo to
run the three tests on a claimreferences/three-tests.md
classify how a claim's standing changedreferences/reversal-tiers.md
decide defect versus ambiguityreferences/attribution.md
tag the problem for the registerreferences/m-taxonomy.md
check a ruling against known failure shapesreferences/counter-examples.md
document a whole paperpaper-card
compare several paperssynthesis-matrix
act on a verdict inside a proposalproposal-forge

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.