Agent skill

Verify Claims

by pedrohcgs in pedrohcgs/claude-code-my-workflow

Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims.

MITAuto-check passedResearch & Science

Install Verify Claims

skills CLI
$ npx skills add pedrohcgs/claude-code-my-workflow --skill verify-claims -a claude-code

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

GitHub CLI
$ gh skill install pedrohcgs/claude-code-my-workflow verify-claims --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/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verify-claims .claude/skills/verify-claims && 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
verify-claims
GitHub stars
1.7k
Token cost
~2.2k tokens
SKILL.md length
832 words
Files
3
Skills in repo
59
Repo updated
First seen
Licence
MIT

At a glance

Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims.

  • Works in 5 steps: Pre-Flight → Extract claims → Generate verification questions → …
  • User says verify these citations
  • SKILL.md covers When to pick this skill, How it works, Example and Fail modes and recovery, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verify Claims is an agent skill from pedrohcgs/claude-code-my-workflow. Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Spawns the claim-verifier agent in a fresh context (never a conversation fork) so it never sees the draft — then reports which claims are supported, contradicted, or unverifiable. Use when user says "verify these citations", "check the claims in X", "did I hallucinate anything", "fact-check this draft", "run CoVe on this", or after any text generation that asserts facts about papers, datasets, or numerical results. NOT for…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `evals/cases/fresh-context-independence.md`).

It sits in Research & Science, covering Fact-checking and source verification and Copy editing and proofreading. The repository describes itself as: A ready-to-fork Claude Code template for academics using LaTeX/Beamer + R. Multi-agent review, quality gates, adversarial QA, and replication protocols. The licence is MIT.

When your agent uses it

  • User says verify these citations
  • Check the claims in X
  • Did I hallucinate anything
  • Fact-check this draft

Example prompts

  • “verify these citations”
  • “check the claims in X”
  • “did I hallucinate anything”
  • “/verify-claims”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Agent, Task, Write

Workflow steps

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

  1. Pre-Flight
  2. Extract claims
  3. Generate verification questions
  4. Spawn claim-verifier (fresh context — never a conversation fork)
  5. Reconcile

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Agent
    • Task
    • Write

    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

    Links to these hosts (documentation or services it may open):

    • arxiv.org

    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

Verify Claims loads about 2.2k tokens when it runs. Until then it costs about 152 tokens; SKILL.md has 832 words of instructions outside code blocks.

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

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 pedrohcgs/claude-code-my-workflow at commit ae72617, republished under its MIT licence (© pedrohcgs). 832 words, ~2,232 tokens.

Download SKILL.mdSave it as .claude/skills/verify-claims/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
verify-claims
description
Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Spawns the `claim-verifier` agent in a fresh context (never a conversation fork) so it never sees the draft — then reports which claims are supported, contradicted, or unverifiable. Use when user says "verify these citations", "check the claims in X", "did I hallucinate anything", "fact-check this draft", "run CoVe on this", or after any text generation that asserts facts about papers, datasets, or numerical results. NOT for style/grammar review (use `/proofread`) or substance review (use `/review-paper`).
allowed-tools
Read, Grep, Glob, Agent, Task, Write
argument-hint
[file-or-text-path] [--source <path-or-url>] [--no-fail-closed]
disallowed-tools
Edit, MultiEdit

/verify-claims — Chain-of-Verification on a Draft

Fact-check a draft using the Post-Flight Verification protocol (.claude/rules/post-flight-verification.md).

Input: $ARGUMENTS — path to a file containing the draft (markdown, .qmd, .tex, .md) or a shorthand pointer. Optional flags:

  • --source <path-or-url> — one or more source-material pointers (repeat for multiple). If omitted, the skill infers from context (e.g., papers referenced, cited arXiv URLs).
  • --no-fail-closed — downgrade FAIL outcomes to warnings without regeneration. Use sparingly.

When to pick this skill

  • /verify-claims (this skill) — ad-hoc fact-checking on any draft or text block the user hands you. One-shot, user-invoked.
  • Other skills that auto-run Post-Flight internally (/lit-review, /research-ideation, /respond-to-referees, /review-paper --peer) — no need to call this separately; they already run it.
  • /proofread — grammar, typos, overflow. Different lens.
  • /review-paper (default mode) — full manuscript review, not just claim verification.
  • /validate-bib — checks citations exist and are well-formed (structural + DOI). This skill checks they hold (the cited paper supports the attributed claim). Complementary — run both before submission.

How it works

Implements the 4-step CoVe loop from Dhuliawala et al. 2023 (arXiv:2309.11495), with architectural enforcement of the fresh-context independence trick.

Phase 0 — Pre-Flight

