deep-explainer skillA
deep-explainer is agent-read markdown (skill) from kaizakin/dotfiles: Use this skill whenever the user asks a question they want genuinely explained — especially while learning an unfamiliar codebase, repository, library, or technical concept. Trigger it for any question ending in a "?", any "what is/how does/why does X work" question, or any moment the user is confused about jargon, code, or architecture. Do NOT trigger it for quick factual lookups the user clearly just wants a short answer to (e.g. "what's the syntax for X", "what year was Go released"), for com.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Deep Explainer
## Why this skill exists
The default failure mode when explaining code or technical concepts is: short paragraphs, undefined jargon, and an assumption that the reader already has the background to fill in the gaps. That's fine for someone who already knows the domain. It's useless — even actively frustrating — for someone trying to actually learn something, like a contributor ramping up on an unfamiliar repository.
This skill's job is to make sure every explanation actually teaches, rather than just technically answering.
## When to use this
Trigger on:
- Any question (literally, ends in "?") about how something works, why it's designed a certain way, or what a piece of code/architecture does
- Questions asked while reading, exploring, or onboarding onto a repository or codebase
- Requests to explain a concept, library, pattern, or unfamiliar term
Do not trigger on:
- Quick lookups ("what's the flag for X", "what version is Y")
- DSA/competitive programming practice, if the user has indicated (in this conversation or from established preference) that they want terse, answer-only responses
- Any moment the user has explicitly asked to keep it short
…Read the whole file at its exact version.
How to install
mdr add kaizakin/dotfiles/deep-explainer@git:20260730.9ff9454mdr add kaizakin/dotfiles/deep-explainer@sha256:5deb6d51e026d96bPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_nlm35t5coicaywx2)
1 badge views in 30 days
Versions
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 (5993 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
kaizakin/dotfiles · 15 stars · license none · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nlm35t5coicaywx2 GET https://markdownregistry.com/api/v1/resolve?ref=kaizakin/dotfiles/deep-explainer GET https://markdownregistry.com/api/v1/blob/5deb6d51e026d96bccde670a1422cf8b9cdbf031a65ae9ab0b8dc951f0a06553
Your agent 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.