clarify SKILL.md skillA
clarify from ronaknnathani/relay is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ronaknnathani/relay/clarify@git:20260629.7380310Pins git:20260629.7380310 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ronaknnathani/relay
- Path
skills/clarify/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260629.7380310, committed Jun 29, 2026
- First version recorded
- Jun 29, 2026
- Size
- 7,139 bytes
- Repository stars
- 43
- License
- MIT
Turn a vague or underspecified task into a crisp requirements + testable acceptance-criteria document by closing the gap between what was asked and what is actually wanted. Use at the start of any non-trivial task before planning, whenever the goal is fuzzy ("make it faster", "make it more robust", "add validation"), or whenever you cannot predict how the user would judge "done". Its output feeds `plan`. (For tidying existing code, use `simplify`, not clarify.).
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
# Clarify Produce a requirements + acceptance-criteria artifact that pins down what success looks like, so a planner never has to guess. The bar: every requirement is measurable and every acceptance criterion is checkable — you could hand the artifact to someone else and they'd build the right thing. This is a peer phase to `plan`, not its parent: it grounds itself in the code via `explore`, then hands its artifact to `plan`. It does **not** design the implementation and does **not** invoke `plan`. ## Process 1. **Resolve from the codebase before asking.** If a question's answer is discoverable in the code — how a thing currently works, what the existing convention is, where an integration point lives — call `explore` (dispatch a sub-agent when available; otherwise do it inline) and find it. Only ask the user what you genuinely cannot determine. Bothering them with a discoverable fact erodes trust. 2. **Form an explicit hypothesis of the whole task.** Write down, for yourself, the outcome you think they want and the success criteria you'd accept. This is what you'll test against the stop condition — and it makes your questions sharper. …
Read the whole file at its exact version.
How to install
mdr add ronaknnathani/relay/clarify@sha256:2db0d08ecf167161The line at the top of this page pins the label git:20260629.7380310, 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_avyo7ntpf2hjfn3k)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Jun 29, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260629.7380310 latest | 2026-06-29 | 7380310 | 7,139 B | A | view · diff |
| git:20260629.a497d9d | 2026-06-29 | a497d9d | 7,075 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 (7139 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
ronaknnathani/relay · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_avyo7ntpf2hjfn3k GET https://markdownregistry.com/api/v1/resolve?ref=ronaknnathani/relay/clarify GET https://markdownregistry.com/api/v1/blob/2db0d08ecf167161fcdd194362e1b7d607b5d8dd80ef3bfefde8ca1e957f9691
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 ronaknnathani/relay
Every file in ronaknnathani/relay