Confirm:

  • Draft file exists and is readable
  • At least one source pointer available (either --source or auto-detected from draft)
  • claim-verifier agent file exists at .claude/agents/claim-verifier.md

If any fail → surface the failure, do NOT proceed.

Phase 1 — Extract claims

Read the draft. Identify factual assertions of these types:

TypeExample
Citation"Smith (2019, JEL) shows X"
Numerical fact"N = 10,000", "ATT = 0.42"
Negative literature"No prior work studies X"
Named entityresearcher, paper title, venue, package, estimator name
Dataset claim"The CPS contains field educ_attain"

Skip: opinions, forward-looking suggestions, definitions the draft introduces.

For citation-type claims, extract the claim↔citation PAIR — not just the citation. Capture what the draft attributes to which work, so the verifier checks appropriateness (does Smith 2019 actually show X?), not merely existence. "Smith (2019) shows a positive wage effect" becomes {cite: Smith2019, attributed: "positive wage effect"}. This is the layer /validate-bib explicitly defers here: validate-bib confirms the citation exists and is well-formed; this skill confirms it holds. A mis-citation (the paper exists but says something else, or the opposite) is exactly a numeric/directional contradiction → HIGH-WARN unless a concrete author_alternative is recorded (then EXPLAINED).

Output a claims table:

markdown
| ID | Claim | Source hint |
|----|-------|-------------|
| C1 | ... | ... |
Phase 2 — Generate verification questions

One question per claim. Make it specific and answerable from the source alone.

Phase 3 — Spawn claim-verifier (fresh context — never a conversation fork)
Agent: subagent_type=claim-verifier   # a named subagent starts fresh; a /fork copy would inherit the draft
Prompt: hand over claims table + verification questions + source material pointers.
        Do NOT include the draft text.

The forked agent runs the CoVe independent-answer step. It has never seen the draft and cannot confirm-bias. It returns a structured verification report.

Show full SKILL.md (415 more words)Show less
Phase 4 — Reconcile

