eli5
Picks the form that explains best and applies the house explanation style: plain prose, controlled English modelled on ASD-STE100, a diagram, an interactive HTML page, or a narrated explainer video. Use when asked for "ELI5", "plain English", "re-pitch that", "stop using jargon", "explain it in STE100", "draw me a diagram of how this works", "make an interactive explainer", or "make a 3b1b style video on X".
- Installs
- 315
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/mblode/agent-skills --skill eli5- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads eli5 automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Plain-language house style
- IS NOT: product copy or documentation (use
ghostwriter), or slide decks (usepresentation-creator).
Use this style for the explanation requested. Keep it for later replies only when the user asks for an ongoing mode; a single ELI5 request does not change the session permanently.
- Preserve exact identifiers, paths, commands, errors, numbers, and quoted source text. Explain around them.
- Avoid minimizers: simply, obviously, just, easy, of course, as you know.
- No em dashes in authored prose; do not substitute a spaced hyphen. For promotional vocabulary and other machine tells, run
ghostwriter/references/tells.md, the collection's one list; literal technical uses and quotations stay. - Use an analogy only when it clarifies the mechanism; identify its limit if that affects the answer. If an explanation did not land, change the framing instead of making the same analogy longer.
- Put the explanation or result first. Include a next action only when the reader needs to act. Do not assign the user work the agent is already authorized to complete.
Return the explanation itself. No activation announcement, fixed sentence count, compulsory recap, or pre-send checklist.
Pick the form
Prose is the default. Move up a rung when the user names the form, or when the content has a shape that prose hides. Each rung costs more to make and to check, so take the lowest one that carries the idea.
| Form | Use when | Cost |
|---|---|---|
| Plain prose | Most answers | None |
| Controlled English | User asks for STE100 or "Simplified Technical English", or the answer is a procedure or a dense mechanism a non-native reader must follow | None |
| Diagram | Parts and the links between them, a sequence over time, states, or a data path | Low |
| HTML page | The reader learns by changing an input and seeing the result, or the topic needs several linked views | Medium |
| Explainer video | User asks for a video, or the idea is motion (an algorithm stepping, a curve changing) | High: render, narration, review |
When the user names a form, use it; do not argue down to prose. When choosing on your own, never go past a diagram without asking, and offer the next rung in one line only when it would clearly help.
"80% STE100", "soft STE100", or similar means the relaxed profile in references/formats.md, not the full specification. Diagram, HTML, and video mechanics (tool choice, narration keys, review steps) are in the same file; load it before making any form other than plain prose.
Boundaries
This changes assistant prose and the explanations it makes. Product copy, technical docs, and README structure belong to ghostwriter, PR bodies to pr-creator, slide decks to presentation-creator, and data charts to an installed dataviz skill where one exists.
Maintenance
evals/evals.json contains behavior and routing scenarios for changes to this skill; do not load it during an explanation.
FAQ
What does the eli5 skill do?
Picks the form that explains best and applies the house explanation style: plain prose, controlled English modelled on ASD-STE100, a diagram, an interactive HTML page, or a narrated explainer video. Use when asked for "ELI5", "plain English", "re-pitch that", "stop using jargon", "explain it in STE100", "draw me a diagram of how this works", "make an interactive explainer", or "make a 3b1b style video on X".
How do I install eli5?
Run npx skills add https://github.com/mblode/agent-skills --skill eli5 in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/eli5/ (personal) or .claude/skills/eli5/ (project).
Which AI agents can use eli5?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is eli5 safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains eli5?
It is published by mblode in mblode/agent-skills. It has 315 recorded installs.
More from mblode/agent-skills
ui-animation
mblode/agent-skills
Builds, reviews, and measures UI motion, including springs, gestures, scroll effects, curve fitting from recordings, and sparse interface sound. Use when asked to "add animation", "match this easing", "reverse engineer this motion", "add a click sound", or find animation opportunities.
multi-tenant-architecture
mblode/agent-skills
Designs tenant isolation, hostname routing, custom-domain lifecycle, and plan limits on Cloudflare or Vercel. Use when asked to "isolate tenant data", "support custom domains", "build a white-label platform", or assess PSL registration. For general module structure use codebase-architecture; for SEO content use seo.
ui-design
mblode/agent-skills
Designs and builds React/Next/Tailwind UI, audits visual and interaction defects, and stress-tests components with worst-case data. Use when asked to "build a landing page", "extract our design system", "add dark mode", "make this responsive", "remove UI slop", "audit this component", "stress-test this component", "break this UI", or "show me the worst case".
typography-audit
mblode/agent-skills
Audits font loading, type scales, measure, spacing, OpenType, and rendered punctuation with 78 scoped rules. Use when asked to "audit typography", "fix the fonts", or "review my type system". For a new visual direction use ui-design Direction; for general UI defects use ui-design Audit.
agent-skills-creator
mblode/agent-skills
Creates and improves portable Agent Skills with a validator, routing scenarios, and evidence-based keep, cut, merge, or retire decisions. Use when asked to "write a skill", "update all skills", "audit my SKILL.md", "remove redundant instructions", or fix skill triggering.
docs-writing
mblode/agent-skills
Writes and audits technical docs with Diataxis type gating, runnable examples, and 51 documentation rules. Use when asked to "review my docs", "write an API reference", or improve a documentation page. For a whole README use readme-creator; for agent instructions use agents-md.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown：查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件，或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.