verifying-claims
From the author
Check that a document's claims about code are actually true by reading the prose, the code, and the tests and reporting (or fixing) where they disagree. Use whenever the user wants to verify a README, guide, spec, or docstring still matches the code; whenever they mention documentation drift, doc-code sync, "is this still accurate", stale docs, or keeping docs/tests/code consistent; before publishing or merging a docs change; or as a periodic doc-accuracy sweep. The agent reads the prose's meaning directly — there is no claim-comment DSL to maintain. Pairs with TDD — the test suite is the deterministic behavioral gate, this skill is the semantic prose-vs-reality review.
Install
npx skills add oaustegard/claude-skills --skill verifying-claims -a claude-code
Installs to .claude/skills/verifying-claims/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 78
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- paper-verificationfcakyon/phd-skillsUse when the user wants to verify paper claims against code or data, audit numerical accuracy, check formula-code alignment, or validate citation accuracy. Triggers on phrases like "verify claims", "check numbers", "do the numbers match", "formula vs code", "audit the paper", or "cross-check results".Science★ 433
- docs-claim-checkkyungseo/skillsteadFact-check public docs, verify a README against a repo, audit release notes, or find stale/overstated claims using supplied evidence. Advisory findings only. Not for standalone code/security review, fixes or command execution; use it only for eligible claims in mixed requests. When using this skill, never edit files and run no commands except to load its SKILL.md at the exact host-catalog path. Use an already supplied full body without rereading. Follow the native loader or, for command-backed loading, one safely quoted literal cat of that path; no other file, shell expansion, chaining, redirection or pipeline. Resolve aliases only from host-provided mappings, without commands. If the path is unresolved or loading fails, is denied or finishes incomplete, stop and request full instructions; do not probe, retry, use shell paging or elevate. The command exception never covers target/evidence reads. Disclose loading and its outcome, including failure; a prohibited attempt invalidates the assessment.Security★ 84
- verify-claimspedrohcgs/claude-code-my-workflowRun 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`).Science★ 1.7K
- run-testsMicrock/ordinary-claude-skillsValidate code changes by intelligently selecting and running the appropriate test suites. Use this when editing code to verify changes work correctly, run tests, validate functionality, or check for regressions. Automatically discovers affected test suites, selects the minimal set of venvs needed for validation, and handles test execution with Docker services as needed.Testing★ 407
- validate-knowledgellopresto87/CypressProve that a knowledge base actually works before trusting it — after building or adopting docs, a knowledge graph, or a wiki, verify it can orient a fresh agent and resist false premises. Use at the end of an adoption, after a large docs change, or before relying on the graph to route work. Two methods: clean-context test agents answering known-answer and adversarial questions, and enforcement tests that plant a violation and confirm the linter catches it. A smoke test proves code runs; this proves the knowledge is correct, navigable, and honest.Testing★ 113
- fact-checkingseb1n/awesome-ai-agent-skillsVerify the accuracy of claims and statements by extracting individual assertions, identifying authoritative sources, cross-referencing evidence, and assigning confidence-scored verdicts. Use when the user requests fact checking or provides relevant inputs for this workflow.Productivity★ 228
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in