Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Fact Checker

ASecurity

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.

428 stars
0 votes
0 copies
1 views
Added 9/20/2026
ai-agentsgo

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/20/2026

$npx -y skills add aiskillstore/marketplace --skill fact-checker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fact Checker?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Fact Checker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-fact-checker/badge)](https://www.skillsdirectory.com/skills/aiskillstore-fact-checker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: fact-checker
description: |
  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.
license: MIT
metadata:
  author: awesome-llm-apps
  version: "1.0.0"
---

# 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

```markdown
## 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)

Attribution

aiskillstoreaiskillstore
View sourceSee grades on GitHubMore from aiskillstore →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →