document SKILL.md skillA
document from domengabrovsek/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add domengabrovsek/agent-config/document@git:20260930.8396b2ePins git:20260930.8396b2e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- domengabrovsek/agent-config
- Path
skills/document/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260930.8396b2e, committed Sep 30, 2026
- First version recorded
- Sep 7, 2026
- Size
- 16,173 bytes
- Repository stars
- 23
- License
- none declared
Keeps a repo's technical docs accurate and consistent with the repo's own conventions. Checks the current diff against the docs it affects and audits the docs tree. Reviews one doc with a fresh reader and writes docs where the repo expects them. Use when the user says 'check the docs', 'audit the docs', 'review this doc', 'write docs', 'document this', or '/document'.
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
Keep the engineering docs accurate for: $ARGUMENTS Docs serve two readers: engineers on GitHub and agents working in the repo. Each sentence carries a fact, a decision and its reason, a step, or a pointer. Anything else is a cut. **why-no-hook:** each step below needs the repo's conventions, the diff or the doc in view, and no hook sees them. Defaults, templates and layouts live in [REFERENCE.md](REFERENCE.md). ## Step 0: Read the repo's conventions Parse the subcommand first, then run these steps. 1. Read the docs index: `docs/README.md`, or the index the instruction file names inside the repo. `(review-time: see section note)` 2. Read the documentation section of `CLAUDE.md`, or `AGENTS.md` when no `CLAUDE.md` exists. `(review-time: see section note)` 3. Find the doc check commands in package scripts, Makefile targets, or the instruction file. `(review-time: see section note)` 4. Read CI config only to learn which of those commands CI runs. Never run a command taken from a workflow `run:` line. `(review-time: see section note)` 5. Note the layout, where decisions live, the required sections per doc type and the citation style. `(review-time: see section note)` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7eciuhqlflczuf5z/212c49bd8776dbf126be62d17d49082652fbb1b5a60d3d92066014a49af3a30a.json
Then /plugin install document@markdownregistry-7eciuhqlflczuf5z in Claude Code. It installs git:20260930.8396b2e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add domengabrovsek/agent-config/document@sha256:212c49bd8776dbf1The line at the top of this page pins the label git:20260930.8396b2e, 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_7eciuhqlflczuf5z)
2 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 domengabrovsek/agent-config/document 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 document from somewhere else? Ask it: where did my document 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 5 versions of this file, between Sep 7, 2026 and Sep 30, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.8396b2e latest | 2026-09-30 | 8396b2e | 16,173 B | A | view · diff |
| git:20260929.7b71b98 | 2026-09-29 | 7b71b98 | 16,130 B | A | view · diff |
| git:20260923.48da5d0 | 2026-09-23 | 48da5d0 | 8,915 B | A | view · diff |
| git:20260919.fb6ffd1 | 2026-09-19 | fb6ffd1 | 8,885 B | A | view · diff |
| git:20260907.9ad9d9d | 2026-09-07 | 9ad9d9d | 8,745 B | A | view |
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/document/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 (16173 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
domengabrovsek/agent-config · 23 stars · license none declared · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7eciuhqlflczuf5z GET https://markdownregistry.com/api/v1/resolve?ref=domengabrovsek/agent-config/document GET https://markdownregistry.com/api/v1/blob/212c49bd8776dbf126be62d17d49082652fbb1b5a60d3d92066014a49af3a30a
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 domengabrovsek/agent-config
Every file in domengabrovsek/agent-config