paper-claim-audit

Reconciles quantitative claims in a paper with raw evidence files.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lightrain-a/medtrace-aris --skill paper-claim-audit-lightrain-a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paper-claim-audit
Source: https://github.com/lightrain-a/medtrace-aris/tree/main/.vendor/aris/skills/paper-claim-audit
Command: npx skills add https://github.com/lightrain-a/medtrace-aris --skill paper-claim-audit-lightrain-a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Paper results can drift from what the raw experiment outputs actually contain due to rounding, cherry-picking, config or dataset mismatches, caption/table errors, arithmetic mistakes, or scope overclaims.

Core Features & Use Cases

  • Zero-context paper-to-evidence verification: checks every quantitative claim in the paper against raw result files using a fresh reviewer with no prior context to reduce confirmation bias.
  • Evidence tracing with explicit statuses: reports exact matches, rounding-allowed matches, ambiguous mappings, missing evidence, config/aggregation mismatches, number mismatches, and unsupported/scope overclaims.
  • Deterministic audit artifacts: writes both a human-readable report (PAPER_CLAIM_AUDIT.md) and a machine-readable JSON (paper/PAPER_CLAIM_AUDIT.json) for downstream verification workflows.

Quick Start

Run the paper-claim-audit skill on your paper directory (including the .tex sources and the raw results/config files) to produce PAPER_CLAIM_AUDIT.md and paper/PAPER_CLAIM_AUDIT.json with a PASS/WARN/FAIL verdict.

Frequently Asked Questions about paper-claim-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify quantitative claims in a research paper against raw data files?

Paper-to-evidence verification checks every quantitative claim against raw result files using a zero-context reviewer to reduce confirmation bias. It applies strict matching with standard rounding rules and validates relative-delta arithmetic to ensure paper-to-results fidelity.

What is zero-context paper-to-evidence verification and how does it reduce confirmation bias?

Zero-context verification means a fresh reviewer with no prior context checks quantitative paper claims against raw result files. This method prevents confirmation bias by excluding executor summaries and relying only on paper sources and raw artifacts.

How do I check if my paper tables and captions match the raw experimental outputs?

You audit paper tables and captions by reconciling each number and scope statement against raw results and config artifacts. The audit emits structured per-claim verdicts that identify exact matches, rounding-allowed matches, ambiguous mappings, and missing evidence.

Can I audit paper claims for specific datasets and configurations excluding executor summaries?

Yes, claim auditing works for specific datasets and configurations while excluding executor summaries. The process reads only paper .tex sources and raw results or config artifacts to verify paper-to-results fidelity without being influenced by executor summaries.

What types of discrepancies does a paper claim audit report identify?

A paper claim audit identifies exact matches, rounding-allowed matches, ambiguous mappings, missing evidence, config or aggregation mismatches, number mismatches, and unsupported scope overclaims. These are emitted as structured per-claim verdicts in both human-readable and machine-readable formats.

What output formats are generated when auditing paper numbers against raw evidence?

Auditing paper numbers generates a human-readable markdown report and a machine-readable JSON file. These deterministic audit artifacts contain structured per-claim verdicts with PASS, WARN, or FAIL outcomes for downstream verification workflows.