grind-prework SKILL.md skillA
grind-prework from zackees/clud is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zackees/clud/grind-prework@git:20260926.1b4dfa8Pins git:20260926.1b4dfa8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zackees/clud
- Path
crates/clud-bin/assets/skills/grind-prework/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260926.1b4dfa8, committed Sep 26, 2026
- First version recorded
- Sep 26, 2026
- Size
- 2,664 bytes
- Repository stars
- 14
- License
- a license file GitHub does not identify
Record one /grind run's plan on its meta issue: post the workflow's pre-built plan comment body (or split parts) exactly once each, in order, and return the comment URLs. Never edits a comment.
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
<!-- managed-by: clud --> # /grind-prework You record the plan; you do not make it. You change no code, so the RED -> GREEN rule for code changes applies later, in `/grind-integrate`. The prompt carries the meta issue number, the repo, and one or more comment bodies the workflow already built. Each body starts with a marker, `<!-- grind:v1 plan run=<run-id> -->`, or `<!-- grind:v1 plan run=<run-id> part=k/N -->` for a split plan, followed by a `~~~json` fenced block holding the public `grind-plan/v1` plan. The workflow keeps backticks, single quotes, `$`, `<` and `>` out of the JSON (they are `\u` escapes), because clud's command hook reads a backtick, `$(`, `<(` or `>(` as a substitution even inside quotes. Never add a backtick fence and never unescape anything. 1. Post each body exactly once, verbatim, in the order given: part 1 first, then parts 2..N. Pipe the body, as one single-quoted word, from `printf '%s'` into `gh`: ```bash printf '%s' '<the body, exactly as given>' | gh issue comment <meta> --repo <repo> --body-file - ``` The body holds no single quote, so single quotes keep every character …
Read the whole file at its exact version.
How to install
mdr add zackees/clud/grind-prework@sha256:b8bc5d778f162a20The line at the top of this page pins the label git:20260926.1b4dfa8, 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_7x5i6aivo4h25ken)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Sep 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.1b4dfa8 latest | 2026-09-26 | 1b4dfa8 | 2,664 B | A | view · diff |
| git:20260926.9d3666a | 2026-09-26 | 9d3666a | 1,836 B | A | view · diff |
| git:20260926.65cf607 | 2026-09-26 | 65cf607 | 1,735 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 (2664 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
zackees/clud · 14 stars · license a license file GitHub does not identify · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7x5i6aivo4h25ken GET https://markdownregistry.com/api/v1/resolve?ref=zackees/clud/grind-prework GET https://markdownregistry.com/api/v1/blob/b8bc5d778f162a20d042081ba2edc1e2090194df9189e55f77f8c5fec72b595c
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.