explain
Skill151 starsChanged 2 months agoMITView on GitHub
Explain content or any concept inside it at the depth the user needs — ELI5, practitioner level, or expert deep-dive — with a jargon glossary and context the original assumes. Use when the user says "explain this", "what does X mean here", "break this down", "I don't understand this part", or shares content and asks how something in it works.
127 other projects use a version of this.
Adopted by
Most recently taken up by
- samsam007b/claude-code-standards-kittheir own version, first seen Nov 16, 2026
- librosdeia/builder-method-claude-plugintheir own version, first seen Nov 15, 2026
- dafto1/skillstheir own version, first seen Nov 15, 2026
- Soe-Reh/soes-skillstheir own version, first seen Nov 15, 2026
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- AmrSabbagh35/project-explainertheir own version, first seen Nov 15, 2026
Used with
Projects with it also use debug-fix, root-cause and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
zebbernSkilldebug-fix
Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)
Also in 3 projects that use this
Ingramradical235Skillroot-cause
Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.
Also in 5 projects that use this
ralphkraussSkillresolve-conflicts
Resolve git merge conflicts or re-apply changes from a stale branch onto current main. Use when user says "resolve conflicts", "merge conflicts", "rebase branch", "branch is behind", "re-apply changes", "port branch", or a branch is too far behind main to merge cleanly.
Also in 4 projects that use this
neurofooSkillsocratic
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
Also in 4 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 6 projects that use this
abdullah1854Skillpr-summary
Also in 3 projects that use this
Other versions127 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 127
- Z3Prover/z3★ 13ksame name
- crbnos/carbon★ 2.8ksame name
- poshan0126/dotclaude★ 871same name
- VinkyDev/vibestart★ 295same name
- hsantanna88/clo-author★ 262same name
- hugosantanna/clo-author★ 262same name
- entireio/skills★ 240same name
- sammcj/agentic-coding★ 169same name
- kv0906/pm-kit★ 138same name
- penwyp/ClaudePreference★ 136same name
117 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bullshit-detectorSkill
- summarizeSkill
- coverage-checkSkill
- fetch-contentSkill
- report-cardSkill
- shareSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 115 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Glossary: every jargon term the content uses without defining, one line each
- Distinctive: line 28
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 …
- Distinctive: line 29
Don't pad: a concept that takes three sentences gets three sentences.
“Common” is measured: kept by at least 6 in 10 of the 115 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
explain
Make the content understandable without dumbing it down dishonestly.
Workflow
- Get the text (via
fetch-contentskill script if it's a URL, else web fetch or paste). - 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
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

