claims-evidence

name	claims-evidence
description	Map claims in the paper to results, configs, or code; avoid unsupported claims.

Claims–Evidence Skill

When to Use

• You are drafting or revising paper text and need to ensure every claim is backed by evidence.
• You are reviewing the paper for unsupported or fabricated claims.

Instructions

• Use references/check-rules.md for the mapping rules.
• When writing: Before adding a claim (e.g. "our method improves over X"), identify the evidence: result file, config, table, or citation. If none exists, do not add the claim or mark it as TODO.
• When reviewing: For each substantive claim in the draft, list the corresponding evidence (path or citation). Flag any claim with no evidence.
• Never fabricate: Do not invent numbers, tables, or figures. Ask the user for real outputs or suggest running the experiment first.