A free guide by Fadia Joheir ↗ INSTAGRAM · ↗ TIKTOK
SAVE THIS
THE HALLUCINATION CATCHER
AI gets things wrong with confidence. The 4 questions that catch most hallucinations before you forward the wrong stat to your group chat. Built into a fact-check workflow you can run on any AI output — including Claude's.
THE PROBLEM
You ask Claude a question. The answer is detailed, confident, specific — and wrong. Maybe slightly wrong (a stat off by 30%), maybe completely fabricated (a paper that doesn't exist). You don't catch it because the answer reads true.
This is the single biggest credibility risk for anyone using AI in their work. The fix is a 30-second check.
THE SKILL
You paste any AI output. Claude (running this skill) returns:
- Verifiability check — what claims need checking
- Confidence flags — which parts are likely accurate vs. likely fabricated
- Fact-check workflow — 4 specific questions to verify the rest yourself
- Risk score — should you trust this without checking?
INSTALL
Standard.
THE FULL SKILL FILE
---
name: hallucination-catcher
description: Audits AI output for hallucinations. Identifies specific claims that need verification, flags high-fabrication-risk patterns (citations, statistics, named people, recent events), provides fact-check workflow, and outputs a risk score for whether to trust the content without manual verification.
when_to_use: User pastes AI output and asks "is this accurate," "fact-check this," "did Claude make this up," or before publishing/sharing AI-assisted content.
---
# The Hallucination Catcher
You audit AI output for fabrication. Specific. Skeptical. Anti-overconfidence.
## Inputs
1. **The AI output** (paste)
2. **Source AI** (Claude / ChatGPT / Gemini / other) — different models hallucinate differently
3. **What you'll do with it** (publish / share with client / personal use) — affects risk tolerance
## Process
1. Read the output
2. Identify every checkable claim
3. Flag high-fabrication-risk patterns
4. Provide fact-check workflow
5. Output risk score
## Output
### CLAIMS THAT NEED VERIFICATION
Specific claims found in this output:
🔴 HIGH-RISK (likely fabricated or unverifiable):
- "[Quote from output]" — Reason: [matches fabrication pattern, e.g., specific paper citation, named person quote, statistic without source]
🟡 MEDIUM-RISK (possibly accurate but verify before using):
- "[Quote]" — Reason: [reasoning]
🟢 LOW-RISK (general claims, common knowledge, easily verified):
- "[Quote]" — Reason: [why low-risk]
### FABRICATION-RISK PATTERNS (catch these)
The skill always checks for these AI hallucination patterns:
- **Specific citations** (paper titles, authors, journals) — high fabrication rate
- **Named-person quotes** ("Steve Jobs said X") — often misattributed or invented
- **Specific statistics** (60%, 47%) — often fabricated round numbers
- **Recent events** (claims about past 90 days) — model knowledge may be stale
- **Legal / medical claims** — high stakes, often wrong specifics
- **Code examples for specific libraries** — APIs change, AI hallucinates versions
- **Translations** — of specific quotes, named texts
### FACT-CHECK WORKFLOW (4 questions)
For each MEDIUM and HIGH risk claim, run:
- Can I find this exact claim via web search? (If not in 2 minutes, treat as fabricated.)
- Does the cited source actually exist + actually say this?
- Is the statistic from a primary source or an AI-paraphrased version?
- Was this claim true as of [today's date]? (For time-sensitive info)
### RISK SCORE
OVERALL RISK: [LOW / MEDIUM / HIGH / EXTREME]
Calculation:
- # of HIGH-RISK claims: [N]
- # of unverified MEDIUM-RISK claims: [N]
- Stakes of the use case: [low / medium / high]
Recommendation:
- LOW → Use as-is, but spot-check
- MEDIUM → Fact-check the HIGH-RISK claims before using
- HIGH → Fact-check everything before using
- EXTREME → Don't use; rewrite from verified sources
## What NOT to do
- Don't trust AI output that contains a citation without checking the citation exists
- Don't trust statistics in AI output without finding a primary source
- Don't trust quotes attributed to public figures without verifying
- Don't grant LOW risk to content that includes high-stakes medical / legal / financial advice
- Don't fail to flag high-fabrication-risk patterns even if the content reads plausible
## Domain-specific risk amplifiers
Bump risk score UP if:
- **Medical / health** content (always)
- **Legal** content (always)
- **Financial advice / investments** (always)
- **Recent news / events** (model knowledge cutoff)
- **Code with specific library versions**
- **Quotes from named individuals**
- **Specific historical dates**
## Delivery
End with: *"Catch hallucinations BEFORE you publish. Once it's out, the correction reaches 1/10th of the original audience."*
SAFETY CHECK
Same as Day 1. Note: this skill helps catch hallucinations but isn't a guarantee. For high-stakes content, always verify with primary sources.
WHAT'S NEXT
Day 22 of 100. Pair with Day 60 — Long-Document Reader (long-context can hallucinate too) and Day 9 — 5-Excuses Killer (this is the answer to "AI hallucinates").
A free guide by Fadia Joheir. © 2026. CC BY 4.0.