Skip to content
Back to skills

Charles Eli14

ASecurity

Explain anything the way a great teacher would explain it to a sharp 14-year-old with no background in the topic: short and clear, the answer first, every key term kept and defined in plain words, and an analogy only where an idea is genuinely hard. Use when someone says explain like I'm 14, eli14, eli5, explain it simply, in plain English, break it down, I don't get it, or what does X actually mean, or asks what something is or how it works and wants to understand it rather than get a summary.

  • 189 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 18, 2026

npx -y skills add LemonFace0309/charles-skills --skill charles-eli14 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Charles Eli14?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Charles Eli14
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lemonface0309-charles-eli14/badge)](https://www.skillsdirectory.com/skills/lemonface0309-charles-eli14)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: charles-eli14
description: "Explain anything the way a great teacher would explain it to a sharp 14-year-old with no background in the topic: short and clear, the answer first, every key term kept and defined in plain words, and an analogy only where an idea is genuinely hard. Use when someone says explain like I'm 14, eli14, eli5, explain it simply, in plain English, break it down, I don't get it, or what does X actually mean, or asks what something is or how it works and wants to understand it rather than get a summary."
---

# Goal

The reader is a sharp 14-year-old: quick, curious and good at following logic, with no background in this topic. When they finish, they can explain the idea to a friend in their own words, and at no point did they feel talked down to. Get them there in as few words as the idea allows.

# Steps

Walk all seven, even for a one-paragraph answer.

## 1. Pick the one idea

Before writing, finish this sentence for yourself: "If they remember one thing, it's that ___." Every sentence in the answer either builds toward that sentence or gets cut.

Why: explanations get confusing when they try to cover everything. One idea built properly beats five ideas mentioned.

## 2. Answer first

The first one or two sentences answer the actual question (what it is, how it works, why it happens) using only words a 14-year-old already knows. The detail comes after.

Why: a reader who knows where you're heading can place each detail as it arrives. Holding back the point makes them carry every detail in their head until the end.

## 3. Build from zero, in order

- Introduce every idea before you use it. Never point at something the reader hasn't seen: "as mentioned", "the usual approach", "the standard fix", "this is why X matters" when X was never explained, or an acronym, product or person dropped in without a word about what it is.
- Go in this order: what it is, how it works step by step, one concrete example with real numbers or a real case, then why it matters or where they'll run into it.
- One new idea per paragraph, and paragraphs of one to three sentences.

Why: a smart reader with no context gets lost at the first reference they can't place, and everything after it stops making sense.

## 4. Keep the real terms, and define them

For every technical term:

```
Do they need this term to understand the idea, or will they meet it again?
├── Yes → keep the real word, bold it the first time, and define it in the same sentence in plain words:
│         "Your screen is a grid of **pixels**, tiny squares that each show one colour."
└── No → leave it out. Don't name things they don't need.
```

- Never swap a real term for a baby word ("the computer's brain" for a CPU). Why: the real word is the one they'll hear in class, search for and see again. A stand-in leaves them stuck the next time.
- Spell out an abbreviation the first time ("a GPU, the graphics processing unit, ..."), then use the short form.
- Define a term by what it does or what it is, using words they already know. If the definition needs another new word, define that one first or find a different definition.
- At most four new terms per answer. Why: past four, they're memorising a glossary instead of understanding. If the topic needs more, cover the first layer and offer the next one.

## 5. Use an analogy only where it earns its place

```
Is this part invisible, abstract or counter-intuitive (electricity, encryption, probability, compound interest)?
├── No → explain it directly. A concrete thing never needs an analogy.
└── Yes → one analogy from everyday life, then:
          1. map it out loud ("the water pressure is the voltage, the pipe is the wire"),
          2. say where it breaks, in one clause ("unlike water, the electrons barely move"),
          3. go back to the real thing.
```

At most one analogy per answer, two only if the answer covers two genuinely hard ideas. Never use one as decoration.

Why: a good analogy makes an abstract idea graspable in one move. Every extra one makes the answer feel written for a child, and an analogy without its limit teaches something false.

## 6. Sound like a person

- Write the way a great teacher talks: "you", short sentences, concrete nouns, real numbers ("a 1080p screen has about 2 million pixels").
- Never write "great question", "simply put", "it's easy", "just" (as in "just do X"), "obviously" or "basically". Why: they pad the answer, and the ones that call it easy make a reader who's stuck feel slow.
- Never announce a move before making it: no "here's an analogy", "this is where an analogy helps", "let's break it down" or "here's the thing". Use the analogy, break it down. Why: the announcement is filler, and it makes the answer read like a script.
- Never use exclamation marks or emoji.

## 7. Check it as the reader

Read the answer as the 14-year-old and fix whatever fails:

- Could they answer the original question in their own words now? If not, the one idea from step 1 is missing or buried.
- Is there a word they'd have to look up? Define it or cut it.
- Does any sentence point at something they haven't seen? Rewrite it.
- Would any sentence be true of almost any topic? Cut it.
- Length: "what is X" is 80 to 200 words, "how does X work" is 150 to 350, and an explanation they asked to go deep on can run longer, split under plain headings. Why: past the point of understanding, every extra sentence competes with the ones that matter.

When the answer runs past 150 words, end with the one-line version: "So, in one line: ___." Offer a next step only when there's an obvious next layer ("Want to know why ___?"). Never quiz them unless they ask.

# Deliver

Plain prose in the chat, or in whatever they're writing if they asked for it there. Headings only past about 300 words. Bullets only for things that really are a list (steps in order, or a few parallel items).

Files in this skill

  • README.md2.3 KB
  • SKILL.md5.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.