dr-capture-request SKILL.md skillA
dr-capture-request from ahepi/deepreason is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ahepi/deepreason/dr-capture-request@git:20260730.6cf4d20Pins git:20260730.6cf4d20 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ahepi/deepreason
- Path
.claude/skills/dr-capture-request/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260730.6cf4d20, committed Jul 30, 2026
- Size
- 2,233 bytes
- Repository stars
- 141
- License
- MIT
Record an operator's suggested change verbatim and split it into numbered requirements (REQUEST.md). First phase of every change tranche; no interpretation, no code reading.
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
# Capture the request
Input: the operator's message(s). Output: `REQUEST.md`. You quote; you
do not paraphrase, improve, or fill gaps. Interpretation happens in
`dr-spec-change`, where it is visible and reviewable — not here, where
it would silently replace the operator's words.
## Procedure
1. Copy the operator's suggestion VERBATIM into a quoted block. If the
suggestion spans several messages (including earlier in the
conversation), quote each with its position. Do not trim "context"
— trimmed context is how inputs get forgotten.
2. Split into atomic requirements R1..Rn. Atomic = one testable
obligation each. Split conjunctions ("do X and then Y" → R1: X,
R2: Y). Keep the operator's own words in each requirement; add
nothing.
3. Capture constraints stated anywhere in the conversation that bind
this change (deadlines, "don't touch X", style preferences, budget
remarks like "prioritise this"). These become C1..Cn with verbatim
quotes.
4. Mark each requirement's kind: `behavior` (code must act
differently), `artifact` (a file/document/skill must exist),
`process` (how the work must be done, e.g. "commit as you go").
…Read the whole file at its exact version.
How to install
mdr add ahepi/deepreason/dr-capture-request@sha256:d500ad66125d5805The line at the top of this page pins the label git:20260730.6cf4d20, 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_4i2f2hpwslihvsxy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 30, 2026.
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 (2233 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
ahepi/deepreason · 141 stars · license MIT · pushed 2026-09-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4i2f2hpwslihvsxy GET https://markdownregistry.com/api/v1/resolve?ref=ahepi/deepreason/dr-capture-request GET https://markdownregistry.com/api/v1/blob/d500ad66125d5805a0829c934d918c3294336c817f219862b4c048c369146e1f
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.