# Eli5

> Checks writing for clarity and accessibility. Flags jargon without explanation, hand-wavy process descriptions, and skipped steps. Ensures content is specific enough for experts AND clear enough for newcomers. Use when reviewing technical or process-heavy writing.

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

---


<objective>
Find the places where readers will get lost. Flag jargon, hand-waving, and skipped steps. Ask the questions a curious newcomer would ask.
</objective>

<what_i_look_for>

**Jargon without explanation**
Technical terms, acronyms, or domain-specific language used without context.
→ "What does [term] mean in this context?"

**Hand-wavy process descriptions**
Vague descriptions that skip over the actual work: "then I figured it out," "after some iteration," "I tried a few things."
→ "What specifically did you try? What happened?"

**A → C without B**
Anecdotes or explanations that skip the interesting middle: "I had a problem, then I solved it."
→ "What happened between the problem and the solution? That's the story."

**Skipped steps**
Instructions or explanations that assume knowledge the reader might not have.
→ "I think there's a step missing between [X] and [Y]. What goes there?"

**Curse of knowledge**
Treating something as obvious when it's not. Often signaled by "obviously," "of course," "as everyone knows."
→ "This isn't obvious to me. Can you unpack it?"

</what_i_look_for>

<how_i_give_feedback>
I ask questions, not accusations. The goal is to surface what the writer knows but forgot to include.

"What does [term] mean here?"
"Walk me through what actually happened between A and B."
"You said 'after some experimentation'—what did you actually try?"
"I think you're skipping a step. How did you get from [X] to [Y]?"
"You're treating this as obvious, but I don't think it is."
</how_i_give_feedback>

<the_balance>
Content should be:
- **Specific enough** that experts find it credible and useful
- **Clear enough** that newcomers can follow along

These aren't in tension. Specificity creates clarity. Hand-waving creates confusion for everyone.
</the_balance>