verify-before-claiming

Validates numbers, statuses, and citations against generating code or primary records before publication.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/ricfulop/cba-agentic-engineering-bootstrap --skill verify-before-claiming-ricfulop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-before-claiming
Source: https://github.com/ricfulop/cba-agentic-engineering-bootstrap/tree/main/skills/verify-before-claiming
Command: npx skills add https://github.com/ricfulop/cba-agentic-engineering-bootstrap --skill verify-before-claiming-ricfulop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents often quote performance numbers, fabrication statuses, or corpus counts that were never actually re-run or confirmed, letting stale or invented claims reach papers, abstracts, and decks. This Skill enforces a verification discipline so every quoted value traces back to generating code or a primary record checked today. ## Core Features & Use Cases - Claim Verification: Locates the generating code or primary record behind any number, status phrase, or count, runs or reads it, and states the filter the measurement applied. - Withdrawal Discipline: When a claim falls, banners the document and splits what is withdrawn, what is contaminated, and what still stands, without silently deleting or reversing claims. - Label Integrity: Blocks upgrading of candidate, exploratory, non-confirmatory, PLACEHOLDER, or QUOTE REQUIRED markers unless the underlying analysis changed, and forbids inventing DOIs (preferring scite or paper-lookup plus Crossref). - Use Case: Before submitting a paper quoting a 12% efficiency gain, re-run the benchmark script, confirm the measurement filter, and verify the citation through scite rather than trusting the draft text. ## Quick Start Verify the performance number and citation in section 3 of my draft against the generating code and a live source before I submit it.

Frequently Asked Questions about verify-before-claiming

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

FAQPage Schema
How do I verify a performance number before quoting it in a paper?

Find the code or primary record that generated the number, run it or read it today, and state the filter the measurement applied. If the record is silent on the claim, say so explicitly rather than deriving a value to fill the gap.

What should I do when a claim in my document turns out to be wrong?

Withdraw rather than delete: banner the document and split what is withdrawn, what is contaminated, and what still stands. A withdrawn claim is not thereby reversed, so the record of the correction stays visible.

How do I verify citations without inventing DOIs?

Never invent DOIs. Prefer the scite MCP for citation checking; if scite is unavailable, use the paper-lookup skill together with a one-pass Crossref query to confirm the reference exists.

When can I upgrade a claim marked candidate or exploratory?

Only when the corresponding analysis has actually changed. Labels like candidate, exploratory, non-confirmatory, PLACEHOLDER, or QUOTE REQUIRED must not be upgraded based on wording edits or time passing alone.

Why can a correctly computed number still be misleading?

A number can be computed correctly yet not measure what its label says. Resolve the label against the code that produced the value before it reaches a paper, abstract, or deck.