iterate-on-a-document SKILL.md skillA
iterate-on-a-document from jessitron/iterate-on-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jessitron/iterate-on-docs/iterate-on-a-document@git:20261027.5c47e3bPins git:20261027.5c47e3b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jessitron/iterate-on-docs
- Path
skills/iterate-on-a-document/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261027.5c47e3b, committed Oct 27, 2026
- First version recorded
- Oct 12, 2026
- Size
- 2,315 bytes
- Repository stars
- 16
- License
- CC0-1.0
Refine a markdown or HTML document with the user by trading turns until they say it is good enough. The user edits the file and adds `@AI: <command>` directives — for HTML, by clicking elements in the browser — and the agent commits their edits, applies them everywhere they fit, and carries out the commands. Use when the user says "iterate on this doc", "let's trade turns on this file", or wants to refine a document by editing it themselves.
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
# Iterate on a document Goal: hand a document back and forth with the user until they say it is good enough, treating their edits as normative and executing their inline commands. The loop commits at each turn so every change is legible in git history. Where those commits go depends on the user's process; `git.md` lists the setups. Every commit and diff below goes through the one you choose. For HTML, each **HTML:** mark names a section of `html.md` to do at that point. Markdown needs nothing more. ## Procedure 0. Choose a git setup from `git.md` and begin it. **HTML:** Start. Commit the file. 1. Tell the user to take their turn. Give them the link to the file (every interaction, so they don't have to scroll up looking for it). Tell them to make any edits they like, and to add `@AI: <command>` directives anywhere in the document. **HTML:** Hand off. 2. Wait. The user's turn ends when they respond. 3. If the user says "good enough", "move on", or equivalent, stop. **HTML:** End. Then finish the git setup. 4. Commit the user's edits as they are, before making any changes. 5. Read the user's edits (`git diff HEAD~1` shows them). Treat each as normative but not …
Read the whole file at its exact version.
How to install
mdr add jessitron/iterate-on-docs/iterate-on-a-document@sha256:7c57d1eb73907a63The line at the top of this page pins the label git:20261027.5c47e3b, 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_acrwv52pjrl54sl5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 12, 2026 and Oct 27, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.5c47e3b latest | 2026-10-27 | 5c47e3b | 2,315 B | A | view · diff |
| git:20261015.fbf07f2 | 2026-10-15 | fbf07f2 | 2,252 B | A | view · diff |
| git:20261015.ff28ebf | 2026-10-15 | ff28ebf | 2,268 B | A | view · diff |
| git:20261012.75c760c | 2026-10-12 | 75c760c | 2,187 B | A | view · diff |
| git:20261012.c25a2d9 | 2026-10-12 | c25a2d9 | 2,177 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 (2315 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
jessitron/iterate-on-docs · 16 stars · license CC0-1.0 · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_acrwv52pjrl54sl5 GET https://markdownregistry.com/api/v1/resolve?ref=jessitron/iterate-on-docs/iterate-on-a-document GET https://markdownregistry.com/api/v1/blob/7c57d1eb73907a63a0dc306cbc0885904d081d43589b54db5355941c5f4eea9f
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.