crux-rd skillA
crux-rd is agent-read markdown (skill) from mehdiforoozandeh/crux: Write the Requirements Document for a crux node — the design detail that does not fit, and should not fit, inside a 400-word question or hypothesis. An RD is one immutable design document per node, living in `rd/` beside the tree, linked from the node, outside the roll-up: the estimand and its bound, the probe ladder, the negative control, the known distortion that must travel with every result. You do not interview and you do not re-derive — you write up the design that has just been settled in.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# crux-rd — the design document a node cannot hold crux caps a node's prose at **400 words**. That cap exists because nodes measured in the thousands of words stopped being readable by the PI they exist to serve. But a cap with no outlet just makes prose denser. **This is the outlet.** An RD is where design detail goes **to be readable, not to hide.** The node's TL;DR must still stand alone: a reader who never opens the RD still knows what is being asked and what would settle it. If moving text into an RD makes the node unintelligible, the move was wrong. ## When you are invoked **Only when asked.** This skill ships `disable-model-invocation: true` and means it. The design being written up **lives in the conversation that just happened with the PI** — that is the whole reason this is a skill and not an agent. From a cold start you would either restate the node or re-derive the design badly. So: no interview, no research phase, no "shall I write this up?" offered unprompted. When the PI says the design has settled, you synthesize what was already discussed. ## The write-vs-skip filter — apply this *before* writing anything …
Read the whole file at its exact version.
How to install
mdr add mehdiforoozandeh/crux/crux-rd@v1.0mdr add mehdiforoozandeh/crux/crux-rd@sha256:bb19a35dddebe27aPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_kucx5owka62otbca)
1 badge views in 30 days
Versions
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 (7002 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
mehdiforoozandeh/crux · 6 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kucx5owka62otbca GET https://markdownregistry.com/api/v1/resolve?ref=mehdiforoozandeh/crux/crux-rd GET https://markdownregistry.com/api/v1/blob/bb19a35dddebe27a135ac581fcee75a08c9fb3c35525c0e2848ff3941c6fb918
Your agent 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.