---
name: Explain
slug: explain
category: Writing
description: Explains content or concepts at the requested depth (ELI5, practitioner, deep-dive) with a jargon glossary and context the original assumes, flagging oversimplifications or errors.
github: "https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain"
language: Python
stars: 125
forks: 7
install: "npx degit https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain ~/.claude/skills/explain"
installs_to: ~/.claude/skills/explain
source_path: skills/analysis/explain/SKILL.md
collection_size: 7
category_size: 1012
collection_url: "https://dirskills.com/collections/SerhiiKorniienko/bullshit-detector"
added: 2026-08-11T07:20:52.130Z
last_synced: 2026-08-11T07:20:52.130Z
canonical_url: "https://dirskills.com/skills/explain"
---

# Explain

Explains content or concepts at the requested depth (ELI5, practitioner, deep-dive) with a jargon glossary and context the original assumes, flagging oversimplifications or errors.

**Install:**

```bash
npx degit https://github.com/SerhiiKorniienko/bullshit-detector/tree/main/skills/analysis/explain ~/.claude/skills/explain
```

## README

# explain

Make the content understandable without dumbing it down dishonestly.

## Workflow

1. **Get the text** (via `fetch-content` skill script if it's a URL, else web fetch or paste).
2. **Pick the depth** — from the user's request, or ask one short question if genuinely unclear:
   - **ELI5** — analogies, zero jargon, the core mechanism only
   - **Practitioner** — assumes general technical literacy, focuses on how it works and what to do with it
   - **Deep dive** — mechanisms, edge cases, history, competing views
3. **Explain**, structured as:
   - The one-sentence version first
   - The mechanism: how it actually works, step by step
   - **Glossary**: every jargon term the content uses without defining, one line each
   - **What the content assumes you know** — the missing prerequisites that made it confusing
   - Where the content's own explanation is wrong or oversimplified, if it is — flag it, don't repeat it

## Rules

- Explaining ≠ endorsing. If the content's claim is contested, present the explanation *and* note the contest ("the video asserts X; the standard view is Y").
- Analogies must survive scrutiny — say where the analogy breaks.
- If the user points at a specific segment ("the part at 12:30", "section 3"), explain that segment in the context of the whole, not in isolation.
- Don't pad: a concept that takes three sentences gets three sentences.