deep-clarify SKILL.md skillA
deep-clarify from chrono-meta/forge-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrono-meta/forge-harness/deep-clarify@git:20260811.eede7adPins git:20260811.eede7ad in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrono-meta/forge-harness
- Path
plugins/fh-meta/skills/deep-clarify/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260811.eede7ad, committed Aug 11, 2026
- First version recorded
- May 26, 2026
- Size
- 5,968 bytes
- Repository stars
- 31
- License
- MIT
Clarifies ambiguous requests through Socratic dialogue, drawing out goals, completion criteria, and constraints to produce a structured spec document. Pre-dispatch requirement clarification step for agent dispatch. Triggered by "I don't know what to build", "how should I approach this", "organize this for me", "clarify this", "deep-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
# deep-clarify — Socratic Requirement Clarification A skill that clarifies vague or open-ended requests through conversation to produce **actionable spec documents**. An independent extension of the "direction confirmation" protocol from agent-composer Step 0-a. ## Triggers - `/deep-clarify` - "I don't know what to build", "How should I approach this?" - "Organize the requirements", "Write a spec document" - "What should I do with this?", "The direction is unclear" - When agent-composer detects pre-dispatch clarification is needed and delegates automatically ## Core Principles **Criteria for asking vs inferring**: - Things only the human can know (goal, priorities, constraints, completion criteria) → ask - Things AI can infer (implementation method, file location, technology choices) → infer and present as `(inferred: X)` - Questions: **maximum 3 rounds, maximum 2 questions per round** — do not overuse --- ## Step 1. Request Analysis Quickly identify the following from the user's request. ``` Clarity check: □ Final state (what will be different when done?) — ask if unclear □ Completion criteria (how will it be verified?) — ask if unclear …
Read the whole file at its exact version.
How to install
mdr add chrono-meta/forge-harness/deep-clarify@sha256:480849f926c0dc63The line at the top of this page pins the label git:20260811.eede7ad, 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_plxtye6yjaeo4qqk)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 26, 2026 and Aug 11, 2026, about one every 77 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260811.eede7ad latest | 2026-08-11 | eede7ad | 5,968 B | A | view · diff |
| git:20260526.2de8630 | 2026-05-26 | 2de8630 | 4,388 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 (5968 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
chrono-meta/forge-harness · 31 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_plxtye6yjaeo4qqk GET https://markdownregistry.com/api/v1/resolve?ref=chrono-meta/forge-harness/deep-clarify GET https://markdownregistry.com/api/v1/blob/480849f926c0dc63fea677239672e7d6c8e974b40a18747f3c92402d6f5a4893
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.