claim-repro-score

Audits documentation against project artifacts to verify reproducibility of technical claims.

30|12|Updated Jun 21, 2026

Search Tags:#documentation #audit #benchmarking #reproducibility #falsifiability #truth-maintenance

Ready to run

npx skills add https://github.com/anthony-chaudhary/fak --skill claim-repro-score

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claim-repro-score
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/claim-repro-score
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill claim-repro-score

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the problem of unverified or unfalsifiable claims in technical documentation, ensuring that every assertion made in the repository is backed by a reproducible artifact, test, or path.

Core Features & Use Cases

Scorecard Execution: Runs automated checks against CLAIMS.md and BENCHMARK-AUTHORITY.md to identify missing evidence.
Debt Retirement: Guides the user in resolving unfalsifiable witnesses by adding missing artifacts, test patterns, or correcting package paths.
Truth Maintenance: Ensures that documentation remains a reliable source of truth by re-measuring claim reproducibility after updates.

Quick Start

Run the claim-repro-score skill to audit the current repository claims and generate a report on missing evidence.

Frequently Asked Questions about claim-repro-score

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

FAQPage Schema

How do I verify technical claim reproducibility in my repository documentation?▼

Verify technical claim reproducibility by running an automated scorecard script that audits documentation against project artifacts and test patterns to identify missing evidence. It validates whether assertions in your repository are backed by reproducible artifacts.

What is claim falsifiability and when do I need to audit it in a software lifecycle?▼

Claim falsifiability ensures every technical assertion is backed by a reproducible artifact or test path. Audit it during software development lifecycles to maintain documentation integrity and ensure performance or functional benchmarks remain a reliable source of truth.

How do I resolve missing witness debt in benchmark documentation?▼

Resolve missing witness debt by following guided remediation to add missing artifacts, implement test patterns, or correct package paths. This debt retirement process ensures all benchmark claims have verifiable supporting evidence.

Can I audit CLAIMS.md files against existing project artifacts automatically?▼

Yes, run the claim-repro scorecard script to automatically audit CLAIMS.md and BENCHMARK-AUTHORITY.md files against existing project artifacts and test patterns. It generates a report identifying unfalsifiable witnesses and missing evidence.

What's the best way to maintain documentation integrity after updating benchmarks?▼

Maintain documentation integrity by re-measuring claim reproducibility after updates using the scorecard script. This truth maintenance process ensures your documentation remains a reliable source of truth by verifying all assertions still have valid backing evidence.

Why does my documentation audit report show unfalsifiable witnesses?▼

Unfalsifiable witnesses appear when technical claims lack backing from reproducible artifacts, tests, or valid package paths. The audit identifies this missing evidence debt so you can correct documentation and ensure all assertions are verifiable.