blog-factcheck

Verify statistics and claims in blog posts by fetching cited source URLs and scoring match confidence.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-factcheck-captaindevv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blog-factcheck
Source: https://github.com/captaindevv/SEO-ajaypipes/tree/main/skills/blog-factcheck
Command: npx skills add https://github.com/captaindevv/SEO-ajaypipes --skill blog-factcheck-captaindevv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Blog posts often contain statistics and claims that are misquoted, outdated, or lack any source, which damages credibility. This Skill automates the tedious work of checking every numeric claim against its cited source so you can publish with confidence. ## Core Features & Use Cases - Claim Extraction: Scans a blog post for every statistic, percentage, dollar amount, and named-source attribution, building a structured claims list with location and URL. - Source Verification: Fetches each cited URL via WebFetch and scores how well the page supports the claim, from exact match (1.0) to not found (0.0). - Uncited Claim Flagging: Marks claims without sources as UNVERIFIED and suggests search queries to find supporting evidence. - Use Case: Before publishing a marketing post citing "73% of marketers use video", run the fact-check to confirm the stat appears on the cited report page and get a report of any claims needing new sources. ## Quick Start Fact check the statistics and sources in my blog post draft.md and show me the verification report.

Frequently Asked Questions about blog-factcheck

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

FAQPage Schema
How do I fact check statistics in a blog post?▼

Run the fact-check workflow on your post file. It extracts every claim containing a number, percentage, or named source, fetches each cited URL, and produces a report scoring each claim as verified, paraphrase, weak, not found, or unverified.

How does automated source verification work for cited URLs?▼

Each cited URL is fetched and searched for the specific numeric value in the claim. An exact match in matching context scores 1.0, paraphrased or rounded data scores 0.7-0.9, a topically relevant page without the stat scores 0.3-0.6, and missing data scores 0.0.

What happens to claims in my post that have no source URL?▼

Claims without a URL are marked UNVERIFIED rather than scored. The report suggests a search query you can run to find a source, and if the claim names a specific organization, it suggests checking that organization's domain.

Can this verify statistics behind paywalls or in PDFs?▼

Paywalled pages cannot be fetched and score as WEAK (0.5) with a paywall note. PDF sources may not extract reliably and are flagged for manual verification, while 404 URLs score 0.0 with a suggestion to check web.archive.org.

Is there a limit on how many sources can be checked at once?▼

Yes, the workflow processes a maximum of 10 URLs per run to avoid rate-limiting source servers. If a post cites more than 10 URLs, the first 10 are verified and the remainder are listed as SKIPPED in the report.