Maps gathered sources as supporting, contradicting, or silent on a specific claim so you can assess sourcing strength before publication.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:source-cross-referencerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Takes a specific claim and a list of sources you have gathered, then maps which sources support, contradict, or are silent on the claim — so you can see at a glance whether your sourcing is solid before publication.
Takes a specific claim and a list of sources you have gathered, then maps which sources support, contradict, or are silent on the claim — so you can see at a glance whether your sourcing is solid before publication.
Required: The exact claim you want to cross-reference (one sentence, as it would appear in your story). A list of sources — for each source, paste the relevant excerpt or summarise what it says. Minimum two sources.
Optional: The original context where the claim appears (paragraph or script line). The type of story (news report, documentary, magazine feature, podcast episode). Any known relationship between the sources — for example, if two of them cite the same underlying report.
Two-part output. First, a source comparison table with columns: Source Name / Type (official data, academic study, eyewitness account, etc.) / Position on Claim / Key Quote or Detail / Caveats. Then a short narrative paragraph (three to five sentences) summarising the overall picture: whether the claim is well-corroborated, contested, or undercooked — and what the journalist should do next. Total length: roughly 300–500 words depending on how many sources are provided. Plain language throughout. No legal advice, no editorial opinion beyond the sourcing assessment.
Claim to cross-reference: "Ambulance response times in the city's northern district averaged 14 minutes last year, well above the national benchmark of 8 minutes."
Sources:
Regional health authority annual report — "Mean emergency response time across all districts: 11.3 minutes. Northern district recorded the highest mean at 13.8 minutes."
City council budget committee minutes — Councillor quote: "Paramedic shortages have pushed response times in the north to nearly 15 minutes on some nights, which is unacceptable."
National ambulance standards body — Published benchmark: "Target response time for Category 2 emergencies is 18 minutes mean, with an aspirational target of 8 minutes. The 8-minute standard applies only to Category 1 life-threatening calls."
Investigative piece in a regional newspaper — "Northern district response times hit 14 minutes last year, according to health authority data, more than double the national target."
| Source | Type | Position on Claim | Key Detail | Caveat |
|---|---|---|---|---|
| Regional health authority annual report | Official government data | Partially supports | Records 13.8 min for northern district — close to the claimed 14 min but not identical | Difference of 0.2 min may matter for accuracy |
| City council budget committee minutes | Official meeting record | Partially supports | References "nearly 15 minutes on some nights" — consistent in direction but this is a peak figure, not an annual average | Councillor is not citing a specific statistic; this is anecdotal corroboration |
| National ambulance standards body | Official benchmark | Contradicts the framing | The 8-minute standard applies only to Category 1 (life-threatening) calls, not all emergencies | If your story does not specify call category, the comparison is misleading |
| Regional newspaper | Secondary source | Appears to support | Cites "14 minutes" from health authority data — but is drawing from the same underlying report as your Source 1 | Not independent corroboration; both traces to the same primary source |
Narrative summary: The claim has solid grounding in official data but two problems need fixing before publication. First, the annual report shows 13.8 minutes, not 14 — a small difference but worth correcting to avoid accuracy challenges. More significantly, the "8-minute national benchmark" framing is contested: the standards body defines that target for life-threatening Category 1 calls only. If the story is comparing all-category averages against a Category 1 target, the comparison is misleading and legally and editorially risky. The regional newspaper piece does not add independent corroboration — it draws on the same health authority data. Recommended next step: confirm the call-category breakdown from the health authority before finalising the claim, and either narrow the benchmark comparison to Category 1 calls or use the 18-minute mean target instead.
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsProduces structured verification briefs for claims, breaking down assertions, identifying source types, red flags, and editorial judgment framework.
Extracts and verifies factual claims from PR copy or journalistic drafts, providing citations and warning on low certainty. Use before sending pitches or press releases.
Corroborates claims against external URLs by fetching content with smart-fetch or WebFetch, analyzing credibility, and recording findings as evidence or risks. Useful for verifying statements in code docs or research.