doc-sync SKILL.md skillA
doc-sync from univers42/claude-deal-with-the-devil is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add univers42/claude-deal-with-the-devil/doc-sync@git:20260930.06ed519Pins git:20260930.06ed519 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- univers42/claude-deal-with-the-devil
- Path
skills/doc-sync/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260930.06ed519, committed Sep 30, 2026
- First version recorded
- Sep 30, 2026
- Size
- 3,769 bytes
- Repository stars
- 4
- License
- none declared
Find the documentation a change just made false and fix exactly that, examples copied from a passing run. Use when a flag was renamed, a path moved, a default changed, a command was removed, or a README example no longer matches what the code prints. Auto-triggers on: "update the docs", "are the docs current", "the README is out of date", "document this change", "the docs are stale".
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
# Doc sync Documentation does not rot gradually. It becomes false at a specific commit, and then stays false until someone notices — usually a new person, who trusts it, and loses an afternoon. This is the pass that runs *after* a change: find what the change falsified, and fix exactly that. The `documenter` agent writes docs from scratch; this keeps existing ones true. ## 1. Find what the change falsified Start from the diff, not from the docs. ```sh git diff --name-only <base>..HEAD ``` For every renamed, removed or signature-changed thing, grep the docs for it: ```sh rg -n '<old-name>|<old-flag>|<old-path>' --glob '*.md' --glob '*.rst' devil selfcheck # in a .claude config: names docs claim but that are gone ``` The five that go stale first, in order of how often: 1. **Command examples** — a renamed flag, a changed default, a moved path. 2. **Output samples** — pasted once, never re-run, now showing columns that no longer exist. 3. **Config keys** — documented after being renamed. 4. **Cross-references** — a link to a file that moved or a section that was retitled. 5. **Counts and lists** — "the six tools", now seven. This one is invisible and constant. …
Read the whole file at its exact version.
How to install
mdr add univers42/claude-deal-with-the-devil/doc-sync@sha256:a91e541a25b8a84eThe line at the top of this page pins the label git:20260930.06ed519, 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_v25kspytiokypqz3)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Sep 30, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.06ed519 latest | 2026-09-30 | 06ed519 | 3,769 B | A | view · diff |
| git:20260930.b857b76 | 2026-09-30 | b857b76 | 3,630 B | A | view · diff |
| git:20260930.a77cb5e | 2026-09-30 | a77cb5e | 3,634 B | A | view · diff |
| git:20260930.aa9f9b9 | 2026-09-30 | aa9f9b9 | 3,589 B | A | view · diff |
| git:20260930.445fa69 | 2026-09-30 | 445fa69 | 3,593 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 (3769 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
univers42/claude-deal-with-the-devil · 4 stars · license none declared · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v25kspytiokypqz3 GET https://markdownregistry.com/api/v1/resolve?ref=univers42/claude-deal-with-the-devil/doc-sync GET https://markdownregistry.com/api/v1/blob/a91e541a25b8a84eee24ae7879d141a2081e9c0eabfb8780c1d92b96e923f140
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 univers42/claude-deal-with-the-devil
Every file in univers42/claude-deal-with-the-devil