recap-ask SKILL.md skillA
recap-ask from sd0xdev/sd0x-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sd0xdev/sd0x-harness/recap-ask@git:20260905.d98c025Pins git:20260905.d98c025 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sd0xdev/sd0x-harness
- Path
skills/recap-ask/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260905.d98c025, committed Sep 5, 2026
- First version recorded
- Apr 17, 2026
- Size
- 12,036 bytes
- Repository stars
- 194
- License
- MIT
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap-<date>.md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code tracing (use /code-explore). Output: per-turn answer referencing file:line + end-of-session promote prompt.
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
# `/recap-ask` — Recap-Bounded Q&A ## Trigger - Keywords: recap-ask, ask about recap, 追問 recap, follow-up on recap, 本輪問答 ## When NOT to Use | Scenario | Alternative | |----------|------------| | Generate a new recap doc from scope | `/recap-doc` | | Full flow (detect + doc + Q&A) | `/post-dev-recap` wrapper | | General project Q&A, no recap in hand | `/ask` | | Deep multi-source investigation | `/deep-research` | | Systematic code tracing across modules | `/code-explore` | | First-principles reasoning about a doc | `/fp-brief` | ## Command Signature ``` /recap-ask <question> --context <recap-doc-path> [--continue <threadId>] [--lazy-fetch] ``` | Flag | Default | Description | |------|---------|-------------| | `<question>` | required | Free-text user question | | `--context` | required | Absolute or repo-relative path to a `briefing-recap-<YYYY-MM-DD>.md` file | | `--continue` | null | Reuse an existing Codex threadId for follow-up turns | …
Read the whole file at its exact version.
How to install
mdr add sd0xdev/sd0x-harness/recap-ask@sha256:889adc2a85d14b91The line at the top of this page pins the label git:20260905.d98c025, 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_tr7vn7g2ir7q5t3v)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 17, 2026 and Sep 5, 2026, about one every 71 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.d98c025 latest | 2026-09-05 | d98c025 | 12,036 B | A | view · diff |
| git:20260811.d9a8bca | 2026-08-11 | d9a8bca | 11,855 B | A | view · diff |
| git:20260417.ef6942e | 2026-04-17 | ef6942e | 10,211 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 (12036 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
sd0xdev/sd0x-harness · 194 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tr7vn7g2ir7q5t3v GET https://markdownregistry.com/api/v1/resolve?ref=sd0xdev/sd0x-harness/recap-ask GET https://markdownregistry.com/api/v1/blob/889adc2a85d14b91661aae10b68d3073f4b8250a82632603103c33272c900a96
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.