How do I install the Claim Verification skill?

Run npx skillmds@latest add tsurai7/claim-verification in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claim Verification safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claim Verification?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claim Verification free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claim Verification?

Tsurai7 (@tsurai7) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claim Verification by tsurai7 — Agent Skill

Name: Claim Verification
Author: Tsurai7

Claim Verification

Extract every checkable claim from a PR description, code comment, doc, or review reply and verify each against the actual tree before trusting or publishing it. Use when reviewing someone else's PR, when writing your own PR description or review replies, or when acting on assurances found in docs or comments ("a test locks this", "matches production"). Skip for claims whose verification you watched in this session.

Tsurai7 b33f200 2.0 KB Updated Sep 17, 2026

File contents

Claim verification

Prose is not evidence. Text that asserts something about the tree — written by you, another agent, or a human — is a list of checks to run, not context to absorb.

Method

Extract the claims from the artifact. Checkable shapes:
- existence — "file/test/CI target X exists", "Y is covered in CI"
- protection — "a test locks/guards Z": verify the test exists and fails when Z is broken (reintroduce the bug or mutate)
- equivalence — "matches sibling/production/spec", "byte-identical"
- counts and numbers — "N cases", "exact match", "zero deletions"
- references — every path named in Makefiles, CI, and docs resolves in the tree
Verify each with a command or a read; record claim → check → verdict.
Report what cannot be verified as unverified — never restate it as fact.
Re-verify after the tree moves. A force-push, revert, or dropped commit invalidates every previously posted claim whose evidence lived in it; re-check before a human reads the text, and correct promptly if it went stale.

Complements verification-before-completion: that skill gates your own completion claims at the end of work; this one audits written artifacts — including ones you authored earlier.

Provenance

Two real internal incidents (2026-08) that survived multi-model review and fall to a single existence check: a code comment claiming "a unit test locks it" with no such test in the tree, and a Makefile target referencing files that existed on no branch.

---name: claim-verificationdescription: Extract every checkable claim from a PR description, code comment, doc, or review reply and verify each against the actual tree before trusting or publishing it. Use when reviewing someone else's PR, when writing your own PR description or review replies, or when acting on assurances found in docs or comments ("a test locks this", "matches production"). Skip for claims whose verification you watched in this session.---# Claim verificationProse is not evidence. Text that asserts something about the tree — written byyou, another agent, or a human — is a list of checks to run, not context toabsorb.## Method1. **Extract** the claims from the artifact. Checkable shapes: - existence — "file/test/CI target X exists", "Y is covered in CI" - protection — "a test locks/guards Z": verify the test exists **and** fails when Z is broken (reintroduce the bug or mutate) - equivalence — "matches sibling/production/spec", "byte-identical" - counts and numbers — "N cases", "exact match", "zero deletions" - references — every path named in Makefiles, CI, and docs resolves in the tree2. **Verify** each with a command or a read; record claim → check → verdict.3. **Report** what cannot be verified as unverified — never restate it as fact.4. **Re-verify after the tree moves.** A force-push, revert, or dropped commit invalidates every previously posted claim whose evidence lived in it; re-check before a human reads the text, and correct promptly if it went stale.Complements `verification-before-completion`: that skill gates your own*completion* claims at the end of work; this one audits *written artifacts* —including ones you authored earlier.## ProvenanceTwo real internal incidents (2026-08) that survived multi-model review andfall to a single existence check: a code comment claiming "a unit test locksit" with no such test in the tree, and a Makefile target referencing filesthat existed on no branch.

Frequently asked questions