polish SKILL.md skillB
polish from vzakharov/muthur is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vzakharov/muthur/polish@git:20261016.bb62c02Pins git:20261016.bb62c02 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vzakharov/muthur
- Path
.claude/skills/polish/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.bb62c02, committed Oct 16, 2026
- First version recorded
- Sep 23, 2026
- Size
- 2,706 bytes
- Repository stars
- 22
- License
- MIT
Run the standard quality passes over work just done — `/dry`, then `/tend-prose` — scoped to what the branch has changed since it was last polished, committing what they change. These are the passes `/go` runs at its Step 3; this skill is how work that never went through `/go` gets them. Invoke as `/polish [focus guidance]`, or `/polish full` to re-read the branch's whole diff against its base rather than only what it changed since the last polish commit. Use when the operator says…
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
**The passes run in a fresh subagent, never in the session that loads this skill.** That session is usually the work's author, reading the diff with the change's history in mind, so a comment narrating the edit, or two blocks it remembers as different, reads fine to it and not to a reviewer. A subagent has only the diff and the plan, as the reviewer will. So launch one `general-purpose` subagent, in the foreground (`run_in_background: false`) since it edits, commits and pushes the working tree, and touch nothing until it returns. Its prompt carries: - `@.claude/skills/polish/passes.md`, to load and follow — the whole procedure, which this session does not read; - the argument, verbatim; - the plan under `docs/plans/`, when the branch has one, as the record of intent. Nothing else: no account of what was built or why. **It reports, and the session relays.** Answer the intent questions this session's context settles and act on them, committed under the type the edit would carry anyway: a `polish:` subject would put the edit below the next run's floor (`passes.md` § "The floor"), unreviewed. The rest go to the operator with `/dry`'s calls. …
Read the whole file at its exact version.
How to install
mdr add vzakharov/muthur/polish@sha256:95ddd695ef8da3a0The line at the top of this page pins the label git:20261016.bb62c02, 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_6uxv6arj6e2oiwp3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 23, 2026 and Oct 16, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.bb62c02 latest | 2026-10-16 | bb62c02 | 2,706 B | B | view · diff |
| git:20261015.bfd1a40 | 2026-10-15 | bfd1a40 | 2,351 B | B | view · diff |
| git:20261014.0f16275 | 2026-10-14 | 0f16275 | 7,990 B | B | view · diff |
| git:20260924.b8e79b6 | 2026-09-24 | b8e79b6 | 7,967 B | B | view · diff |
| git:20260923.d6730fb | 2026-09-23 | d6730fb | 7,587 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2706 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
vzakharov/muthur · 22 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6uxv6arj6e2oiwp3 GET https://markdownregistry.com/api/v1/resolve?ref=vzakharov/muthur/polish GET https://markdownregistry.com/api/v1/blob/95ddd695ef8da3a0b625f0031b2c8fe2be975931d4d0ad7ff256e1b3675f84f7
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 vzakharov/muthur
Every file in vzakharov/muthur