agentleFS
Sign inStart free
nearmapnearmap/shipyard/skills/explain/SKILL.md

explain

Skill1 starsChanged 21 days agoMITView on GitHub

Teach one gnarly topic (a bug family, a design constraint, a system) until you genuinely understand it: author a verified, layered explainer doc through an isolated investigation, then walk it with you one layer at a time, with checkpoints, live repros on challenge, and a decision — never a lecture — as the endpoint. Never reads or writes the tracker.

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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 109 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No tracker read or write, at any point — this is about your understanding, not the project record.

    line 27
  2. Very specific:

    Every subagent dispatch resolves its model and effort from config and passes them as the Agent invocation's actual model and effort …

    line 29

“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

Two modes. If $ARGUMENTS names an existing explainer doc, run it. If it names a topic, author one first, then offer to run it.

$ARGUMENTS

Author

Delegate the investigation to sy:explain-author — an isolated context, so its file reads and repro attempts never enter this session. Seed the prompt with every anchor already in hand: paths, symbols, the commit, the plan/gate/CI finding that made this worth explaining. It writes the doc itself to <topic>_explainer.md in the topic's resolved scratch directory (scratch_dir(<topic-slug>)) and returns only a compact brief — the resolved doc path, layer count, the one surprising rule, and how many claims are verified versus inferred.

Present that brief as a Status update, then close with one optional suggestion (${CLAUDE_PLUGIN_ROOT}/skills/shared/references/user-interaction.md): walk it here now, or run claude "/sy:explain <doc path>" in a new session for a clean slate before something like a merge. Never block on it — proceed either way.

Run

references/running.md owns the walk: one layer per turn, an AskUserQuestion checkpoint after each, live repros the moment something is challenged, a decision (not a fact) at the end.

No tracker read or write, at any point — this is about your understanding, not the project record.

Every subagent dispatch resolves its model and effort from config and passes them as the Agent invocation's actual model and effort parameters, per ${CLAUDE_PLUGIN_ROOT}/skills/shared/references/model-dispatch.md; a nested dispatch inherits nothing and must resolve again.

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