Skip to content
Skills Library
Education · Learning & explanation

tiny-tale

/tiny-tale

Explains any technical or complex topic (programming, AI, networking, finance, medicine, science, law) with a very short, very simple story a 5-year-old could follow, then maps the story back to the real concept. Use when the user says "tiny tale", "explain like I'm 5", "ELI5", "explain with a story", "explain it simply", or says they don't get a concept and want it made intuitive. Not for requests that need precise technical detail, code review, or debugging.

Repository
ReWord ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Explains any technical or complex topic (programming, AI, networking, finance, medicine, science, law) with a very short, very simple story a 5-year-old could follow, then maps the story back to the real concept. Use when the user says "tiny tale", "explain like I'm 5", "ELI5", "explain with a story", "explain it simply", or says they don't get a concept and want it made intuitive. Not for requests that need precise technical detail, code review, or debugging.

Triggers from the description

tiny taleexplain like IELI5explain with a storyexplain it simply
Original author description

Explains any technical or complex topic (programming, AI, networking, finance, medicine, science, law) with a very short, very simple story a 5-year-old could follow, then maps the story back to the real concept. Use when the user says "tiny tale", "explain like I'm 5", "ELI5", "explain with a story", "explain it simply", or says they don't get a concept and want it made intuitive. Not for requests that need precise technical detail, code review, or debugging.

How it works

  1. Rules
  2. Format
  3. Going deeper
  4. Accuracy
  5. Self-check
  6. Example
Original SKILL.md headings · 78 lines, 508 words
SKILL.md preview
---
name: tiny-tale
description: Explains any technical or complex topic (programming, AI, networking, finance, medicine, science, law) with a very short, very simple story a 5-year-old could follow, then maps the story back to the real concept. Use when the user says "tiny tale", "explain like I'm 5", "ELI5", "explain with a story", "explain it simply", or says they don't get a concept and want it made intuitive. Not for requests that need precise technical detail, code review, or debugging.
---

# Tiny Tale

One idea, one tiny story, then the real term. If a 5-year-old couldn't follow the story, it's too complicated. Simpler beats complete.

## Rules

1. **One idea.** The single most important one. Drop the rest, however true; offer it later.
2. **One or two characters.** A plain name (Mia, Ravi) or "a girl", "a fox". A group ("her friends") counts as one.
3. **One problem, one fix.** Something is hard, someone tries a smarter way, it gets better. No subplot, no twist.
4. **Small words.** Words a young child knows. Sentences under 12 words. No technical terms or brand names in the story.
5. **Everyday things.** Toys, snacks, cups, boxes, buses, blocks, stickers, and things every Indian kid knows: a lunch dabba, a cricket bat, kites, a chai stall, an auto-rickshaw, a school bag. No settings that need explaining (offices, banks, servers).
6. **Map at most 3 parts.** A detail that maps to nothing gets cut.
7. **50-100 words.**
8. **Tone:** warm and plain. The reader is smart and new to this. No baby talk, at most one "!".
9. **Language:** match the user. If they ask in Hinglish, tell the tale in simple Hinglish.

## Format

**The tale**
(50-100 words)

**In real life**
> tale thing = real term
> (max 3 lines)

**Where it breaks**
(one sentence: where the tale misleads or what it leaves out)

**The simple truth**
(one plain sentence with the proper term; it may name one key part the tale skipped, if "Where it breaks" mentions it)

**Go deeper?**
(one line offering the next level)

## Going deeper

On "go deeper": 2-3 short paragraphs with real terms, one step more technical, not expert level. Keep the same tale as the anchor. Offer the next level after.

## Accuracy

Simple, not wrong. If the analogy would teach a false idea, pick another or flag it in "Where it breaks". Unsure of a detail: leave it out.

## Self-check

Rewrite shorter and simpler if any answer is no:
- Under 100 words?
- Two characters or fewer?
- One problem, one fix?
- Would a 5-year-old know every word?
- Does every detail map to something real?
- "In real life" 3 lines or fewer?

## Example

**User:** tiny tale, what is an API?

**The tale**
Ravi wants a snack from a big box machine. He can't open it. He can't see inside.

But the machine has buttons. Ravi presses B2. Clunk. Chips drop out.

He doesn't know how the machine works inside. He only needs the right button, and the machine does the rest.

**In real life**
> snack machine = another program
> buttons = the API
> chips dropping out = the response

**Where it breaks**
A real API also takes things in, like a form you send, not only gives things out.

**The simple truth**
An API is a set of agreed requests one program can make to another without knowing how the other works inside.

**Go deeper?**
I can explain it with endpoints, requests, and responses.

Versions

The database has no other skills named tiny-tale.

Database snapshot: 13.11.2026 · package version e68fc73b259d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95curious-kid
    Explains any technical or complex topic (programming, ML, networking, finance, medicine, science, etc.) using a very short, very simple story that a 5-year-old could follow, then maps the story back to the real concept. Use when the user asks to "explain like I'm 5", "ELI5",…
  • 100concept-explainer
    Explains complex or technical concepts clearly at the right level for the audience, using layered depth, concrete analogies, worked examples, and checks for understanding — adapting from ELI5 to expert. Use this skill when the user asks to "explain X", "ELI5", "help me…
  • 100eli5
    Create a simple, picture-first explanation of a topic, defaulting to self-contained HTML. Use when the user says ELI5, asks to explain something like they are five, or wants a visual explanation with very few words; do not use for ordinary concise explanations that do not ask for this style.
  • 82ase-meta-eli5
    Explain a topic in "Explain Like I'm 5" (ELI5) style, optionally grounded in Internet/Web facts. Use when the user wants a topic explained in a very simple, child-friendly way, or mentions "eli5" or "explain like I'm 5".
  • 100kiss
    Explain a technical topic to a developer the keep-it-simple way, as one plain HTML page. A short route of the whole flow comes first, then one stamped step per stop, each with a big flat drawing on the left and a few words with the real names on the right. Use when the user…
  • 100explain-concept
    Use when a concept needs making clear rather than practising: explain simply, why does this exist, draw it, or simplify for a beginner. Not for scaffolded practice: use drill.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.