New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify Claims

by happier-dev in happier-dev/happier

Audit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources.

MITAuto-check passedResearch & Science

Install Verify Claims

skills CLI
$ npx skills add happier-dev/happier --skill verify-claims -a claude-code

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

GitHub CLI
$ gh skill install happier-dev/happier 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/happier-dev/happier.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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.9k
Token cost
~791 tokens
SKILL.md length
394 words
Files
1
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

Audit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources.

  • Works in 6 steps: Extract the load-bearing claims — those… → Re-derive each from a primary source.… → Use a different path than the claim… → …
  • Tasks that involve Fact-checking and source verification
  • SKILL.md covers Procedure, Output and Failure this prevents
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verify Claims is an agent skill from happier-dev/happier. Audit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources. Use before trusting subagent/lane reports, before building decisions on unverified claims, or when reviewing a conclusion written earlier (including your own). Distinct from running the app to verify behavior or reviewing a diff — this audits claims.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Fact-checking and source verification and Subagents. The repository describes itself as: Web, Desktop & Mobile client and orchestrator for Codex, Claude Code, OpenCode, Pi, Cursor, Grok, Antigravity, Kimi, Augment Code, Qwen, fully end-to-end encrypted. The licence is MIT.

When your agent uses it

  • Tasks that involve Fact-checking and source verification
  • Tasks that involve Subagents

Example prompts

  • “/verify-claims”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Extract the load-bearing claims — those whose falseness would change the decision being made. Ignore decoration; auditing everything…
  2. Re-derive each from a primary source. Source hierarchy: running code > tests > docs > comments > memory. Each step down the ladder is a…
  3. Use a different path than the claim arrived by. Claim from reading code → check with a runtime observation. Claim from a test → read the…
  4. Verify decision-material measurements against primary evidence. Recompute derived counts from raw records. For test, coverage, and timing…
  5. Treat plausibility as zero evidence. Narrative fit is what generated the claim, so "sounds right" is correlated with exactly the error…
  6. Downgrade what you cannot verify. If re-derivation is too expensive, do not skip and do not trust: relabel the claim as an assumption and…

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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 791 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 394 words of instructions outside code blocks.

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

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 happier-dev/happier at commit 1f03ccd, republished under its MIT licence (© happier-dev). 394 words, ~791 tokens.

