Some concepts are genuinely hard to hold in your head as plain text. Tax brackets, how compound interest erodes purchasing power, the way a neural network layers its decisions — words alone often fail. Claude has a built-in skill called ELI5 that sidesteps this problem by generating a self-contained HTML visual instead of a wall of prose.
Type /eli5 followed by your topic, and Claude doesn’t just explain it — it renders it.
What the ELI5 Skill Actually Produces
The output is a small, styled HTML page you can open directly in a browser. It’s built around diagrams, color-coded breakdowns, and simple labels — the kind of thing a good teacher would draw on a whiteboard. It’s not a chatbot response dressed up with a header. It’s a genuine visual artifact.
Take something like how a Roth IRA works. A text explanation will tell you about post-tax contributions and tax-free growth. The ELI5 visual will show you two timelines side-by-side — money going in after taxes on one, a growing balance with no tax drag on the other — so the advantage clicks immediately rather than after three re-reads.
Or try /eli5 explain how DNS resolves a domain name. Instead of a numbered list of steps, you get a diagram of the request bouncing from your browser to a resolver to root servers to the authoritative nameserver and back, each hop labeled in plain language.
Why Visual Output Changes How You Absorb Information
Reading that interest compounds means something. Seeing a bar that doubles, doubles again, and then doubles again makes it land differently. Cognitive load drops when the structure of an idea is externalised into a shape you can scan.
This is especially true for:
- Hierarchical concepts — things with layers, like how a bill becomes law, or how an operating system is organized above hardware
- Flow-based processes — anything with steps that depend on the previous one, like how blood moves through the heart or how an API call travels through a backend
- Comparative ideas — two options side by side, like renting vs. buying or TCP vs. UDP
- Proportional relationships — budgets, tax rates, time allocations where you want to see the size of each piece
If you’re trying to learn something new and you feel like the explanation isn’t sticking, that’s usually a signal the format is wrong, not that the topic is too hard.
How to Use It Well
The slash command is the trigger: /eli5 [your topic]. You can open a new conversation in Claude and use it right away — no setup required.
A few things that make the output better:
Be specific about the angle you want. /eli5 explain how marginal tax rates work for someone earning $85,000 will produce a tighter, more useful visual than /eli5 taxes. The more Claude knows about your context, the more relevant the labels and numbers will be.
Ask for a specific type of visual if you have one in mind. You can append something like “show it as a flowchart” or “break it down as a proportional diagram” and Claude will lean that direction.
Paste the HTML into your browser. Claude will display a preview in some interfaces, but if it shows you raw code, just copy it, save it as a .html file, and open it. Takes ten seconds.
Iterate. If the first visual gets the concept mostly right but misses something, tell Claude what to adjust. “Add a step showing what happens if the request times out” or “make the federal vs. state distinction clearer” both work well as follow-ups.
When Text Is Still Better
ELI5 isn’t the right tool for everything. If you need a precise definition, a nuanced argument, or step-by-step instructions you’ll follow while doing something, plain prose is faster and cleaner. The visual format shines when the relationship between parts is the thing you’re trying to grasp — not a single fact.
It’s also not great for very abstract philosophical ideas where there’s no underlying structure to map. Trying to visualize “the nature of consciousness” will produce something that looks organized but probably won’t illuminate much.
The Underlying Habit Worth Building
The real value here isn’t the ELI5 command specifically — it’s the habit of asking yourself what format would make this click fastest. Sometimes that’s a visual. Sometimes it’s an analogy. Sometimes it’s a worked example with real numbers.
Claude’s skills are a shortcut to some of those formats, but you can prompt your way to all of them without a slash command too. ELI5 just makes the visual path frictionless enough that you’ll actually take it.
Next time a concept isn’t sticking after two or three explanations, stop asking for another explanation. Ask for a picture instead.
