doc-consistency-check 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.
doc-consistency-check from yeaight7/agent-powerups is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yeaight7/agent-powerups/doc-consistency-check@git:20260606.c191da4Pins git:20260606.c191da4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yeaight7/agent-powerups
- Path
plugins/documentation-systems/skills/doc-consistency-check/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260606.c191da4, committed Jun 6, 2026
- First version recorded
- May 2, 2026
- Size
- 2,949 bytes
- Repository stars
- 8
- License
- Apache-2.0
Use when documentation may have rotted against the code -- files were renamed or moved, scripts or env vars changed, or readers report commands and paths from the docs that no longer work.
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
## Purpose
Documentation rots when code changes. This check finds stale references in Markdown files — paths, commands, package scripts, env names, links — and flags them for immediate correction.
## When to Use
- After a refactor that renamed or moved files, scripts, or env vars
- A reader followed the docs and a command or path failed
- Periodic doc hygiene before a release
## Inputs
- The documentation set (Markdown files across the repo, not just the README)
- The current repo state to validate against
## Workflow
1. **Inventory the docs and extract referenced paths:**
```bash
git ls-files "*.md" # full doc inventory
rg -no "[A-Za-z0-9_-]+/[A-Za-z0-9_./-]+\.[a-z]{2,4}" README.md docs/ # path-like references
```
2. **Verify referenced files still exist** in the repository. If not, the documentation is stale:
```bash
test -f src/components/Button.tsx || echo "STALE: src/components/Button.tsx"
```
3. **Verify documented commands against reality.** Package scripts, CLI invocations, and env names must match the current source:
```bash
…Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/doc-consistency-check@sha256:5f39b6c72a1184bcThe line at the top of this page pins the label git:20260606.c191da4, 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_pzc5ogcn2qrhkg6z)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 2, 2026 and Jun 6, 2026, about one every 17 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.c191da4 latest | 2026-06-06 | c191da4 | 2,949 B | A | view · diff |
| git:20260502.5b203d8 | 2026-05-02 | 5b203d8 | 647 B | A | view · diff |
| git:20260502.f6e3f26 | 2026-05-02 | f6e3f26 | 142 B | B | 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 (2949 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
yeaight7/agent-powerups · 8 stars · license Apache-2.0 · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pzc5ogcn2qrhkg6z GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/doc-consistency-check GET https://markdownregistry.com/api/v1/blob/5f39b6c72a1184bc3fda2c029cd298e898bb9b6beedb01e449993f9ba98bdd59
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 yeaight7/agent-powerups
Every file in yeaight7/agent-powerups