Explain Like I'm Five
Most explanations fail because they're pitched at the wrong level — experts use jargon and assume prerequisites, simplifiers strip away so much that the explanation becomes misleading. Explain Like I'm Five gives you three layered explanations of the same concept: an analogy a child could follow, a working explanation for a smart adult, and an expert-level version that satisfies the edge cases.
What this skill does
Each level builds something different. Level 1 gives you intuition — you feel the shape of the concept viscerally and could sketch it on a napkin. Level 2 gives you competence — you could use the concept in a meeting, make a decision involving it, or explain it to a colleague. Level 3 gives you mastery — you understand the edge cases, where the simple model breaks down, and what experts disagree about. Most learners need all three. The intuition anchors. The competence enables use. The depth keeps you honest about the limits.
The analogy in Level 1 is the hardest part and the most important. A good analogy is directionally correct — it simplifies without lying. A bad analogy is cute but creates a misconception that Level 2 has to undo. "The internet is a series of tubes" is famously bad because it builds a wrong mental model of packet routing. The skill tests each analogy against this question: where does it break? If it breaks at the very next level of understanding, it gets replaced. If it breaks at the expert level, that's fine — Level 3 will address it.
The skill is opinionated about when not to do all three levels. A genuinely simple concept (a URL, an HTTP status code, a variable) gets one clear explanation and a "going deeper" note, not three forced levels. A topic that's actually a field — "explain machine learning" — gets narrowed first, because no real concept-explainer can compress an entire discipline into 600 words without lying. If you say "I only need the simple version", you get the simple version and nothing else, because the user's stated need beats the template.
What you don't get: condescension. No "simply put", no "in other words", no "essentially" — those words signal that the writer thinks the harder version was too hard for you, which is its own kind of insult. The user chose their level. The skill respects it.
When this triggers
- ·You half-understand a concept and want it explained without the jargon shield
- ·You're teaching something and need versions of the same idea for different audiences
- ·You read the Wikipedia article and feel more confused than before
- ·You want to know specifically where the simple version of an idea stops being accurate
- ·You've memorised a definition but realise you couldn't explain it to a friend
Example
Trigger
User: 'Explain recursion at 3 levels. I'm a non-programmer.'
Output
## Level 1: The Simple Version Imagine you're standing in a queue and want to know your position. You can't see the front. So you tap the person in front of you and ask "what number are you?" They don't know either, so they tap the next person. It keeps going until someone at the front says "I'm number 1." Then the answer travels back: "I'm 2." "I'm 3." Each person solved the same problem by asking the same question to the person in front of them. ## Level 2: The Real Version Recursion is when a function solves a problem by calling itself on a smaller version of the same problem. Two things make it work: a base case (the person at the front who knows their number) and a recursive case (everyone else, who defers to the person in front). Without a base case, the function calls itself forever and crashes. The common misconception: people think recursion is a loop. It isn't — each call creates a new copy of the function on a stack. ## Level 3: The Full Picture [Stack frames, tail-call optimisation, when recursion outperforms iteration and when it doesn't, the equivalence with mathematical induction, where the queue analogy breaks down — namely, real function calls don't pass information backwards through a chain; each frame returns to the one that called it.] ## Quick Reference One-sentence definition: A function calling itself on a smaller version of its own problem until it hits a base case. Key insight: every recursive solution implies a base case and a smaller subproblem — if either is missing, it's not recursion. Common misconception: it's a loop. It isn't.
Get this skill + 7 more
Get the full Learning & Growth pillar (8 skills) or the complete library.
Get the full stack — $299What you get
- 175-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Learning & Growth
Takes a topic — any topic — and map the landscape of ideas within it: what the core concepts are, how they relate to each other, which ones are foundational (everything depends on them) and which are…
When someone presents a position, argues the other side — not as a lazy contrarian, but as the most informed, thoughtful version of the opposition
Takes any learning material — notes, articles, textbook chapters, lectures — and create flashcards optimised for long-term retention
Doesn't quiz to confirm what someone knows — it quizzes to find what they *don't* know and force them to confront it
When someone asks "How good am I at X?", most people lie — friends encourage, colleagues hedge, and AI assistants default to flattery
Takes "I want to learn X" and turn it into a structured, realistic learning path with clear phases, time estimates, the right resources at each stage, and milestones that tell the user when they're…
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles