Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and every schema change.
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
# ELI5
Turn the referenced spec or change into an accurate mental model for a technical
reader who does not live in the code. Plain language, full precision: simplify
the telling, never the claims.
## The Register
Other skills point here when their output must be readable by someone who
didn't live the work. The reader is technical — pseudocode and precise claims
land fine — but they have read none of the code and none of the session's
messages: no diff, no transcript, no labels the work invented along the way.
Writing ELI5 means:
- Walk one concrete scenario end to end — the triggering event, what happens
today, what the change (or the unbuilt alternative) would do — instead of
describing properties in the abstract.
- Define every term of art at first use; never lean on labels the spec, code,
or session invented.
- Use small concrete examples without replacing precise claims with analogies.
- Reach for pseudocode when explaining control flow, ordering, or timing.
Prose describing when-something-fires reads as plausible and hides the gap;
five lines of pseudocode make the gate visible and let the reader see the
…
The line at the top of this page pins the label git:20260813.f2a4f7b, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_iajkc7mtagx7cm7u
GET https://markdownregistry.com/api/v1/resolve?ref=dzhng/duet-agent/eli5
GET https://markdownregistry.com/api/v1/blob/268c996bcc62796e31ca74105929c77907e4b4e1abda3341b9a01b9cd2059004
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.
dzhng/duet-agent · .agents/skills/audit-agents/SKILL.md · Audit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never…
dzhng/duet-agent · .agents/skills/audit-choices/SKILL.md · Audit the choices an implementing agent made, not its diff — a pure decision audit that traces the session's history…
dzhng/duet-agent · .agents/skills/audit-tests/SKILL.md · Audit whether tests earn their maintenance cost and which suite owns each contract. Use when pruning redundant tests…
dzhng/duet-agent · .agents/skills/claude/SKILL.md · Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent…
dzhng/duet-agent · .agents/skills/close-spec/SKILL.md · When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec)…
dzhng/duet-agent · .agents/skills/code-review/SKILL.md · Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing…
dzhng/duet-agent · .agents/skills/codex/SKILL.md · Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second…
dzhng/duet-agent · .agents/skills/compare-screenshots/SKILL.md · Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for…
dzhng/duet-agent · .agents/skills/design-with-images/SKILL.md · Explore UI and visual design with image generation, then iterate the real implementation against the user-selected…
dzhng/duet-agent · .agents/skills/eval-skills/SKILL.md · Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each…
dzhng/duet-agent · .agents/skills/explore-unknowns/SKILL.md · Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work…
coldteadotai/pr-lens · skills/eli5/SKILL.md · WHAT: Explains a codebase, a folder, a feature, a command or a pull request to someone who knows nothing about it, as a…
dzhng/skills · skills/engineering/eli5/SKILL.md · Explain a technical spec or proposed change in plain language: what problem it solves, how the solution works, and…
dcouple/pane · main/src/services/paneChatBundle/skills/eli5/SKILL.md · Teach an unfamiliar topic from first principles with a picture-first HTML explanation, saved in Grain when connected…
greenfield-inc/pane · main/src/services/paneChatBundle/skills/eli5/SKILL.md · Teach an unfamiliar topic from first principles with a picture-first HTML explanation, saved in Grain when connected…
mblode/agent-skills · skills/eli5/SKILL.md · Picks the form that explains best and applies the house explanation style: plain prose, controlled English modelled on…
doodledood/manifest-dev · claude-plugins/manifest-dev-tools/skills/eli5/SKILL.md · Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture…
naveedharri/benai-skills · plugins/all-skills/skills/eli5/SKILL.md · Explain a topic like I'm a 5 year old. Use when the user types /eli5 [topic] or asks for a dead-simple picture…
kanevry/session-orchestrator · .cursor/skills/eli5/SKILL.md · Explain a topic like I'm a 5 year old — restate my last output, or a named topic, in plain words without dropping a…
