agentleFS
SerhiiKorniienkoSerhiiKorniienko/bullshit-detector/skills/analysis/explain/SKILL.md

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

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.
  • zebbernSkill

    debug-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

  • Ingramradical235Skill

    root-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

  • ralphkraussSkill

    resolve-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

  • neurofooSkill

    socratic

    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

  • anombyte93Skill

    discover

    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

  • abdullah1854Skill

    pr-summary

    Also in 3 projects that use this

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
  1. Distinctive:

    Glossary: every jargon term the content uses without defining, one line each

    line 20
  2. Distinctive:

    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 …

    line 28
  3. Distinctive:

    Don't pad: a concept that takes three sentences gets three sentences.

    line 29

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.