Agent skill

Fact Check

by jwynia in jwynia/agent-skills

Verify claims in generated output against sources. An agent skill from jwynia/agent-skills.

MITAuto-check passedResearch & Science

Install Fact Check

skills CLI
$ npx skills add jwynia/agent-skills --skill fact-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills fact-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/general/research/verification/fact-check .claude/skills/fact-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fact-check
GitHub stars
170
Token cost
~2.9k tokens
SKILL.md length
1,184 words
Files
1
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Verify claims in generated output against sources. An agent skill from jwynia/agent-skills.

  • Works in 10 steps: Claim Extraction → Claim Categorization → Source Verification → …
  • Tasks that involve Fact-checking and source verification
  • SKILL.md covers Why Separate Passes Matter, Diagnostic States, The Verification Process and Hallucination Patterns, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fact Check is an agent skill from jwynia/agent-skills. Verify claims in generated output against sources. Use as a separate pass AFTER content generation to catch hallucinations. Critical constraint - cannot be reliably combined with generation in a single pass.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Fact-checking and source verification. The licence is MIT.

When your agent uses it

  • Tasks that involve Fact-checking and source verification

Example prompts

  • “/fact-check”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Claim Extraction
  2. Claim Categorization
  3. Source Verification
  4. Confidence Assignment
  5. Plausible Fabrication
  6. Confident Extrapolation
  7. Temporal Confusion
  8. Attribution Drift
  9. Amalgamation
  10. Precision Inflation

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fact Check loads about 2.9k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 1,184 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 1,184 words, ~2,855 tokens.

