deepen SKILL.md skillA
deepen from dylan/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dylan/skills/deepen@git:20261109.5ef7913Pins git:20261109.5ef7913 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dylan/skills
- Path
plugins/rigor/skills/deepen/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261109.5ef7913, committed Nov 9, 2026
- Size
- 5,292 bytes
- Repository stars
- 2
- License
- none declared
Deepens a task prompt before it runs. It names what a top professional in the field would do that the prompt doesn't ask for, the rawest material they would start from, the methods and tools they would use, and a check outside the model and the user that would show the result is right. Then it rewrites the prompt to ask for exactly that. Use when the user runs /deepen, asks to deepen, sharpen or level up a prompt or task, asks how an expert would approach something, or wants expert-grade work…
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
# Deepen Make the task deeper without making it bigger. The skill produces a better prompt; it doesn't do the work. ## What makes this work Each part of the method closes a gap between an amateur request and professional work. - Depth, not breadth. The rewrite keeps the original goal and scope and adds no deliverables. It changes how the work is done and what counts as done. - Diagnosis first. The user sees the four answers before the rewrite, and the rewrite asks only for what those answers justify. - A named professional. Asking what a top practitioner would do brings in the steps they take for granted, which the user didn't know to ask for. - Raw material. Summaries, articles and earlier answers carry someone else's framing and errors. Starting upstream lets the work find what the summary dropped. - Named methods and tools. A method with a name can be run, checked and repeated; "analyze it carefully" can't. - An outside check. The model grading its own work proves nothing, and neither does the user eyeballing it. Only a check that can disagree with both of them turns an opinion into a result. ## Input …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_va5mhm7ltc5hklra/0e925cbda93e84b51a1221b1ee9dfca3017b38538e9f3dc3794d18dc4333f603.json
Then /plugin install deepen@markdownregistry-va5mhm7ltc5hklra in Claude Code. It installs git:20261109.5ef7913, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add dylan/skills/deepen@sha256:0e925cbda93e84b5The line at the top of this page pins the label git:20261109.5ef7913, 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_va5mhm7ltc5hklra)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in dylan/skills/deepen since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of deepen from somewhere else? Ask it: where did my deepen come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 9, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/deepen/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (5292 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
dylan/skills · 2 stars · license none declared · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_va5mhm7ltc5hklra GET https://markdownregistry.com/api/v1/resolve?ref=dylan/skills/deepen GET https://markdownregistry.com/api/v1/blob/0e925cbda93e84b51a1221b1ee9dfca3017b38538e9f3dc3794d18dc4333f603
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.