agentsclimarketplace
Sign in

Fact checker

Skill radustefandumitru/overdrive/skills/fact-checker

Check factual claims in writing against credible sources, rate support levels, and suggest safer wording or better citations. Use for blog posts, landing pages, reports, social posts, research summaries, investor materials, SEO content, or any output with claims, stats, studies, or factual assertions.From its SKILL.md

Install
npx -y skills add radustefandumitru/overdrive --skill fact-checker

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 526 tokens by cl100k_base, as published. Nobody here has run it

Fact Checker

Use this skill to separate claims that are supported, weakly supported, misleading, outdated, or unverifiable.

This is an original Overdrive skill inspired by public discussion of claim-checking skills. Do not copy unavailable or non-resolving upstream skill text.

Claim Categories

Extract and review:

  • numerical claims and statistics
  • causal claims
  • comparative claims
  • quotes and attributions
  • legal, medical, financial, or safety claims
  • product claims and benchmarks
  • historical/current-event claims
  • source-dependent claims such as "studies show" or "experts say"

Ignore purely subjective opinions unless they are presented as fact.

Source Hierarchy

Prefer sources in this order:

  1. Primary sources, official docs, standards, public filings, datasets, papers, or legal/regulatory text.
  2. Reputable secondary sources that cite primary evidence.
  3. Established news/research organizations with visible methodology.
  4. Company blogs or vendor docs for claims about their own products.
  5. Social posts, forums, marketing pages, and unverified blogs only as weak context.

For current, legal, medical, financial, political, market, software-version, or high-stakes claims, use current web/official sources instead of memory.

Ratings

Use these ratings:

  • TRUE: directly supported by strong sources.
  • MOSTLY TRUE: supported with minor caveats or wording issues.
  • MIXED: partly supported but missing context or overgeneralized.
  • UNSUPPORTED: plausible but not verified by adequate sources.
  • FALSE: contradicted by reliable sources.
  • UNVERIFIABLE: cannot be checked from available evidence.

Output Contract

Return a table when practical:

ClaimRatingEvidenceSafer wording / action

Then provide:

  • highest-risk claims
  • missing citations
  • recommended rewrites
  • source list
  • remaining uncertainty

Rewrite Rules

  • Preserve the user's intended meaning where possible.
  • Replace overconfident claims with scoped, sourced wording.
  • Remove unsupported numbers instead of inventing citations.
  • Use date-specific wording for time-sensitive facts.
  • Do not bury high-risk uncertainty in footnotes.

Pairings

  • Pair with last30days for recent events.
  • Pair with reddit-research when checking community sentiment, but do not treat Reddit as primary evidence.
  • Pair with content-research-writer for sourced long-form content.
  • Pair with humanizer only after factual corrections are complete.

What ships with it: 1 file

454 B alongside SKILL.md

agents/

Gives 0 of the 12 instructions most quality gates skills give in 526 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

  • Read full output and check exit codein 45 of 1524, across 40 files
  • Verify output confirms the claimin 44 of 1524, across 39 files
  • Identify the command that proves the claimin 43 of 1524, across 39 files
  • Execute the full verification commandin 36 of 1524, across 30 files
  • Produce a verification reportin 34 of 1524, across 18 files
  • Review git diff changesin 30 of 1524, across 16 files
  • Fix build failures immediatelyin 29 of 1524, across 9 files
  • Group findings by severityin 28 of 1524
  • State claim only with evidencein 27 of 1524, across 22 files
  • Verify regression tests with red-green cyclein 26 of 1524, across 22 files
  • Run the full test suitein 26 of 1524, across 25 files
  • Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

  • Extract all numerical and causal claims
  • Use current web sources for high-stakes claims
  • Rate claims using the defined support scale
  • Replace overconfident claims with scoped wording
  • List highest-risk claims and missing citations

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.