Agent skill · Data & Analytics

blog-factcheck

Verify statistics and claims in blog posts by fetching cited source URLs and checking if the claimed data actually appears on the page. Extracts all load-bearing claims (statistics, product or policy claims, ranking and comparative claims, named sources), validates cited URLs before fetching, and scores match confidence (exact match 1.0, paraphrase 0.7-0.9, not found 0.0). Flags uncited claims as UNVERIFIED. Use when user says "fact check", "verify statistics", "check sources", "validate claims", "factcheck", "source verification".

AgriciDanielgithub.com/AgriciDanielGitHub ↗
claude-codeMIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-factcheck --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/blog-factcheck/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,566
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Blog Fact-Check Verify statistics, claims, and source attributions in blog posts. Pure Claude pipeline with no external NLP dependencies. ## Workflow ### Step 1: Read the Blog Post Read the target file and identify all sections containing data or other load-bearing claims. ### Step 2: Extract Load-Bearing Claims Scan the full text for every claim that would need evidence if challenged. Include numeric claims and non-numeric load-bearing claims such as policy, product, ranking, methodology, legal, comparative, "best", "first", "latest", or platform-behavior statements. Build a claims list with these fields: | Field | Description | |-------|-------------| | claim_text | The exact sentence or phrase containing the claim | | claim_type | Statistic, policy, product, ranking, comparative, legal, methodology, freshness | | value | The numeric value if present (e.g., "42%", "$1.2M", "3x") | | attribution | Named source if present (e.g., "HubSpot", "Gartner 2025") | | url | Cited URL if present (from markdown link or parenthetical) | | location | Heading or line number where the claim appears | ### Step 3: Verify Cited Claims For each claim that includes a URL: 1. Validate the URL before

What's inside
Steps it walks through
  1. Workflow
  2. Step 1: Read the Blog Post
  3. Step 2: Extract Load-Bearing Claims
  4. Step 3: Verify Cited Claims
  5. Step 4: Flag Uncited Claims
  6. Step 5: Generate Verification Report
  7. Claim Extraction Patterns
  8. Source Tier and Echo Checks
  9. Verification Scoring
  10. Output Format
  11. Verification Report: [Post Title]
  12. Recommended Actions
  13. Integration
  14. Cross-reference
More from claude-blog
All skills →
About this skill
What does the blog-factcheck skill do?

Verify statistics and claims in blog posts by fetching cited source URLs and checking if the claimed data actually appears on the page. Extracts all load-bearing claims (statistics, product or policy claims, ranking and comparative claims, named sources), validates cited URLs before fetching, and scores match confidence (exact match 1.0, paraphrase 0.7-0.9, not found 0.0). Flags uncited claims as UNVERIFIED. Use when user says "fact check", "verify statistics", "check sources", "validate claims", "factcheck", "source verification".

How do I install it?

Run `npx skills add AgriciDaniel/claude-blog --skill blog-factcheck --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From AgriciDaniel/claude-blog, a repository with 1,566 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going