Download SKILL.mdSave it as .claude/skills/verify-claims/SKILL.md (or your agent's skills folder).
name
verify-claims
description
Audit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources. Use before trusting subagent/lane reports, before building decisions on unverified claims, or when reviewing a conclusion written earlier (including your own). Distinct from running the app to verify behavior or reviewing a diff — this audits claims.

Verify Claims

Take a report — a subagent's, a lane's, a plan's, or your own from earlier — and re-derive its load-bearing claims instead of trusting how they sound. Full doctrine: docs/agent-craft.md §4.

Procedure

  1. Extract the load-bearing claims — those whose falseness would change the decision being made. Ignore decoration; auditing everything dilutes the audit.
  2. Re-derive each from a primary source. Source hierarchy: running code > tests > docs > comments > memory. Each step down the ladder is a step toward hearsay.
  3. Use a different path than the claim arrived by. Claim from reading code → check with a runtime observation. Claim from a test → read the code the test exercises. Two derivations sharing a path share that path's blind spot.
  4. Verify decision-material measurements against primary evidence. Recompute derived counts from raw records. For test, coverage, and timing claims, inspect the actual command/workload, terminal output, and relevant source/environment basis; a summary or inherited counter is insufficient. Match a named commit/artifact exactly; for dirty work, inspect the relevant current paths and account for concurrent changes. Apply root Validation to reuse versus re-execution: rerun when evidence is missing, stale, contradictory, cannot establish the claimed result, or independent risk-selected verification requires it. A new handoff alone does not require repeating every successful suite. Decorative counts should be removed.
  5. Treat plausibility as zero evidence. Narrative fit is what generated the claim, so "sounds right" is correlated with exactly the error being hunted. Check the best-fitting claims first, not last.
  6. Downgrade what you cannot verify. If re-derivation is too expensive, do not skip and do not trust: relabel the claim as an assumption and carry it labeled.
Show full SKILL.md (123 more words)Show less

For claims of backward, forward, mixed-version, upgrade, or rollback compatibility, use .agents/skills/happier-compatibility. Re-derive the claim against the exact released tag/artifact or applicable predecessor worktree basis, the real old/new component roles, and every claimed direction. A current-code fixture or mock that merely agrees with the current implementation is not independent compatibility evidence.

Output

Each audited claim in one of three bins, with the evidence:

  • Confirmed — how it was re-derived, via which independent path.
  • Refuted — the contradicting observation. Lead the report with these; a refuted claim is the headline.
  • Assumption — why it is unverifiable right now, and what would verify it.

Failure this prevents

Confident propagation of a wrong premise: reasoning chains valid at every link and false in total because link one was hearsay.

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

Files

Just SKILL.md in .agents/skills/verify-claims of happier-dev/happier.

Open the folder on GitHubat commit 1f03ccd

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 skillhappier-dev/happier1.9k—~791Automated safety check: PassMIT
Verify Openspec Docsgoern/forgejo-mcp1411 repos~1.1kAutomated safety check: PassGPL-3.0
Deep Researchalirezarezvani/claude-skills28k—~1.9kAutomated safety check: PassMIT
Web ResearchJuncai22/spring-ai-agent-learning1233 repos~1.1kAutomated safety check: PassApache-2.0
Workflow PatternsQuintinShaw/pi-dynamic-workflows554—~827Automated safety check: PassMIT
Choruz DocinclusionAI/Choruz991—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Verify Openspec Docs

    goern/forgejo-mcp

    Fact-checks OpenSpec user documentation with a fresh-context subagent that re-runs commands and checks claims against source.

    141 GitHub starsUsed in 1 repo~1.1k tokens
    Research & ScienceAuto-check passed

  • Deep Research

    alirezarezvani/claude-skills

    Run a disciplined, multi-source research investigation for a high-stakes question or decision — fan-out web search across many channels, parallel sub-agents, source triangulation (each claim backed…

    28k GitHub stars~1.9k tokensUpdated 1 mo ago
    Research & ScienceAuto-check passed

  • Web Research

    Juncai22/spring-ai-agent-learning

    A skill your agent uses for requests related to web research; it provides a structured approach to conducting comprehensive web research

    123 GitHub starsUsed in 3 repos~1.1k tokens
    Research & ScienceAuto-check passed

  • Workflow Patterns

    QuintinShaw/pi-dynamic-workflows

    Argument shapes for the 5 built-in workflow patterns — deep-research, adversarial-review, code-review, multi-perspective, codebase-audit — runnable via the workflow tool's name input, without…

    554 GitHub stars~827 tokensUpdated yesterday
    Research & ScienceAuto-check passed

  • Choruz Doc

    inclusionAI/Choruz

    Create, restructure, review, audit, or migrate Choruz Markdown documentation (docs/, README, AGENTS.md, the in-app docs pages) using one owner per fact, tier placement, executed-operation…

    991 GitHub stars~1.6k tokensUpdated yesterday
    Research & ScienceAuto-check passed

  • Deep Research

    312362115/claude

    深度调研技能：对任意命题进行系统性调研并输出专业研究报告. An agent skill from 312362115/claude.

    107 GitHub stars~6.6k tokensUpdated 4 mo ago
    Research & ScienceAuto-check passed

More from happier-dev/happier

All 28 skills in this repo

  • Happier Review

    happier-dev/happier

    Conduct evidence-backed Happier code, plan-completeness, session, worktree, feature, commit, branch, PR, codebase, and release-readiness reviews with affected-corridor analysis, high-confidence…

    1.9k GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Happier CI Stabilize

    happier-dev/happier

    Stabilize failing, flaky, slow, or repeatedly rerun Happier CI and nightlies by collecting all reachable failures from one exact attempt, correcting canonical causes in one batch, simplifying…

    1.9k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Happier Commit Worktree

    happier-dev/happier

    Reconnoiter, classify, validate, group, and commit a large or continuously changing Happier worktree as coherent, human-understandable commits while preserving concurrent work and excluding…

    1.9k GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Happier Release

    happier-dev/happier

    Resolve Happier's private release authority and run an exact-SHA release or nightly through cheap admission, verified CI evidence, resumable immutable candidates, and terminal publication proof.

    1.9k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • Happier Diagnose

    happier-dev/happier

    Diagnose and explain a Happier runtime, session, daemon, provider (Claude/Codex/OpenCode), authentication, or connectivity incident from logs, structured diagnostics, runtime state, and source…

    1.9k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Happier Implement

    happier-dev/happier

    Implement, change, build, fix, refactor, migrate, or apply accepted review findings in the Happier repositories with canonical-owner discovery, scope-preserving solution economy, TDD, efficient…

    1.9k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Verify Claims

What does Verify Claims do?

Audit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources. Verify Claims is an agent skill from happier-dev/happier. Audit a report, plan, or handoff by re-deriving every load-bearing claim from primary sources.

When should I use Verify Claims?

Verify Claims fits situations like: tasks that involve Fact-checking and source verification; tasks that involve Subagents.

How do I install Verify Claims in Claude Code?

Run `npx skills add happier-dev/happier --skill verify-claims -a claude-code`. Or copy the skill folder (.agents/skills/verify-claims in happier-dev/happier) 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 happier-dev/happier --skill verify-claims -a codex`. Or copy the skill folder (.agents/skills/verify-claims in happier-dev/happier) 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 happier-dev/happier --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.

Does Verify Claims access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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 791 tokens (SKILL.md is roughly 3.2k 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: Verify Openspec Docs (goern/forgejo-mcp, 141 stars), Deep Research (alirezarezvani/claude-skills, 28k stars), Web Research (Juncai22/spring-ai-agent-learning, 123 stars) and Workflow Patterns (QuintinShaw/pi-dynamic-workflows, 554 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Claims?

happier-dev (a GitHub organization) maintains it in happier-dev/happier, which has 1,883 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 8, 2026.

Source: happier-dev/happier on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.