blog-factcheck

Featured

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".

Data & Documents 2,121 stars 354 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 fetching: allow `http` and `https` only, reject `localhost`, loopback, private, link-local, and reserved IPs after DNS resolution, reject `javascript:`, `data:`, and `file:` URLs, limit redirects and validate the final URL, and cap response size and timeout. 2. Fetch the source pa...

Details

Author
AgriciDaniel
Repository
AgriciDaniel/claude-blog
Created
6 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

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 statistical claims (numbers, percentages, named sources), fetches each cited URL via WebFetch, 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".

0 Updated 1 weeks ago
gaznilmuzammil12-prog
AI & Automation Listed

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,...

1 Updated 1 months ago
imMamdouhaboammar
Data & Documents Listed

factcheck

Adversarial citation and claim audit for any document — "do these sources actually say what the text claims?" Takes a markdown file, URL, or pasted draft (including this repo's own pulse/verdict briefs), extracts every checkable claim, then fans out verifier sub-agents instructed to refute, not confirm: does the cited link resolve AND assert the claim as stated, is the source primary or a laundered secondary write-up, has the claim gone stale. Emits a graded audit table — VERIFIED / MISATTRIBUTED / UNSUPPORTED / STALE / UNCHECKABLE — with a quoted passage as evidence for every grade, saved to out/factcheck/. Advisory: it grades, the human edits. Use when the user wants to check citations, verify sources, or audit a report, post, or brief — e.g. "/factcheck <doc>", "verify the sources in this", "are these citations real?", "is this actually true?". For researching a fresh topic use pulse; for judging code changes use done.

9 Updated 3 days ago
duthaho