CommunityProgramación y desarrollogithub.com

fact-checker

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.

Compatible con~Claude Code~Codex CLI~Cursor
npx add-skill https://github.com/Shubhamsaboo/awesome-llm-apps/tree/main/awesome_agent_skills/fact-checker

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)

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

academic-researcher

Academic research assistant for literature reviews, paper analysis, and scholarly writing. Use when: reviewing academic papers, conducting literature reviews, writing research summaries, analyzing methodologies, formatting citations, or when user mentions academic research, scholarly writing, papers, or scientific literature.

code-reviewer

Thorough code review with focus on security, performance, and best practices. Use when: reviewing code, performing security audits, checking for code quality, reviewing pull requests, or when user mentions code review, PR review, security vulnerabilities, performance issues.

content-creator

Creates engaging content for blogs, social media, and marketing materials with audience focus. Use when: writing blog posts, creating social media content, developing marketing copy, crafting engaging headlines, or when user mentions content creation, blogging, social media, or audience engagement.

content-writer

Writes marketing copy for landing pages, emails, and social media posts. Use when creating promotional content, sales copy, or brand messaging.

data-analyst

SQL, pandas, and statistical analysis expertise for data exploration and insights. Use when: analyzing data, writing SQL queries, using pandas, performing statistical analysis, or when user mentions data analysis, SQL, pandas, statistics, or needs help exploring datasets.

debugger

Systematic debugging and root cause analysis for identifying and fixing software issues. Use when: debugging errors, troubleshooting bugs, investigating crashes, analyzing stack traces, fixing broken code, or when user mentions debugging, error, bug, crash, or "not working".

decision-helper

Structured decision-making frameworks for evaluating options and making informed choices. Use when: making decisions, evaluating options, weighing trade-offs, or when user needs help choosing between alternatives, analyzing pros/cons, or making structured decisions.

deep-research

Comprehensive research assistant that synthesizes information from multiple sources with citations. Use when: conducting in-depth research, gathering sources, writing research summaries, analyzing topics from multiple perspectives, or when user mentions research, investigation, or needs synthesized analysis with citations.

editor

Professional editing and proofreading for clarity, grammar, style, and readability improvements. Use when: editing text, proofreading documents, improving clarity, fixing grammar, refining style, or when user asks to "edit", "proofread", "improve", "revise", or mentions grammar and readability.

email-drafter

Professional email composition for business communication across various contexts. Use when: writing emails, drafting professional messages, composing replies, or when user mentions email, message drafting, or needs help with business correspondence.

fullstack-developer

Modern web development expertise covering React, Node.js, databases, and full-stack architecture. Use when: building web applications, developing APIs, creating frontends, setting up databases, deploying web apps, or when user mentions React, Next.js, Express, REST API, GraphQL, MongoDB, PostgreSQL, or full-stack development.

meeting-notes

Structured meeting summaries with action items, decisions, and key discussion points. Use when: taking meeting notes, summarizing discussions, tracking action items, or when user mentions meeting notes, minutes, action items, or needs structured meeting documentation.

project-planner

Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones. Use when: planning projects, creating task breakdowns, defining milestones, estimating timelines, managing dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.

python-expert

Senior Python developer expertise for writing clean, efficient, and well-documented code. Use when: writing Python code, optimizing Python scripts, reviewing Python code for best practices, debugging Python issues, implementing type hints, or when user mentions Python, PEP 8, or needs help with Python data structures and algorithms.

sprint-planner

Agile sprint planning with story estimation, capacity planning, and sprint goal setting. Use when: planning sprints, estimating stories, defining sprint goals, managing sprint backlogs, or when user mentions sprint planning, agile, scrum, story points, or sprint capacity.

strategy-advisor

High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.

technical-writer

Creates clear documentation, API references, guides, and technical content for developers and users. Use when: writing documentation, creating README files, documenting APIs, writing tutorials, creating user guides, or when user mentions documentation, technical writing, or needs help explaining technical concepts clearly.

ux-designer

Expert UX design assistance for user research, wireframing, prototyping, and design strategy. Use when: creating wireframes, conducting user research, building prototypes, designing user flows, writing UX copy, reviewing designs for usability, creating personas, planning usability tests, or when user mentions UX design, user experience, wireframes, prototypes, user research, information architecture, or design systems.

visualization-expert

Chart selection and data visualization guidance for effective data communication. Use when: creating visualizations, choosing chart types, designing dashboards, or when user mentions data visualization, charts, graphs, or needs help presenting data visually.

Skills relacionados