Skip to content
Skills Library
AI & agents · Learning & explanation

explain-better

/explain-better

Explain a topic, code, or model output in a form that is easier to understand than plain prose. Picks one of four formats, from simple to rich - ASD-STE100 writing, a diagram, an HTML page, or an explainer video. Use when the user says "/explain-better", "help me understand", "explain this visually", "make a diagram of", "explain it as a page", or "make an explainer video". Based on Andrej Karpathy's tips for understanding LLM output.

Repository
skills ↗
Licence
MIT
Last repository change
07.10.2026

Assessment and security

90/ 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.
Content25 / 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 07.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

Explain a topic, code, or model output in a form that is easier to understand than plain prose. Picks one of four formats, from simple to rich - ASD-STE100 writing, a diagram, an HTML page, or an explainer video. Use when the user says "/explain-better", "help me understand", "explain this visually", "make a diagram of", "explain it as a page", or "make an explainer video". Based on Andrej Karpathy's tips for understanding LLM output.

Triggers from the description

help me understandexplain this visuallymake a diagram ofexplain it as a pagemake an explainer video

Arguments

/explain-better [format: writing|diagram|html|video] <topic or file>
Original author description

Explain a topic, code, or model output in a form that is easier to understand than plain prose. Picks one of four formats, from simple to rich - ASD-STE100 writing, a diagram, an HTML page, or an explainer video. Use when the user says "/explain-better", "help me understand", "explain this visually", "make a diagram of", "explain it as a page", or "make an explainer video". Based on Andrej Karpathy's tips for understanding LLM output.

How it works

  1. Pick the format
  2. 1. Writing: ASD-STE100
  3. 2. Diagram
  4. 3. HTML page
  5. 4. Explainer video (3Blue1Brown style)
  6. Rules
Original SKILL.md headings · 63 lines, 606 words
SKILL.md preview
---
name: explain-better
description: Explain a topic, code, or model output in a form that is easier to understand than plain prose. Picks one of four formats, from simple to rich - ASD-STE100 writing, a diagram, an HTML page, or an explainer video. Use when the user says "/explain-better", "help me understand", "explain this visually", "make a diagram of", "explain it as a page", or "make an explainer video". Based on Andrej Karpathy's tips for understanding LLM output.
argument-hint: "[format: writing|diagram|html|video] <topic or file>"
disable-model-invocation: true
---

Goal: help the user understand something fast. Oversight and understanding is the bottleneck now, not output. Output is cheap, so make a custom, throwaway artifact.

Input: `$ARGUMENTS`

## Pick the format

If the first word of the input is `writing`, `diagram`, `html`, or `video`, use that format. Otherwise pick the lowest rung that fits. Each rung is richer than the one before.

| Rung | Format | Use when |
| --- | --- | --- |
| 1 | ASD-STE100 writing | The idea is a sequence, a rule, or a definition. |
| 2 | Diagram | The idea has parts and links, a flow, or a hierarchy. |
| 3 | HTML page | The idea needs interaction, many diagrams, or animation. |
| 4 | Explainer video | The idea is a process that changes over time, and the user wants to watch it. |

Do not ask which format. State the pick in one line, then do it. If the user is unsure, offer the next rung up at the end.

## 1. Writing: ASD-STE100

ASD-STE100 is Simplified Technical English. It was made for aerospace maintenance manuals.

- Maximum 20 words per instruction sentence. Maximum 25 for descriptive text.
- One instruction per sentence.
- Active voice. Simple tenses. No `-ing` verb forms except technical nouns.
- One word for one meaning. Never rotate synonyms.
- Plain, short words. Define each technical term at first use.
- Paragraphs: one topic, maximum 6 sentences. Use lists for 3 or more steps.

The full spec is strict. If the result reads stiff, relax to "80% of the way to ASD-STE100": keep the short sentences and the one-word-one-meaning rule, and allow some passive voice and tenses.

## 2. Diagram

Load the `artifact-diagramming` skill first. Draw the real mechanism: the parts, the links, and the direction of data or control. Label every arrow with what travels on it. Use inline SVG or Mermaid. Add at most 3 sentences of text.

## 3. HTML page

Load the `artifact-design` skill, then build one self-contained `.html` file. Put these in it:

- A short summary at the top.
- Diagrams, with hover or click to show detail.
- Small interactive parts where they help (sliders, step buttons, toggles).
- No external build step.

Check the page with a headless browser tool such as Playwright. Open it in the browser with a local file URL.

## 4. Explainer video (3Blue1Brown style)

1. Write a short script first: 5 to 10 scenes, one idea per scene. Show the script to the user only if the topic is large.
2. Build the scenes with Manim (`pip install manim`) or Remotion. Use Manim for math and diagrams. Use Remotion for UI and text.
3. Narration, in this order:
   1. ElevenLabs, if the user has a key. Read it from an environment variable or a secrets manager. Never print the key or write it to a file. If no key is found, go to step 2.
   2. A free local option: macOS `say`, or Piper or Kokoro TTS.
4. Render to `.mp4`, then open it for the user. Name the output path in the reply.

Render a low-quality preview first (`manim -ql`). Render the final file only after the preview works.

## Rules

- Do not ship a diagram, page, or video for a trivial question. Use rung 1.
- Keep the artifact discardable. Write it in the scratchpad or a `explain/` folder, not in a project repo, unless the user names a path.
- End with one line: what was made, where it is, and what the next rung up would add.

Versions

The database has no other skills named explain-better.

Database snapshot: 13.11.2026 · package version c16b7169c950 (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

  • 100legible-explainer
    Explain a subject in the format that is easiest to understand, following Karpathy's output-format ladder: ASD-STE100 Simplified Technical English prose, then a diagram, then a self-contained HTML spec sheet drawn like an engineering drawing, then a narrated explainer video. Use…
  • 100explainer-formats
    Use when asked to explain a topic, codebase, process, or document in a specific output format — plain language or Simplified Technical English (STE, in the style of ASD-STE100 with its controlled vocabulary and short procedural sentences), a diagram (Mermaid, SVG, or an animated…
  • 90eli5
    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…
  • 95output-ladder
    Use when a user wants to understand or explain a topic and needs help choosing between writing, diagrams, interactive web pages, and explainer videos, or wants a reusable prompt for one of these formats.
  • 95asd-ste100
    Comprehensive ASD-STE100 Simplified Technical English (STE) skill and prompt compiler for Claude Code, OpenAI Codex, and LLMs. Repurposes aerospace maintenance controlled English to eliminate ambiguity in agent communications and human comprehension. Implements Andrej Karpathy's…
  • 100explain
    Use when the user wants to understand something rather than change it - "explain this", "what is X", "how does this work", "why does this happen", "what is going on here", "what caused this", "walk me through", "break this down", "teach me", "help me understand", "help me make…

Feedback and reports

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