docs-audit SKILL.md skillA
docs-audit from strands-agents/box is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add strands-agents/box/docs-audit@git:20261007.158dadePins git:20261007.158dade in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- strands-agents/box
- Path
.agents/skills/docs-audit/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261007.158dade, committed Oct 7, 2026
- Size
- 3,825 bytes
- Repository stars
- 548
- License
- Apache-2.0
Assess an existing Box documentation page (docs/user/, docs/design/, or a crate README.md) for accuracy against the code and its tests, placement, and voice, and recommend what to fix. Use before a rewrite, when a page may have drifted from the code, or when asked to "audit this page", "is this page still true", or "what is wrong with this doc".
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
# Documentation audit Assess one existing page, and produce a structured assessment with the fixes in priority order. **How this differs from `docs-reviewer`.** The reviewer is a voice gate for a draft. The audit is for a page that already exists: it checks each claim against the code and its tests, finds the gaps, and decides what needs work. Use the audit to decide *what to fix*. Use the reviewer to decide *that a draft can ship*. ## Inputs - **Target page**: a path in the repository. - **Context** (optional): an issue, a changed behavior, or a concern. ## Process ### Step 1: Read and classify Read the page. Classify its guide and its content type. A page that mixes types is itself a finding, and it is the most common structural problem. ### Step 2: Accuracy Follow [`claim-verification.md`](../../references/claim-verification.md). List each claim on the page, and check it against the code and the test that pins it. **The code is the authority.** Where the page and the code disagree, the page is wrong. Name the symbol or the test that the page disagrees with. Never recommend a code change to agree with a page. Check each of these: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3nalymgsipemhdyi/6467c9914d62a3ba95e248b4ab032f66c3e8560b3d3f0035da5eeb20d3d4fb8b.json
Then /plugin install docs-audit@markdownregistry-3nalymgsipemhdyi in Claude Code. It installs git:20261007.158dade, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add strands-agents/box/docs-audit@sha256:6467c9914d62a3baThe line at the top of this page pins the label git:20261007.158dade, 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_3nalymgsipemhdyi)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in strands-agents/box/docs-audit since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of docs-audit from somewhere else? Ask it: where did my docs-audit come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Oct 7, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/docs-audit/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (3825 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
strands-agents/box · 548 stars · license Apache-2.0 · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3nalymgsipemhdyi GET https://markdownregistry.com/api/v1/resolve?ref=strands-agents/box/docs-audit GET https://markdownregistry.com/api/v1/blob/6467c9914d62a3ba95e248b4ab032f66c3e8560b3d3f0035da5eeb20d3d4fb8b
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 strands-agents/box
Every file in strands-agents/box
Other files named docs-audit
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.