paper-claim-audit

Cross-reference quantitative paper claims against raw evidence files and emit audit verdicts.

1|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/zhuyingqin/ARIS-WEB --skill paper-claim-audit-zhuyingqin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paper-claim-audit
Source: https://github.com/zhuyingqin/ARIS-WEB/tree/main/crates/runtime/assets/skills/paper-claim-audit
Command: npx skills add https://github.com/zhuyingqin/ARIS-WEB --skill paper-claim-audit-zhuyingqin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Edit, Grep, Glob, Agent, mcp__codex__codex, and includes assets (resource) components.

What problem does it solve?

This Skill prevents confirmation bias by checking that every quantitative claim in a paper exactly matches the underlying raw result files, not just what the executor expects.

Core Features & Use Cases

  • Zero-context evidence audit: Runs a fresh reviewer with no prior logs, summaries, or narrative context, only the paper .tex claims and raw evidence files.
  • Claim-to-evidence tracing: Extracts each numeric/percentage/comparison claim and maps it to the exact file and value it came from.
  • Targeted mismatch detection: Flags rounding drift, best-seed vs average cherry-picks, config/split mismatches, aggregation errors, arithmetic delta mistakes, caption/table mismatches, and scope overclaims.
  • Deterministic outputs for review pipelines: Always emits PAPER_CLAIM_AUDIT.md and the authoritative PAPER_CLAIM_AUDIT.json for downstream verification steps.

Quick Start

Run paper-claim-audit to check whether the numbers and comparisons in your paper match the raw result files in your paper directory.

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 paper claims against raw experimental data before submission?

Verifying paper claims against raw experimental data requires extracting every numeric assertion from .tex files and cross-referencing values directly against raw .json, .csv, .yaml, and metrics files to ensure exact matches without relying on executor summaries.

What is zero-context evidence auditing for academic papers?

Zero-context evidence auditing prevents confirmation bias by running a fresh reviewer with no prior logs or narrative context, checking only paper .tex claims against raw evidence files to detect mismatches in numeric accuracy and rounding.

How do I detect rounding errors or cherry-picked best-seed results in a manuscript?

Detecting rounding errors or cherry-picked best-seed results involves tracing extracted quantitative claims back to raw result files, flagging rounding drift, aggregation errors, and best-seed versus average discrepancies for submission readiness.

Can I audit LaTeX paper numbers against CSV and JSON raw result files?

Auditing LaTeX paper numbers against CSV and JSON files is supported by strict extraction of numeric and scope claims from .tex documents, cross-referencing them against raw .json, .csv, .yaml, metrics, and config inputs to confirm exact matches.

What does a paper claim audit output look like for review pipelines?

A paper claim audit outputs deterministic PAPER_CLAIM_AUDIT.md and PAPER_CLAIM_AUDIT.json files containing per-claim verdicts and hashes, providing structured downstream verification steps for submission assurance workflows.

When should I not rely on executor summaries for paper submission readiness?

Executor summaries should not be relied upon for submission readiness when confirmation bias risks exist, as quantitative claims require fresh-model zero-context review against raw evidence to catch caption mismatches, config discrepancies, and scope overclaims.