paper-claim-trace

Trace manuscript claims to result files and pre-registered decision rules.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill paper-claim-trace-zk-theory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paper-claim-trace
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/paper-claim-trace
Command: npx skills add https://github.com/ZK-Theory/TDL --skill paper-claim-trace-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting a research manuscript often produces prose that runs ahead of the evidence: numbers with no backing result file, conclusions stronger than the data, or negative results quietly softened. This Skill audits every claim in a draft so each one is bound to a concrete result artifact and the pre-registered decision rule that licenses it. ## Core Features & Use Cases - Claim-to-artifact binding: Links every quantitative or interpretive claim, table entry, figure caption, and limitation to a date-suffixed result JSON and vault [RESULT]/[DECISION]/[NEGATIVE] entry. - Decision-rule lock checking: Verifies that outcome-contingent prose follows the pre-registered outcome-to-prose mapping rather than a post-hoc reading. - Honest reporting enforcement: Flags overstated claims, buried nulls, and undisclosed cascade effects or pre-registration amendments, producing a claim-by-claim verdict table (TRACED / AWAITING COMPUTATION / OVERSTATED / UNDISCLOSED). - Use Case: Before submitting a paper, run the audit on the discussion section to confirm each reported effect size matches its result file and that a weaker-than-expected finding is reported honestly rather than hedged. ## Quick Start Audit the claims in my manuscript draft and verify each one traces to a result file and decision rule.

Frequently Asked Questions about paper-claim-trace

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

FAQPage Schema
How do I verify manuscript claims against experimental results?▼

Verify manuscript claims by binding each claim to its backing result file and vault entry, then checking the prose value matches the result to the stated precision. The audit outputs a claim-by-claim table with verdicts: TRACED, AWAITING COMPUTATION, OVERSTATED, or UNDISCLOSED.

How to check that paper conclusions follow pre-registered decision rules?▼

Check that outcome-contingent claims have a vault [DECISION] entry locking the outcome-to-prose direction against the pre-registered rule. Prose must follow the locked direction; any claim without a decision-rule lock triggers escalation.

What happens when a drafted claim has no backing result file?▼

A claim with no backing result file or vault entry is flagged as AWAITING COMPUTATION, and no prose should be drafted for it under the empiricism-first rule. The audit lists every untraced claim explicitly and escalates rather than guessing.

Does this handle negative or weaker-than-expected results?▼

Yes, negative or weaker-than-expected results must be reported as such, with the claim's strength matching the result's strength. Hedged prose implying a stronger finding is flagged as OVERSTATED, and buried nulls are surfaced.

When should disclosure of amendments or cascade effects be checked?▼

Disclosure is checked whenever cascade effects, pre-registration amendments, or superseded analyses affect a claim. These must appear in the limitations or methods text; missing disclosures produce an UNDISCLOSED verdict.