claim-provenance

Tags document fact-claims inline as validated or assumption with retire-by milestones.

4|1|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/radarist/structured-analytic-skills --skill claim-provenance-radarist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claim-provenance
Source: https://github.com/radarist/structured-analytic-skills/tree/main/skills/claim-provenance
Command: npx skills add https://github.com/radarist/structured-analytic-skills --skill claim-provenance-radarist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Briefs and reports often mix cited facts with reasoned guesses so seamlessly that readers cannot tell which sentences rest on evidence and which rest on priors, leading to over-trusted assumptions or wholesale distrust of the document. This Skill separates the two by tagging every fact-claim inline with its provenance. ## Core Features & Use Cases - Inline provenance tagging: Marks each fact-claim as [validated, {source}] when a specific source states it, or [assumption, retire-by {milestone}] when it is reasoned from priors, with every assumption tied to a concrete event, date, or threshold that will test it. - Coverage reporting: Emits a coverage line verifying that at least 80% of quantitative sentences, 100% of headline claims, and 100% of forward-looking projections are tagged. - Vendor self-report handling: Treats a party's claims about itself as assumptions requiring independent verification rather than validated facts. - Use Case: A market brief claims "$6.25B market size" and "24.8% CAGR" alongside a projection that "skills graphs will dominate by 2027". The Skill tags the first two with their analyst-report citations and the projection as an assumption with a dated retire-by milestone, so a decision-maker sees exactly which numbers are sourced. ## Quick Start Go through this draft and tag each claim as validated with its source or as an assumption with a specific retire-by milestone, then show me the coverage summary.

Frequently Asked Questions about claim-provenance

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

FAQPage Schema
How do I mark which claims in a report are sourced versus assumptions?▼

Tag each fact-claim inline: use [validated, source] when a specific source states that exact claim, and [assumption, retire-by milestone] when it is reasoned from priors. Place the bracket immediately after the sentence, then report coverage across the document.

What counts as a validated claim versus an assumption?▼

A claim is validated only when a specific, reasonably authoritative source states that exact claim, such as filings for financials or registries for grants. It is an assumption when reasoned from priors, projected without a model, or based on a party's self-report about itself.

What is a retire-by milestone for an assumption?▼

A retire-by milestone is a specific event, date, or threshold that will convert an assumption into knowledge or kill it, such as a quarterly earnings disclosure. Vague milestones like "later" or "more research" are rejected because they carry no discipline.

When should I not use claim provenance tagging?▼

Do not use it to verify whether a specific value is correct; that is fact-checking against sources. It also does not fit corroborating a single claim across sources, or tagging headings, methodology text, and qualitative narrative, which should stay untagged.

How much of a document needs provenance tags?▼

Coverage thresholds require at least 80% of quantitative sentences tagged, 100% of executive-summary and headline fact-claims tagged, and 100% of forward-looking projections tagged as assumptions with retire-by milestones. The coverage line reports each figure.