verifying-claims SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
verifying-claims from oaustegard/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add oaustegard/claude-skills/verifying-claims@v0.2.0Pins v0.2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- oaustegard/claude-skills
- Path
verifying-claims/SKILL.md- Versions recorded
- 3
- Latest version
- v0.2.0, committed Jun 13, 2026
- First version recorded
- Jun 7, 2026
- Size
- 5,215 bytes
- Repository stars
- 158
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# verifying-claims Check that what a document *says* about code is true, by reading the document, the code, and the tests together and reporting where they disagree. ## What changed (v0.1 → v0.2) v0.1 was a comment-DSL: you hand-wrote `<!-- claim: ... -->` next to prose and a script checked the *comment* against the code. That had a fatal gap — the comment and the prose were two artifacts stapled together, and only the comment was checked, while humans read the prose. The prose could lie with a green run. v0.2 drops the DSL. The reviewer is the agent: it reads the prose's *meaning* directly and compares it to what the code does and what the tests assert. No shadow copy, because the thing being checked is the thing the human reads. (Existing tools already own the alternatives — Gherkin binds executable scenarios, Lean's Verso transcludes facts into prose, TDD couples code to tests. This fills the remaining slot: free-prose documentation, judged.) ## Division of labor — read this first This skill does NOT gate merges and is NOT a test framework. - **The test suite (TDD/CI)** owns the behavioral contract: deterministic, …
Read the whole file at its exact version.
How to install
mdr add oaustegard/claude-skills/verifying-claims@sha256:2be6b85b8fe561dcThe line at the top of this page pins the label v0.2.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lmhzzyqtt3k233re)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 7, 2026 and Jun 13, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.2.0 latest | 2026-06-13 | d93d7fb | 5,215 B | A | view · diff |
| v0.2.0 | 2026-06-07 | 2238e93 | 5,212 B | A | view · diff |
| v0.1.0 | 2026-06-07 | 958b5ba | 7,975 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5215 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
oaustegard/claude-skills · 158 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lmhzzyqtt3k233re GET https://markdownregistry.com/api/v1/resolve?ref=oaustegard/claude-skills/verifying-claims GET https://markdownregistry.com/api/v1/blob/2be6b85b8fe561dc531de2a51d770d677b7b5fe442c9e848b9b3ac7f1aa05765
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from oaustegard/claude-skills
Every file in oaustegard/claude-skills