Download SKILL.mdSave it as .claude/skills/fact-check/SKILL.md (or your agent's skills folder).
name
fact-check
description
Verify claims in generated output against sources. Use as a separate pass AFTER content generation to catch hallucinations. Critical constraint - cannot be reliably combined with generation in a single pass.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.domain
research
metadata.cluster
methodology
metadata.type
diagnostic
metadata.mode
evaluative

Fact-Check Skill

Systematic verification of claims in generated content. Designed to catch hallucinations, confabulations, and unsupported assertions.

Why Separate Passes Matter

The Fundamental Problem: LLMs generate plausible-sounding content by predicting what should come next. This same mechanism produces hallucinations—confident statements that feel true but aren't. An LLM in generation mode cannot reliably catch its own hallucinations because:

  1. Attention is on generation, not verification
  2. Coherence pressure makes false claims feel correct in context
  3. Same weights that produced the error will confirm it
  4. No external grounding to contradict the confabulation

The Solution: Verification must be a separate cognitive pass with:

  • Fresh attention focused solely on each claim
  • Explicit source checking (not memory/training data)
  • Adversarial stance toward the content
  • External grounding where possible

Diagnostic States

F1: No Verification Pass

Symptoms: Content generated and delivered without any fact-checking. Risk: Hallucinations pass through undetected. Intervention: Run verification pass before delivery. Extract claims, check each against sources.

F2: Self-Verification (Invalid)

Symptoms: Same pass asked to "check your facts" while generating. Risk: False confidence—errors confirmed by same process that created them. Intervention: Complete generation first, then run separate verification pass with explicit source requirements.

F3: Memory-Based Verification (Unreliable)

Symptoms: Claims checked against "what I know" without external sources. Risk: Hallucinations verified by hallucinated knowledge. Intervention: Require explicit source citation for each verified claim. If no source available, mark as unverified.

F4: Selective Verification

Symptoms: Only some claims checked; others assumed correct. Risk: Unchecked claims may contain errors. Intervention: Systematic extraction of ALL verifiable claims. Check each, or explicitly mark unchecked items.

F5: Verification Complete

Symptoms: All claims extracted, each checked against sources, confidence levels assigned. Indicators: Source citations present, unverified claims marked, confidence explicit.

The Verification Process

Phase 1: Claim Extraction

Extract every verifiable statement from the content.

Claim types to extract:

  • Factual assertions ("X is Y", "X causes Y")
  • Statistics and numbers ("40% of...", "in 2023...")
  • Attributions ("According to X...", "Research shows...")
  • Definitions ("X means...", "X is defined as...")
  • Historical claims ("X happened in...", "X was founded by...")
  • Causal claims ("X leads to Y", "X prevents Y")
  • Comparative claims ("X is better than Y", "X is the largest...")

What to skip:

  • Opinions clearly marked as such
  • Hypotheticals and speculation (if labeled)
  • Logical deductions from stated premises
  • Direct quotes (verify attribution, not content)
Phase 2: Claim Categorization

Categorize each claim by verifiability:

CategoryDescriptionVerification Strategy
Verifiable-HardNumbers, dates, names, quotesMust match source exactly
Verifiable-SoftGeneral facts, processes, mechanismsSource should substantially support
Attribution"X said...", "According to..."Verify source exists and said something similar
InferenceConclusions drawn from evidenceVerify premises, assess reasoning
Opinion-as-FactSubjective claim stated as objectiveFlag for rewording or qualification
Phase 3: Source Verification

For each claim, attempt verification:

markdown
## Claim Verification Log

### Claim 1: "[exact claim text]"
- **Category:** [Verifiable-Hard/Soft/Attribution/Inference]
- **Source checked:** [specific source]
- **Finding:** [Confirmed/Partially supported/Not found/Contradicted]
- **Confidence:** [High/Medium/Low]
- **Notes:** [discrepancies, qualifications needed]

### Claim 2: ...

Verification outcomes:

OutcomeMeaningAction
ConfirmedSource explicitly supports claimKeep, cite source
Partially supportedSource supports part, not allQualify or narrow claim
Not foundNo source locatedMark unverified, consider removing
ContradictedSource says oppositeRemove or correct
OutdatedSource is dated; current state may differUpdate or add recency caveat
Phase 4: Confidence Assignment

Assign overall confidence to the content:

LevelCriteria
HighAll key claims verified; no contradictions found
MediumMost claims verified; some unverified but plausible
LowSignificant claims unverified; some corrections needed
UnreliableMultiple contradictions found; major revision needed

Hallucination Patterns

Common hallucination types to watch for:

1. Plausible Fabrication

Pattern: Specific details that sound right but don't exist. Examples: Fake paper citations, non-existent statistics, invented quotes. Detection: Verify specific claims against primary sources.

2. Confident Extrapolation

Pattern: Reasonable inference stated as established fact. Examples: "Studies show..." (no specific study), "Experts agree..." (no citation). Detection: Require specific source for any claim of external support.

3. Temporal Confusion

Pattern: Mixing information from different time periods. Examples: Old statistics presented as current, defunct organizations described as active. Detection: Check dates on sources, verify current status.

4. Attribution Drift

Pattern: Correct information attributed to wrong source. Examples: Quote assigned to wrong person, finding attributed to wrong study. Detection: Verify attribution specifically, not just content.

5. Amalgamation

Pattern: Combining details from multiple sources into one fictional source. Examples: Invented study that combines real findings from separate papers. Detection: Verify the specific source exists and contains all attributed claims.

Show full SKILL.md (482 more words)Show less
6. Precision Inflation

Pattern: Adding false precision to vague knowledge. Examples: "Approximately 47.3%" when only "about half" is supported. Detection: Check if source actually provides that level of precision.

Verification Checklist

Before releasing fact-checked content:

  • Claims extracted? All verifiable statements identified
  • Sources checked? Each claim verified against external source
  • Specific, not memory? Verification used actual sources, not LLM training data
  • Contradictions flagged? Conflicts between claims and sources noted
  • Unverified marked? Claims without sources explicitly identified
  • Confidence stated? Overall reliability level communicated
  • Separate pass? Verification done after generation, not during

Integration with Research Skill

Research PhaseFact-Check Role
During researchVerify claims in sources themselves
After synthesisVerify that synthesis accurately represents sources
Before deliveryFinal pass to catch hallucinations in output

Handoff pattern:

  1. Research skill gathers and synthesizes information
  2. Content is generated based on research
  3. Fact-check skill runs as separate pass
  4. Corrections made, confidence assigned
  5. Output delivered with verification status

Operational Constraints

What This Skill Cannot Do
  1. Verify during generation — Must be separate pass
  2. Catch all hallucinations — Some may slip through
  3. Verify without sources — No sources = unverified, not "verified by knowledge"
  4. Replace domain expertise — Can check sources exist, not evaluate quality
When Verification Is Most Critical
ContextVerification Level
Published contentFull verification required
Decision supportKey claims must be verified
Educational contentHigh accuracy expected
Casual conversationLight verification acceptable
Creative fictionN/A (different standards)

Anti-Patterns

PatternProblemFix
"I'm confident"Confidence ≠ accuracyRequire source citation
"To the best of my knowledge"Memory is unreliableCheck external source
"Generally speaking"Vagueness hides uncertaintyBe specific or mark unverified
"Research shows"Which research?Cite specific source
Verify-while-generatingSame pass can't catch own errorsSeparate passes mandatory
Check one, assume restPartial verificationCheck all or mark unchecked

Output Format

When delivering fact-checked content:

markdown
## [Content Title]

[Content body with claims]

---

### Verification Status

**Overall Confidence:** [High/Medium/Low]

**Verified Claims:**
- [Claim 1] — Source: [citation]
- [Claim 2] — Source: [citation]

**Unverified Claims:**
- [Claim 3] — No source found; treat as uncertain

**Corrections Made:**
- [Original claim] → [Corrected claim] (Source: [citation])

**Caveats:**
- [Any limitations or qualifications]

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:
    • "Where should I save output from this fact-check session?"
    • Suggest: explorations/fact-check/ or a sensible location for this project
  4. Store the user's preference:
    • In context/output-config.md if context network exists
    • In .fact-check-output.md at project root otherwise
Primary Output

For this skill, persist:

  • Claims extracted - all verifiable statements identified
  • Verification results - each claim with source and status
  • Confidence assessment - overall content reliability
  • Corrections made - any changes from original
Conversation vs. File
Goes to FileStays in Conversation
Verification status reportDiscussion of sources
Claim-by-claim resultsClarifying questions
Confidence assessmentVerification process
Corrections and caveatsReal-time feedback
File Naming

Pattern: {content-name}-factcheck-{date}.md Example: research-synthesis-factcheck-2025-01-15.md

Source Framework

This skill extends the research cluster with post-generation verification. Distinct from research (which gathers information) and operates as quality control on output.

Related: skills/research/SKILL.md (pre-generation), references/doppelganger/ (truth hierarchies)

© jwynia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/general/research/verification/fact-check of jwynia/agent-skills.

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Fact Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fact Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fact Check this skilljwynia/agent-skills170—~2.9kAutomated safety check: PassMIT
Perplexity Web Searchdavila7/claude-code-templates33k11 repos~3.5kAutomated safety check: NotesMIT
Citation Verification GuideGalaxy-Dawn/claude-scholar5.7k2 repos~1.9kAutomated safety check: PassMIT
Article Fact Checkerdigoal/blog8.6k—~939Automated safety check: PassGPL-2.0
Deep Research Agent TeamImbad0202/academic-research-skills51k—~13kAutomated safety check: PassCustom licence
Docs Grounding Verifiermicrosoft/apm4k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Perplexity Web Search

    davila7/claude-code-templates

    Runs web-grounded searches through Perplexity's Sonar models over OpenRouter for current events, recent literature and cited facts beyond the model's training cutoff.

    33k GitHub starsUsed in 11 repos~3.5k tokens
    Research & ScienceAuto-check: notes
  • Citation Verification Guide

    Galaxy-Dawn/claude-scholar

    Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.

    5.7k GitHub starsUsed in 2 repos~1.9k tokens
    Research & ScienceAuto-check passed
  • 三层审查模型,逐段逐句验证文章真伪、证据链与逻辑结构。Use when the user asks to fact-check, verify, audit, or evaluate the credibility of an article, essay, report, opinion piece, social-media post, or any written claim —…

    8.6k GitHub stars~939 tokensUpdated 2 days ago
    Research & ScienceAuto-check passed
  • Deep Research Agent Team

    Imbad0202/academic-research-skills

    Runs a 13-agent pipeline for rigorous academic research, from forming the question through systematic search, synthesis, bias checks and an APA 7.0 report.

    51k GitHub stars~13k tokensUpdated today
    Research & ScienceAuto-check passed
  • Official

    A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.

    4k GitHub stars~1.9k tokensUpdated yesterday
    Research & ScienceAuto-check passed
  • Fact Checking

    bradygaster/squad

    Review and validate claims using counter-hypothesis testing.

    3.3k GitHub stars~503 tokensUpdated yesterday
    Research & ScienceAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    170 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    170 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    170 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Fact Check

What does Fact Check do?

Verify claims in generated output against sources. An agent skill from jwynia/agent-skills. Fact Check is an agent skill from jwynia/agent-skills. Verify claims in generated output against sources.

When should I use Fact Check?

Fact Check fits situations like: tasks that involve Fact-checking and source verification.

How do I install Fact Check in Claude Code?

Run `npx skills add jwynia/agent-skills --skill fact-check -a claude-code`. Or copy the skill folder (skills/general/research/verification/fact-check in jwynia/agent-skills) into .claude/skills/fact-check in your project. Claude Code loads it when a task matches its description.

How do I install Fact Check in Codex?

Run `npx skills add jwynia/agent-skills --skill fact-check -a codex`. Or copy the skill folder (skills/general/research/verification/fact-check in jwynia/agent-skills) into .agents/skills/fact-check in your project. Codex loads it when a task matches its description.

Can I use Fact Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jwynia/agent-skills --skill fact-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fact-check, .gemini/skills/fact-check, .github/skills/fact-check and .opencode/skills/fact-check in your project.

What does Fact Check need to run?

SKILL.md names no scripts, command-line tools or credentials: Fact Check is instructions for the agent only.

Does Fact Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fact Check safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fact Check use?

Fact Check is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fact Check use?

About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fact Check?

Skills that share tags, products or a category with Fact Check: Perplexity Web Search (davila7/claude-code-templates, 33k stars), Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Article Fact Checker (digoal/blog, 8.6k stars) and Deep Research Agent Team (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fact Check?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

Source: jwynia/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.