The verifier returns a per-claim verdict in one of these severity tiers:

  • HIGH-WARN — fabricated reference (the cited paper doesn't exist at the named venue/year), draft claim directly contradicted by the source, or not_found retrieval that the verifier interprets as a hallucinated citation. Fail closed — surface these first and never present the draft as verified while one stands. This is a reporting rule, not a mechanical gate: nothing in /commit or the pre-commit hook reads these verdicts, so the author decides, and a HIGH-WARN left in place is stated in the report the user sees.
  • MED-WARN — transient infrastructure / retrieval failure (paywall the verifier can normally bypass via cached metadata; DOI resolver timeout; partial PDF read). Surface for the author; do not gate-refuse.
  • LOW-WARN — source genuinely inaccessible (paywalled and not in cache; private dataset; pre-print server transient). Surface with cannot-verify flag; do not gate-refuse.
  • EXPLAINED (v2.0) — a numeric/directional contradiction the author has pre-justified with a concrete named alternative (different defensible edition, specification, sample, or rounding convention), passed to the verifier via the claim's author_alternative field. Surfaced with the evidence and the recorded reason; non-gating. The hard floor holds: a fabricated citation is never EXPLAINED, and a blank/vague alternative stays HIGH-WARN. This mirrors audit-reproducibility's EXPLAINED disposition for numeric claims — a mismatch is not always a failure when a defensible alternative is named.

Verdict aggregation by tier across all extracted claims (EXPLAINED counts as non-gating, like LOW):

Tier countsOutcomeWhat the report says
0 HIGH, 0 MED, ≥ 0 LOW/EXPLAINEDPASS (green block)draft verified
0 HIGH, ≥ 1 MED, any LOW/EXPLAINEDPARTIAL (yellow block)verified with warnings
≥ 1 HIGHFAIL (red block)never reported as verified while a HIGH-WARN stands (unless --no-fail-closed)

--no-fail-closed reports HIGH-WARN verdicts as ordinary warnings instead of failing closed. Use sparingly — it's there for offline / hallucination-sensitive contexts where the user accepts the risk in writing.

If the draft is writeable and the user asked for auto-correction, regenerate the affected sections using the verifier's evidence. Otherwise return the report and let the user decide.

Example

/verify-claims quality_reports/lit-review_measurement-error.md --source master_supporting_docs/author_2021_method.pdf --source master_supporting_docs/coauthor_2020_survey.pdf

Expected output (abridged):

markdown
## Post-Flight Verification — lit-review_measurement-error.md

**Claims extracted:** 14
**Verified independently:** 14 (fresh-context claim-verifier)
**Outcome:** FAIL — 12 verified, 1 contradicted by its source (HIGH-WARN), 1 unverifiable (LOW-WARN); the draft is not reported as verified until C7 is corrected

### Discrepancies

- **C7** — draft claims "Coauthor (2020) *proposes* a bias-corrected estimator." Source Section 4 shows they propose a weighting estimator, not a bias-corrected one. Recommend correction.

### Unverifiable

- **C12** — draft cites "Third Author et al. 2024 (working paper)". No canonical URL in provided sources. Recommend user supply DOI or arXiv link.

### Verified

| ID | Claim | Evidence |
|----|-------|----------|
| C1 | "Author 2021 defines the calibration constant as a ratio of moments" | p. 5, eq. (3) |
| ... | ... | ... |

Fail modes and recovery

Verifier times out: surface a warning block, return draft as provisional. Do not silently ship.

Source material inaccessible (paywall, 404): report the specific claims that hinge on it, flag as cannot-verify, recommend user supply an alternative source.

Draft contains only opinions / forward-looking text: report "no verifiable factual claims extracted — nothing to check" and return.

Cross-references

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

Files

SKILL.md and 2 other files in .claude/skills/verify-claims of pedrohcgs/claude-code-my-workflow.

  • SKILL.md
  • evals/cases/fresh-context-independence.md
  • evals/marker.txt

Open the folder on GitHubat commit ae72617

Compare with similar skills

Verify Claims 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.

Verify Claims compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Claims this skillpedrohcgs/claude-code-my-workflow1.7k—~2.2kAutomated 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 pedrohcgs/claude-code-my-workflow

All 59 skills in this repo
  • Devils Advocate

    pedrohcgs/claude-code-my-workflow

    Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation.

    1.7k GitHub starsUsed in 2 repos~641 tokens
    Auto-check passed
  • Vaccinate

    pedrohcgs/claude-code-my-workflow

    Qualify a check before it is allowed to clear anything — prove it can detect the failure it is meant to catch.

    1.7k GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check: notes
  • Compile Latex

    pedrohcgs/claude-code-my-workflow

    Compile a Beamer LaTeX slide deck with XeLaTeX (3 passes + bibtex).

    1.7k GitHub starsUsed in 1 repo~492 tokens
    Auto-check: notes
  • Context Status

    pedrohcgs/claude-code-my-workflow

    Show current context status and session health. An agent skill from pedrohcgs/claude-code-my-workflow.

    1.7k GitHub starsUsed in 1 repo~613 tokens
    Auto-check: notes
  • Capture Environment

    pedrohcgs/claude-code-my-workflow

    Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt /…

    1.7k GitHub stars~2.8k tokensUpdated 13 days ago
    Auto-check: notes
  • Checkpoint

    pedrohcgs/claude-code-my-workflow

    Save a structured state snapshot before stopping or handing off.

    1.7k GitHub stars~2.8k tokensUpdated 13 days ago
    Auto-check: notes

Questions about Verify Claims

What does Verify Claims do?

Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Verify Claims is an agent skill from pedrohcgs/claude-code-my-workflow. Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims.

When should I use Verify Claims?

Verify Claims fits situations like: user says verify these citations; check the claims in X; did I hallucinate anything; fact-check this draft.

How do I install Verify Claims in Claude Code?

Run `npx skills add pedrohcgs/claude-code-my-workflow --skill verify-claims -a claude-code`. Or copy the skill folder (.claude/skills/verify-claims in pedrohcgs/claude-code-my-workflow) into .claude/skills/verify-claims in your project. Claude Code loads it when a task matches its description.

How do I install Verify Claims in Codex?

Run `npx skills add pedrohcgs/claude-code-my-workflow --skill verify-claims -a codex`. Or copy the skill folder (.claude/skills/verify-claims in pedrohcgs/claude-code-my-workflow) into .agents/skills/verify-claims in your project. Codex loads it when a task matches its description.

Can I use Verify Claims 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 pedrohcgs/claude-code-my-workflow --skill verify-claims -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-claims, .gemini/skills/verify-claims, .github/skills/verify-claims and .opencode/skills/verify-claims in your project.

What does Verify Claims need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify Claims is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Agent, Task, Write.

Does Verify Claims access the network?

SKILL.md names 1 domain. As links in the text: arxiv.org. This is read from the text; nothing was executed.

Is Verify Claims 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 Verify Claims use?

Verify Claims is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Claims use?

About 2.2k tokens (SKILL.md is roughly 8.9k 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 Verify Claims?

Skills that share tags, products or a category with Verify Claims: 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 Verify Claims?

pedrohcgs (a GitHub user) maintains it in pedrohcgs/claude-code-my-workflow, which has 1,655 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on September 27, 2026.

Source: pedrohcgs/claude-code-my-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.