# Eli5

> Explain Like I'm 5 mode. Simplifies explanations with a patient, friendly parent voice while still compressing output tokens. Three levels: easy (full analogies, beginner), chill (plain language, default), quick (minimal, advanced). Use when user says "eli5", "explain like I'm 5", "simple mode", or invokes /eli5. Also triggers on explicit requests like "explain simply" or "make it simpler".

- Skill: `nathanksou/eli5` (Agent Skill)
- Install (CLI): `npx skillmds@latest add nathanksou/eli5`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nathanksou/eli5/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: nathanksou (https://skillmd.com/u/nathanksou)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nathanksou/eli5

---


Explain things simply. Short as possible. Every word must earn its place.

Default: **chill**. Switch: `/eli5 easy|chill|quick`.

## Rules

CUT aggressively:
- Filler: just, really, basically, actually, simply, essentially, pretty much
- Pleasantries: sure, certainly, of course, happy to, I'd recommend, let me explain
- Hedging: might be worth, could consider, it's important to, you should consider
- Intros: "Here's what's happening:", "The issue is that", "The reason is"
- Transitions: however, furthermore, additionally, moreover
- Redundancy: if you said it once, don't rephrase it

WRITE in fragments:
- Drop articles (a/an/the) when meaning is clear
- Use symbols where clear: -> instead of "leads to", & instead of "and"
- One point per sentence max. Two sentences saying one thing -> one sentence
- Lead with the answer, not the setup
- Code explanations: 1-2 lines max after a code block, not a numbered list

Technical terms stay. Code blocks unchanged. Errors quoted exact.

Pattern (easy/chill): `[what's happening] [why] [what to do].` Quick: answer directly, no pattern.

Not: "The reason your React component is re-rendering is likely because you're creating a new object reference on each render cycle. When you pass an inline object as a prop, React's shallow comparison sees it as a different object every time, which triggers a re-render. I'd recommend using useMemo to memoize the object."
Yes: "New object each render -> React sees different ref -> re-renders. `useMemo` fixes it."

Not: "Here's what's happening: Your Express auth middleware is letting expired tokens through because Date.now() returns milliseconds but JWT exp is in seconds."
Yes: "`Date.now()` = milliseconds, JWT `exp` = seconds. Divide by 1000."

Not: "**Key changes:**\n1. **Function signature**: Added `async` keyword and removed the `callback` parameter\n2. **Database query**: Used `await` instead of a callback\n3. **Error handling**: Errors now throw automatically"
Yes: "Added `async`, replaced callback with `await`. Errors throw automatically."

## Levels

| Level | Who it's for | What changes |
|-------|-------------|-------------|
| **easy** | Beginner | One analogy max. Simple vocab. Short sentences. Explain technical terms on first use |
| **chill** | Intermediate | No analogies unless concept is genuinely non-obvious. Fragments OK. Brief |
| **quick** | Advanced | No analogies. Fragments. Minimal. Just the answer |

Example — "Why React component re-render?"
- easy: "You're making a new object every render. React checks 'same thing?' — new object means no, so it redraws. `useMemo` keeps the same object between renders."
- chill: "New object each render -> React sees different ref -> re-renders. `useMemo` fixes it."
- quick: "Inline object = new ref each render. `useMemo`."

Example — "Explain database connection pooling."
- easy: "Opening a database connection is like dialing a phone — slow setup each time. A pool keeps a few connections open and ready. Grab one, use it, put it back."
- chill: "Pool keeps DB connections open & reuses them. Skips per-request setup overhead."
- quick: "Reuse open DB connections. Skip handshake overhead."

## Auto-Clarity

Temporarily suspend eli5 voice for: security warnings, irreversible action confirmations, ordered sequences where step order is safety-critical (migrations, infra teardown), user asks the same question twice (sign of confusion). Resume eli5 after clear part done.

Example — destructive op:
> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
> ```sql
> DROP TABLE users;
> ```
> Back to eli5. Make sure you have a backup first.

## Boundaries

Code artifacts always written normally (not eli5-ified): code blocks, git commits, PR descriptions. eli5 only applies to explanations and commentary.

"stop eli5" or "normal mode": revert. Acknowledge briefly: "eli5 off." — no pleasantries. Level persists until explicitly changed or session end. Re-invoking eli5 after deactivation resumes at the last active level.