eli5
/eli5
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.
- Author
- Kanevry ↗
- Repository
- session-orchestrator ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Arguments
/eli5 [topic]
Original author description
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.
How it works
- Invocation
- The frame
- What to restate
- Two limits, and they are the whole skill
- Shape
- What this is not
SKILL.md preview
--- name: eli5 description: 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. user-invocable: true argument-hint: "[topic]" model: inherit tools: Read, Grep, Glob, Bash --- # 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. - `/eli5 <topic>` — that topic (`$ARGUMENTS`), grounded in what THIS session already measured: name the file, command, or record it came from. If it was never measured here, say that rather than filling the gap from memory. Answer in the operator's language: `owner.language` in `~/.config/session-orchestrator/owner.yaml`, falling back to `en` when that file is missing, unreadable, or the key is absent — and follow the operator's own language the moment he writes in another one. ## Two limits, and they are the whole skill **1. Say more simply what actually happens — introduce nothing that does not exist.** Test: delete every noun the system does not contain. Sentence still true and complete → it was no analogy. Sentence collapses → describe what actually happens instead. ✓ "Waiting means the other session finishes first." ✗ "Think of the session as a level crossing." **2. Simplifying removes words, never facts.** If a path, a number, an error code, an identifier, or an instruction to act disappears, that is data loss, not simplification. The mechanical decider: **could the token you are about to cut ever appear in a `grep`? Then it stays.** `skills/session-start/soul.md` § "Never traded for brevity" outranks every brevity instruction in this file. ## Shape Line 1 answers the question he actually has: **do I have to do something now, and what happens if I don't?** Then the facts, in the order he needs them — not the order you found them. This is a terminal, so there is no picture to draw. The second channel is the `preview` field on an `AskUserQuestion` option: when the options differ in something literal — a diff, a title, a config block, a file list — put that text there and he reads the thing instead of a description of it. ## What this is not - **Not shorter by default.** Eight lines before may be eight lines after. Reorder first; cut only filler. - **Not a children's explanation.** The label is a poster, the reader is an expert who was not in the room. - **Not a second attempt at the answer.** If the first answer was wrong, fix the answer — `/eli5` restates, it never re-derives.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Kanevry/session-orchestrator | 100 | MIT |
| akillness/jeo-skills | 100 | MIT |
| jongio/skills | 100 | MIT |
| chanmuzi/git-claw | 100 | MIT |
| flc1125/skills | 100 | MIT |
| 609NFT/eli5 | 100 | MIT |
| yldio/skills | 100 | Apache-2.0 |
| mblode/agent-skills | 90 | MIT |
| piabrota/nix-os | 90 | MPL-2.0 |
Database snapshot: 13.11.2026 · package version fd7dd314933d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90restate
When the user wants the last reply said again in plain words, wants a catch-up since their last message, or wants the decision they need to make. - 82ase-meta-eli5
Explain a topic in "Explain Like I'm 5" (ELI5) style, optionally grounded in Internet/Web facts. Use when the user wants a topic explained in a very simple, child-friendly way, or mentions "eli5" or "explain like I'm 5". - 92say-it-plain
Explains any topic so the reader understands it on the first read, with the answer first and short, plain sentences. Use when the user asks for a clear, simple, or to-the-point explanation of anything, or says they did not understand something. - 100kiss
Explain a technical topic to a developer the keep-it-simple way, as one plain HTML page. A short route of the whole flow comes first, then one stamped step per stop, each with a big flat drawing on the left and a few words with the real names on the right. Use when the user… - 100feynman-technique
Coach the user through the Feynman Technique to deeply understand a topic by explaining it in simple words, finding gaps, relearning, and simplifying. Use when the user wants to truly understand (not memorize) a topic they studied, says "Feynman technique", "explain it like I'm… - 90plain
Re-explain the previous answer, or rewrite a named document, in plain teaching English for a newcomer to the field, with every term defined and every code explained in words. Use when the reader says an answer was cryptic, jargon-heavy or hard to follow, or asks for /plain.