agentleFS
Sign inStart free
whyashthakkerwhyashthakker/estack/skills/explain/SKILL.md

explain

Skill0 starsChanged 11 days agoMITView on GitHub

Explain code, a concept, a diff, or what the agent just did, in layers that match the user's level. Starts with one plain sentence, then goes deeper only as far as needed, with a small diagram or example. Use when the user says "explain", "what does this do", "I don't get this", "walk me through", "ELI5", "how does X work", or asks about a file, function, error, or term.

122 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 10 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

  • mitsuhikoSkill

    summarize

    Fetch a URL or convert a local file (PDF/DOCX/HTML/etc.) into Markdown using `uvx markitdown`, optionally it can summarize

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 109 edited versions we read keep these.

  • 5

    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:

    Use what you already know about the user (their questions, their code, their role).

    line 12
  2. Distinctive:

    Stop at the layer that answers the question.

    line 16
  3. Distinctive:

    Go deeper: Only if asked: edge cases, history (git log -L or git blame when "why" matters), alternatives.

    line 26
  4. Distinctive:

    Use the user's real code and names in examples, not foo/bar.

    line 31
  5. Distinctive:

    If you are not sure how something works, read the code or run it.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 109 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

Goal: the user understands the thing well enough to change it or decide about it. Not a lecture. Not a tour of everything.

1. Find the level

Use what you already know about the user (their questions, their code, their role). If you do not know, assume a smart person who is new to this exact topic. Do not ask about level unless the answer would change a lot.

2. Write in layers

Stop at the layer that answers the question. The user can ask for more.

  1. One sentence. What it is or does, in plain words, with no jargon. "This function retries a failed payment up to three times, then gives up."
  2. Why it exists. The problem it solves. One to three sentences.
  3. How it works. The main steps in order. Use a short numbered list or a small ASCII diagram for flows:
    request -> check cache -> hit? -> return
                        \-> miss -> call API -> save -> return
  4. The tricky part. The one thing that surprises people or causes bugs here. Point to the exact line (file:line).
  5. Go deeper. Only if asked: edge cases, history (git log -L or git blame when "why" matters), alternatives.

3. Rules

  • Define each new term the first time, in six words or fewer. "Idempotent (safe to run twice)".
  • Use the user's real code and names in examples, not foo/bar.
  • One idea per paragraph. Short sentences.
  • If you are not sure how something works, read the code or run it. Say "I checked" or "I did not check". Never guess and present it as fact.
  • For "what did you just do": list each change, why you made it, and what the user should check.

4. Close the loop

End with one line: the single most useful thing to remember. If the topic is worth keeping, offer quiz-me.

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.

Check your setup, free