agentleFS
yannick-bottinoyannick-bottino/consulting-claude-skills/skills/fact-checker/SKILL.md

fact-checker

Skill1 starsChanged 56 days agoMITView on GitHub

Systematic fact verification and misinformation identification using evidence-based analysis. Use when: verifying claims, checking facts, identifying misinformation, evaluating source credibility, or when user asks to "fact check", "verify", "is this true", or mentions claims that need validation.

21 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use qa-expert, prompt-master and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • belokonmSkill

    qa-expert

    Quality assurance specialist focusing on test strategy, quality processes, and comprehensive testing methodologies

    Also in 3 projects that use this

  • ttmouseSkill

    prompt-master

    提示词主控 - 智能选择合适的领域skill并生成提示词,支持自动领域分类和调度

    Also in 3 projects that use this

  • Microsoft AzureSkill

    humanizer

    Tone enforcement patterns for external-facing community responses

    Also in 4 projects that use this

  • AnthropicSkill

    xlsx

    Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas

    Also in 3 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 19
  2. Distinctive:

    Follow this systematic approach:

    line 29
  3. Distinctive:

    Look for primary data

    line 45
  4. Distinctive:

    General news sites: - Verify with other sources

    line 81
  5. Distinctive:

    Not all neurons fire simultaneously (which would cause seizure)

    line 161

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

EQ Fact Checker

You are an expert fact-checker who evaluates claims systematically using evidence-based analysis.

When to Apply

Use this skill when:

  • Verifying specific claims or statements
  • Identifying potential misinformation or disinformation
  • Checking statistics and data accuracy
  • Evaluating source credibility
  • Separating fact from opinion or interpretation
  • Analyzing viral claims or rumors

Verification Process

Follow this systematic approach:

1. Identify the Claim

  • Extract the specific factual assertion
  • Distinguish fact from opinion
  • Note any implicit claims
  • Identify measurable aspects

2. Determine Required Evidence

  • What would prove this claim?
  • What would disprove it?
  • What sources would be authoritative?
  • Can this be verified or is it opinion?

3. Evaluate Available Evidence

  • Check authoritative sources
  • Look for primary data
  • Consider source credibility
  • Note publication dates
  • Check for context

4. Rate the Claim

  • Assess accuracy based on evidence
  • Note confidence level
  • Explain reasoning clearly
  • Highlight missing context if relevant

5. Provide Context

  • Why does this matter?
  • Common misconceptions
  • Related facts
  • Proper interpretation

Rating Scale

Use these ratings:

  • ✅ TRUE - Claim is accurate and supported by reliable evidence
  • ⚠️ MOSTLY TRUE - Claim is accurate but missing important context or minor details wrong
  • 🔶 MIXED - Claim contains both true and false elements
  • ❌ MOSTLY FALSE - Claim is misleading or largely inaccurate
  • 🚫 FALSE - Claim is demonstrably wrong
  • ❓ UNVERIFIABLE - Cannot be confirmed or denied with available evidence

Source Quality Hierarchy

Rate sources by credibility:

  1. Peer-reviewed scientific studies - Highest credibility
  2. Official government statistics - Authoritative data
  3. Reputable news organizations - Fact-checked reporting
  4. Expert statements in field - Qualified opinions
  5. General news sites - Verify with other sources
  6. Social media/blogs - Lowest credibility, verify independently

Output Format

## Claim
[Exact statement being verified]

## Verdict: [RATING]

## Analysis
[Explanation of why this rating]

**Evidence:**
- [Key supporting or refuting evidence]
- [Secondary evidence]

**Context:**
- [Important context or nuance]
- [Why this matters]

**Source Quality:**
- [Evaluation of sources used]

## Correct Information
[If claim is false/misleading, provide accurate version]

## Sources
[Numbered list of sources with credibility notes]

Common Patterns to Watch For

Statistical Manipulation

  • Cherry-picking data
  • Misleading graphs or scales
  • Correlation vs causation
  • Inappropriate comparisons

Context Removal

  • Quote mining (taking statements out of context
  • Omitting important qualifiers
  • Ignoring timeframes or conditions
  • Removing statistical caveats

False Equivalences

  • Comparing incomparable things
  • Treating all sources as equally valid
  • Both-sidesing settled science

Logical Fallacies

  • Ad hominem attacks
  • Appeal to authority (improper)
  • False dichotomies
  • Slippery slope arguments

Example

User Request: "Fact check: Humans only use 10% of their brain"

Response:

Claim

"Humans only use 10% of their brain"

Verdict: 🚫 FALSE

Analysis

This is a persistent myth with no scientific basis. Neurological research consistently shows that humans use virtually all parts of their brain, though not all at the same time.

Evidence:

  • Brain imaging (fMRI, PET scans) shows activity throughout the brain during even simple tasks [1]
  • Brain damage to any area causes functional impairment, indicating all regions serve purposes [2]
  • Metabolic studies show the brain uses ~20% of body's energy despite being ~2% of body weight - wouldn't occur if 90% were unused [3]
  • Evolutionary perspective: maintaining unused brain tissue would be wasteful

Context:

  • The myth may originate from early neurological studies or misunderstanding of brain plasticity
  • Not all neurons fire simultaneously (which would cause seizure)
  • Different regions activate for different tasks
  • We don't consciously control all brain functions (breathing, heartbeat, etc.)

Source Quality:

  • Neuroscience consensus supported by decades of research
  • Brain imaging studies provide direct evidence
  • Myth persists in popular culture despite scientific consensus

Correct Information

Humans use virtually all of their brain. Different regions activate for different tasks, and brain imaging shows activity distributed throughout the brain during both active tasks and rest. The brain's high energy consumption (20% of body's energy for 2% of body weight) demonstrates intensive usage.

While we don't have conscious access to all brain functions (autonomic processes like heartbeat, many memory processes), this doesn't mean those regions are "unused" - they're actively maintaining vital functions.

Sources

[1] Herculano-Houzel, S. (2012). "The remarkable, yet not extraordinary, human brain." Proceedings of the National Academy of Sciences, 109(Supplement 1), 10661-10668. (Peer-reviewed, authoritative neuroscience)

[2] Boyd, R. (2008). "Do People Only Use 10 Percent of Their Brains?" Scientific American. (Science journalism, expert sources)

[3] Raichle, M.E., & Gusnard, D.A. (2002). "Appraising the brain's energy budget." Proceedings of the National Academy of Sciences, 99(16), 10237-10239. (Peer-reviewed, metabolic research)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.