blog-fact-checking

Fact-checking blog claims involves comparing your content's assertions about tools, versions, APIs, and configurations against authoritative documentation. This Skill fetches official sources via web_fetch and produces verdicts—Verified, Mismatch, Outdated, or Hallucinated—so you identify what needs correction before publishing.

Yes. This Skill targets specific version claims, API endpoint details, and configuration examples in your writing, then cross-references them against official docs to catch outdated or incorrect technical references that could mislead readers.

You can verify claims about external tools and libraries, version numbers, API signatures, quotes and attributions, configuration syntax, and performance benchmarks. The Skill compares each claim type against referenced sources to flag discrepancies or obsolete information.

By fetching current official documentation and comparing it directly to your claims, fact-checking detects when referenced features no longer exist, versions have changed, or APIs have been deprecated, letting you update content before readers encounter broken or misleading guidance.

The Skill works most effectively when claims reference specific tools or libraries; it uses web_fetch to retrieve official documentation. Providing the section or claim you want checked and naming the tool or source accelerates accurate verification and reduces ambiguity.

The Skill reports the specific mismatch, outdated status, or hallucinated claim with clear feedback so you can revise the content. This targeted reporting saves time by pinpointing exactly what needs attention rather than requiring a full manual review.