deep-dive SKILL.md skillA
deep-dive from akillness/jeo-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add akillness/jeo-skills/deep-dive@git:20260728.4f971c4Pins git:20260728.4f971c4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- akillness/jeo-skills
- Path
.agent-skills/deep-dive/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260728.4f971c4, committed Jul 28, 2026
- First version recorded
- May 30, 2026
- Size
- 26,677 bytes
- Repository stars
- 52
- License
- none declared
Cross-runtime 2-stage pipeline for Claude Code, Codex/OMX, and Gemini/Antigravity/OMA: trace causal hypotheses, inject evidence into deep-interview style requirements crystallization, then hand off to the right runtime planner/executor.
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
<Purpose> Deep Dive orchestrates a 2-stage pipeline that first investigates WHY something happened (trace) then precisely defines WHAT to do about it (deep-interview). The trace stage runs 3 parallel causal investigation lanes, and its findings feed into the interview stage via a 3-point injection mechanism — enriching the starting point, providing system context, and seeding initial questions. The result is a runtime-portable spec grounded in evidence, not assumptions. </Purpose> <Use_When> - User has a problem but doesn't know the root cause — needs investigation before requirements - User says "deep dive", "deep-dive", "investigate deeply", "trace and interview" - User wants to understand existing system behavior before defining changes - Bug investigation: "Something broke and I need to figure out why, then plan the fix" - Feature exploration: "I want to improve X but first need to understand how it currently works" - The problem is ambiguous, causal, and evidence-heavy — jumping to code would waste cycles </Use_When> <Do_Not_Use_When> - User already knows the root cause and just needs requirements gathering — use `/deep-interview` directly …
Read the whole file at its exact version.
How to install
mdr add akillness/jeo-skills/deep-dive@sha256:4da31085cf75ec3dThe line at the top of this page pins the label git:20260728.4f971c4, 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_jrqxrwuccr4yrfc4)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 30, 2026 and Jul 28, 2026, about one every 15 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.4f971c4 latest | 2026-07-28 | 4f971c4 | 26,677 B | A | view · diff |
| git:20260626.48fd3af | 2026-06-26 | 48fd3af | 26,670 B | A | view · diff |
| git:20260626.4f9b684 | 2026-06-26 | 4f9b684 | 26,667 B | A | view · diff |
| git:20260530.9827c65 | 2026-05-30 | 9827c65 | 27,003 B | A | view · diff |
| git:20260530.b9e7496 | 2026-05-30 | b9e7496 | 26,519 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 (26677 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
akillness/jeo-skills · 52 stars · license none declared · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jrqxrwuccr4yrfc4 GET https://markdownregistry.com/api/v1/resolve?ref=akillness/jeo-skills/deep-dive GET https://markdownregistry.com/api/v1/blob/4da31085cf75ec3d1e3d29b04fcc5651a6953bfe34478be3c75326330101289d
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 akillness/jeo-skills
Every file in akillness/jeo-skills