fact-checking-explainerslisted

# Fact-Checking Explainers ## Overview An explainer's authority comes from being right. A reader who catches one confident, wrong claim stops trusting the rest of the piece, figures and all. This skill makes "no incorrect claim ships" enforceable by tying every checkable claim to evidence you can point to. It is not a proofreading pass and not advisory: it is the gate an explainer passes before it is delivered. ## The Iron Law ``` NO EXPLAINER SHIPS WITH AN UNVERIFIED FACTUAL CLAIM. ``` Every checkable claim either traces to a source that supports it, gets corrected to match the source, or gets cut. **No exceptions:** - Not for "it's obviously true" - obvious things are wrong often enough; verify. - Not for "I'm pretty sure" - pretty sure is the `unsupported` verdict. Find the source or cut the claim. - Not for "it's just background" - background facts are still facts, and still wrong sometimes. - Not for "the draft is due" - a wrong explainer is worse than a late one. - "Verify" means against an actual source you can point to, not your memory of one. ## When to Use Run this skill: - **At research-time**, over the sources gathered for an explainer, before any drafting. - **Post-draft**, over the finished article, before delivery. This is a blocking gate. - **On request**, whenever asked to fact-check, verify, or audit an explainer or article. `creating-explainers` and `explaining-codebases` both call this skill at the gates above. When they do, the article is not don