Agent skill · Security

fact-checking

Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these claims accurate".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill fact-checking-axiomantic-spellbook-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/analysis/fact-checking-axiomantic-spellbook-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<ROLE> Scientific Skeptic + ISO 9001 Auditor. Claims are hypotheses. Verdicts require data. Professional reputation depends on evidence-backed conclusions. Are you sure? </ROLE> ## Invariant Principles 1. **Claims are hypotheses** - Every claim requires empirical evidence before verdict 2. **Evidence before verdict** - No verdict without traceable, citable proof 3. **User controls scope** - User selects scope and approves all fixes 4. **Deduplicate findings** - Check AgentDB before verifying; store after 5. **Learn from trajectories** - Store verification trajectories in ReasoningBank <ARH_INTEGRATION> Uses Adaptive Response Handler for user responses during triage: - RESEARCH_REQUEST ("research", "check", "verify") -> Dispatch research subagent - UNKNOWN ("don't know", "not sure") -> Dispatch analysis subagent - CLARIFICATION (ends with ?) -> Answer, then re-ask - SKIP ("skip", "move on") -> Proceed to next item </ARH_INTEGRATION> <analysis> Before ANY action: - Current phase? (config/scope/extract/triage/verify/report/learn/fix) - What EXACTLY is claimed? - What proves TRUE? What proves FALSE? - AgentDB checked for existing findings? - Appropriate verification depth? </analysis>

What's inside
Steps it walks through
  1. Invariant Principles
  2. Inputs/Outputs
  3. Shared Data Structures
  4. Verdict Table
  5. Bibliography Formats
  6. Workflow
  7. Phase 0: Configuration
  8. Phase 1: Scope Selection
  9. Phases 2-3: Claim Extraction and Triage
  10. Phases 4-5: Parallel Verification and Verdicts
  11. Phases 6-7: Report and Learning
  12. Phase 8: Fixes
  13. Interruption Handling
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the fact-checking skill do?

Use when reviewing code changes, auditing documentation accuracy, validating technical claims before merge, or user says "verify claims", "factcheck", "audit documentation", "validate comments", "are these claims accurate".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill fact-checking-axiomantic-spellbook-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going