clarify SKILL.md skillA
clarify from ericrisco/rsc-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ericrisco/rsc-harness/clarify@git:20261003.f0c84d6Pins git:20261003.f0c84d6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ericrisco/rsc-harness
- Path
skills/clarify/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261003.f0c84d6, committed Oct 3, 2026
- First version recorded
- Jun 2, 2026
- Size
- 14,304 bytes
- Repository stars
- 236
- License
- MIT
Use when a spec exists and must be de-risked before planning — hunt its ambiguities, unstated assumptions and edge cases, ask the few build-changing questions, bake the answers back into the spec. The rsc SDD gate between `specify` (writes the spec) and `plan` (designs the build). NOT the cross-artifact consistency check (that is `analyze`).
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 — the de-risking gate before planning A spec written in one sitting always lies a little. It states what the author *thought of*, and stays silent on everything they didn't — the edge cases, the unstated defaults, the words that mean two things. Those silences don't disappear; they get discovered later, mid-implementation, where they cost ten times as much to fix. **Clarify is the gate that drags those silences into the open while they are still cheap.** This is the fourth phase of the rsc SDD chain (`constitution` → `specify` → **`clarify`** → `plan` → `tasks` → `analyze` → `implement` → `verify` → `review` → `ship`); the method itself lives in `../sdd/SKILL.md`. `specify` turned a fuzzy intent into a spec; clarify interrogates that spec, asks the user the questions that actually change the build, and writes the answers back so the spec becomes safe to plan from. It produces **no new artifact** — it sharpens the existing one in place. The line is **specify creates, clarify de-risks, plan designs**: if you find yourself proposing how to *build* it, you have left clarify. …
Read the whole file at its exact version.
How to install
mdr add ericrisco/rsc-harness/clarify@sha256:bde50792a5acd076The line at the top of this page pins the label git:20261003.f0c84d6, 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_3vdzxferzkapyx7i)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 2, 2026 and Oct 3, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.f0c84d6 latest | 2026-10-03 | f0c84d6 | 14,304 B | A | view · diff |
| git:20260821.de017ea | 2026-08-21 | de017ea | 14,763 B | A | view · diff |
| git:20260803.a8156bc | 2026-08-03 | a8156bc | 13,024 B | A | view · diff |
| git:20260729.3ecb845 | 2026-07-29 | 3ecb845 | 12,280 B | A | view · diff |
| git:20260607.9863e04 | 2026-06-07 | 9863e04 | 15,352 B | A | view · diff |
| git:20260602.36355ae | 2026-06-02 | 36355ae | 14,636 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 (14304 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
ericrisco/rsc-harness · 236 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3vdzxferzkapyx7i GET https://markdownregistry.com/api/v1/resolve?ref=ericrisco/rsc-harness/clarify GET https://markdownregistry.com/api/v1/blob/bde50792a5acd0761d98e88db32b9eef31a5161936ef7f162de268826204dae7
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 ericrisco/rsc-harness
Every file in ericrisco/rsc-harness