Explain a topic like I'm a 5 year old — restate my last output, or a named topic, in plain words without dropping a single fact. Use when the user types /eli5 [topic], or says an answer was too technical, too long, or unclear about what he now has to do.
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
Say it again in plain words. Same facts, in the order he needs them.
## Invocation
Invoked as `/eli5 [topic]` with arguments: **$ARGUMENTS**.
The argument is optional and is a topic, in prose. If `$ARGUMENTS` is empty, the target is my own last substantial output in this conversation; if there is none yet, say so rather than picking a topic for him.
- `/eli5` — restate what I just said.
- `/eli5 warum ist der Regel-Korpus voll?` — explain that, grounded in what this session measured.
## The frame
**Write for someone who knows this project but has not seen what you just saw.**
He owns this repo. He is not missing knowledge, he is missing observation — he did not watch the command run or read the file it points at. Write across, not down. `.claude/rules/ask-via-tool.md` § AUQ-006 and `skills/session-start/soul.md` § Register are the canonical statement of this register; apply them, do not restate them.
## What to restate
- `/eli5` — my last substantial output in this conversation. If there is none yet, say so instead of inventing a topic.
…
The line at the top of this page pins the label git:20260916.3ebf0e9, 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_hijz6mzksqe2pme6
GET https://markdownregistry.com/api/v1/resolve?ref=kanevry/session-orchestrator/eli5
GET https://markdownregistry.com/api/v1/blob/fb939da858116266b68e83c84f5f62e7ac2e151f9506a90bce97ff5e25f5f56d
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.
kanevry/session-orchestrator · .agents/skills/architecture/SKILL.md · Use when the user asks to improve architecture, find refactoring opportunities, surface deepening opportunities…
kanevry/session-orchestrator · .agents/skills/autopilot/SKILL.md · Use this skill when running an autonomous session-orchestration loop. Chains session-start → session-plan →…
kanevry/session-orchestrator · .agents/skills/bootstrap/SKILL.md · Use this skill when scaffolding the minimum repository structure required by session-orchestrator. Invoked…
kanevry/session-orchestrator · .agents/skills/brainstorm/SKILL.md · Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue…
kanevry/session-orchestrator · .agents/skills/claude-md-drift-check/SKILL.md · Use when detecting drift between CLAUDE.md (or AGENTS.md, the Codex CLI alias) / _meta narrative and live repository…
kanevry/session-orchestrator · .agents/skills/debug/SKILL.md · Use when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging…
kanevry/session-orchestrator · .agents/skills/deepen/SKILL.md · Make a task deeper, not bigger. Use when the user asks for a deeper or more ambitious version of a task (tiefer, geh…
kanevry/session-orchestrator · .agents/skills/discovery/SKILL.md · Use this skill when running systematic quality discovery and issue detection. Runs modular probes adapted to the…
kanevry/session-orchestrator · .agents/skills/dispatcher/SKILL.md · Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates…
kanevry/session-orchestrator · .agents/skills/docs-orchestrator/SKILL.md · Use this skill when orchestrating documentation generation and updates within a session. Maps session scope to…
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, published to the workspace's…
greenfield-inc/pane · main/src/services/paneChatBundle/skills/eli5/SKILL.md · Teach an unfamiliar topic from first principles with a picture-first HTML explanation, published to the workspace's…
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…
agentbull/ankole · app/library/agent-plugins/methodology/skills/eli5/SKILL.md · Explain a certain topic in an easy-to-understand way. Use when the user asks for a dead-simple picture explainer of how…
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…
