coverage-check
Count how many independent origins are behind news coverage of a claim, instead of counting URLs. Queries GDELT for matching articles, collapses reprints and wire copy into single origins, and flags publication bursts that indicate syndication. Use when a claim appears to be confirmed by many outlets and you need to know whether that's many sources or one source many times.
npx skills add SerhiiKorniienko/bullshit-detector --skill coverage-check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# coverage-check Ten URLs are not ten sources. This turns "lots of outlets reported it" into a number you can defend. ## When to reach for it During claim verification, when a claim looks *corroborated by volume* — a pile of search results all saying the same thing. That pattern has two very different causes: - Many newsrooms independently established the fact → genuinely strong evidence - One pre
What does the coverage-check skill do?
Count how many independent origins are behind news coverage of a claim, instead of counting URLs. Queries GDELT for matching articles, collapses reprints and wire copy into single origins, and flags publication bursts that indicate syndication. Use when a claim appears to be confirmed by many outlets and you need to know whether that's many sources or one source many times.
How do I install it?
Run `npx skills add SerhiiKorniienko/bullshit-detector --skill coverage-check --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 SerhiiKorniienko/bullshit-detector, a repository with 104 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.