Skip to content
Development
Skill

/verifying-claims

Verifies claims and assesses source credibility. Use when fact-checking claims, verifying accuracy, validating sources, detecting hallucinations, triangulating evidence, or performing SIFT or RADAR assessment.

From plugin
rageatc-oss
1145 skills11 agents

Claude Code

$ npx -y skills add isvlasov/rageatc-oss --skill verifying-claims --agent claude-code

SKILL.md

verifying-claims.SKILL.md
name: verifying-claims
description: Verifies claims and assesses source credibility. Use when fact-checking claims, verifying accuracy, validating sources, detecting hallucinations, triangulating evidence, or performing SIFT or RADAR assessment.

Verifying Claims

Medium freedom: follow the phases sequentially (extract → mode → assess sources → weight → triangulate → resolve conflicts → calibrate), adapting verification depth to claim significance and risk.

Non-negotiable standards:

  • Identical verification standards for all claims (non-partisanship)
  • Document every source consulted — transparent audit trail
  • Calibrated confidence language; never present uncertain claims as certain
  • Surface disagreements between authoritative sources rather than hiding them
  • Primary sources over secondary, secondary over tertiary

Phase 1 — Extract and categorise claims

**Extract** discrete, verifiable assertions: statements presented as fact; names, dates, numbers, statistics, events; asserted causal relationships and predictions; factual claims embedded in interpretive passages.

Example: "The UK's ageing population, which reached 67.3 million in 2021, will strain healthcare resources" yields three claims — population 67.3 million in 2021 (factual), population ageing (factual, needs definition), will strain healthcare (interpretive/predictive).

**Categorise** each claim:

  • **Factual/verifiable** — provable with objective evidence (statistics, dates, events, findings) → full verification
  • **Interpretive/analytical** — facts plus judgement (causal claims, predictions, impact assessments) → verify the factual basis, assess the reasoning
  • **Opinion** — values, beliefs, preferences, aesthetics → do not fact-check; flag as opinion

**Filter uncheckable claims** and note why: future predictions, personal experiences, vague claims ("many people believe…"), hypotheticals.

**Prioritise** by significance (affects key conclusions or decisions), specificity, risk, and feasibility.

Phase 2 — Select verification mode

**Mode A — Retrospective (sources provided).** Check claims against provided documents; the standard mode for detecting extrinsic hallucinations in AI-generated content. Compare each claim systematically against the sources and flag:

  • **Contradiction** — claim conflicts with sources (high severity)
  • **Unsupported** — sources should cover it but don't (medium severity)
  • **Supported** — explicitly backed by the sources (low/none)

Check: are statistics and numbers present in the sources? Are quotes actually from the cited source? Are causal claims supported? Are dates, names, and details consistent? Does the output acknowledge limitations the sources mention? Is its confidence calibrated to source certainty?

AI-specific detection methods: `references/hallucination-detection.md`.

**Mode B — Proactive (find sources).** No sources provided, or provided sources insufficient. Apply SIFT:

  • **Stop** — pause before accepting; a strong emotional reaction or an extraordinary claim means more checking, not less
  • **Investigate the source** — lateral reading: leave the source and search what trusted sources say about it ("[source] bias", "[source] credibility", fact-checking sites, Wikipedia entries on the organisation)
  • **Find better coverage** — seek consensus across reputable sources; prioritise primary sources and official data; peer-reviewed research for scientific claims
  • **Trace claims, quotes, and media** — follow quotes and statistics to their original context; confirm claim-makers are quoted accurately and images aren't decontextualised

Phase 3 — Assess source quality (RADAR)

Apply to each source before weighting its evidence:

  • **Rationale** — why was this created? Important omissions? Neutral or emotionally charged language?
  • **Authority** — author credentials; affiliation with reputable institutions?
  • **Date** — current enough for the field's pace?
  • **Accuracy** — cites reliable sources? Key claims verifiable elsewhere?
  • **Relevance** — directly addresses the question?

Full rubric with red flags and scoring: `references/source-evaluation-radar.md`. Always prefer official/primary sources over third-party interpretation.

Phase 4 — Weight evidence by tier

  • **Tier 1 — Primary** (original research papers, official statistics, historical documents, legislation, official organisational statements): 90–100% confidence when multiple primary sources agree. When they exist, cite them directly.
  • **Tier 2 — Secondary** (literature reviews, meta-analyses, textbooks, reputable news reporting — Reuters, AP, BBC — expert analysis citing primary evidence): 70–89% confidence when multiple quality sources agree. Use when primary sources are inaccessible or need expert interpretation.
  • **Tier 3 — Tertiary** (encyclopaedias including Wikipedia, dictionaries, almanacs): orientation only — too far from firsthand information to cite. Use to find primary and secondary sources.

Context-dependent weighting adjustments: `references/evidence-hierarchy.md`.

Phase 5 — Triangulate

Significant factual claims require **at least three independent, high-quality sources**.

  • **Verify independence**: not citing each other, different organisations, different methodologies or data. Three sources repeating one original claim is weak triangulation.
  • Check consistency across time periods, locations, and populations.
  • **Strong consensus** (3+ quality sources agree) → Confirmed. **Weak consensus** (2 agree, 1 disagrees) → Likely; investigate the outlier and weight by quality. **No consensus** → Phase 6.
  • Record sources consulted, points of agreement and disagreement, quality assessments, and the rationale for the final rating.

Phase 6 — Resolve conflicting sources

1. **Identify the disagreement precisely** — facts or interpretation? Same question? Different contexts (dates, definitions, methodologies)? 2. **Analyse methodologies** — could method, assumptions, or data access exp

Read more
@isvlasov
Ships withrageatc-oss

Rage Against The C - pick your own C to rage against. Two plugins for Claude Code / Cowork, built on the idea that we're using AI wrong: the speed of its output tricks us into rushing the input.

1145 skills11 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
11
Star history of isvlasov/rageatc-oss on GitHub, a chart by star-history.com

Other skills on rageatc-oss.

building-telegram-bots

building-telegram-bots

Writes correct, version-aware Telegram bot code. Use when writing, extending, or debugging a Telegram bot in python-telegram-bot,…

decomposing-work

decomposing-work

Converts an approved ARCHITECTURE.md into an implementation roadmap of isolated, dependency-ordered chunks. Use when architecture…

delegating-to-codex

delegating-to-codex

Delegates a task to OpenAI Codex running as an interactive session in a herdr pane - uses the user's ChatGPT subscription,…

designing-interfaces

designing-interfaces

Creates a design system for software with a UI. Use when a project has a user interface and architecture is confirmed — whether…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react5d252k
@facebook@facebookInstall Skill

Questions about verifying-claims.

Which coding agents can use verifying-claims?
verifying-claims installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.