Eli5

Explain a previous response or requested technical topic in plain language. Use when the user asks for an ELI5 explanation or invokes /eli5; preserve the claims and match the source length.

5 starsOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Magnus-Gille/claude-skills --skill eli5
Manual install
git clone --depth 1 https://github.com/Magnus-Gille/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/eli5 ~/.claude/skills/eli5

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /eli5 — Explain Like I'm 5

Explain the requested source in plain language. Use the immediately previous assistant
message when the user points to the previous answer; otherwise use the named topic,
document, error, decision, or workflow.

## Rules

1. **Same content, simpler form.** Cover the same points as the selected source. Don't drop information; translate it.
2. **No jargon.** If a technical term is unavoidable, define it inline the first time. ("aider — a command-line tool that lets an AI edit code")
3. **Short sentences.** Aim for ~15 words per sentence. Break up long ones.
4. **Concrete over abstract.** Replace "harness misconfiguration" with "I was running the tool with the wrong settings."
5. **Tables stay if useful.** Numbers and comparisons survive translation; the surrounding prose gets simplified.
6. **Don't apologize or preface.** Just give the simpler explanation. No "Sure, here's an easier version:" — start with the content.
7. **Match length to the original.** A short message gets a short re-explanation. A long one gets a similarly long but simpler one. Don't pad.

## What this is NOT

- Not a summary. Cover everything, just in simpler words.
- Not dumbed-down to the point of being wrong. Accuracy stays.
- Not a different answer. Same conclusions, same recommendation.

## Example

Previous message: "The harness misconfig invalidated prior aider+qwen-coder ranking. Real picture: aider and opencode are comparable when aider has per-task file scope."
Read the full skill on GitHub

Details

Skill name
eli5
Path
eli5/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Eli5 skill do?

Explain a previous response or requested technical topic in plain language. Use when the user asks for an ELI5 explanation or invokes /eli5; preserve the claims and match the source length.

How do I install the Eli5 skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Magnus-Gille/claude-skills --skill eli5. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Eli5 popular?

It lives in Magnus-Gille/claude-skills, which has 5 GitHub stars and 0 forks.

Related skills

Close

5

Magnus-Gille/claude-skills

Close a coding-agent session or produce its final handoff only when the user explicitly asks to close, wrap up, or produce an end-of-session handoff.

AI, LLMs & Agents

Cloudflare Private Static Site

5

Magnus-Gille/claude-skills

Create, preview, test, release, verify, or roll back a small static Cloudflare site protected by per-person HTTP Basic Auth. Use for private briefings, reports, one-pagers, document portals, or similar sites that should go from finished content to a custom domain in about ten minutes. Do not use for full applications or when the user requires SSO, identity lifecycle, or Cloudflare Access policy management.

DevOps & Cloud

Code Friction

5

Magnus-Gille/claude-skills

Capture a small, opt-in set of concrete code-changeability observations during a coding task and hand them to Close without affecting readiness.

Software Development

Presentify

5

Magnus-Gille/claude-skills

Create a self-contained HTML one-page briefing from supplied material.

Other

Bun YAML

9

jarle/bun-skills

Use Bun's built-in support for YAML files through both runtime APIs and bundler integration

Other

Refining Requirements

5

tomada1114/tomada-claude-plugins

Turn a vague app idea or an incomplete spec into a signed-off, implementation-ready requirements document through repeated rounds of structured questioning, acting as the PdM while the user plays the client. Each round also scrutinizes the draft — contradictions, missing flows, unstated edge cases, MVP bloat, conflicts with the template or stack — and turns what it finds into the next questions, until the user signs off. Produces features with concrete values, an explicit MVP / Later / Non-goals split, and cross-cutting rules. Use when asked to refine or detail a spec, PRD, or app idea, when s

Other

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.