agentleFS
Sign inStart free
IvanGomezMartinezIvanGomezMartinez/MatStudyLab/.agents/skills/explain/SKILL.md

explain

Skill2 starsChanged 3 months agoMITView on GitHub

Deep-study a MATLAB script and write explain_<stem>.md without changing .m files.

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

9 rules. 0 are common, 1 is distinctive, and 8 are 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.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read LORE.md, AGENTS.md, docs/spec.md, and CONTEXT.md before acting.

    line 9
  2. Very specific:

    Read and execute .agents/skills/matstudylab-bootstrap/SKILL.md before any other step.

    line 13
  3. Distinctive:

    Do not proceed until bootstrap completes (skip, setup/update, or warn-and-continue).

    line 14
  4. Very specific:

    Read LORE.md for companion language and lab context.

    line 39
  5. Very specific:

    If a matching bundle exists in codes/<type>/<bundle>/, recommend:

    line 69
  6. Very specific:

    If the script has no catalog bundle yet, suggest /build or /new first, then /accept for the staging bundle.

    line 77
  7. Very specific:

    Write only under explain/.

    line 83
  8. Very specific:

    Never modify .m files.

    line 84
  9. Very specific:

    Never edit codes/ in situ.

    line 85

“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

Produce explain_<stem>.md in explain/ for one script per session. Read-only on .m files — never edit codes/, new/, modify/, or import/ in place.

Read LORE.md, AGENTS.md, docs/spec.md, and CONTEXT.md before acting. Use docs/templates/explain-doc.md for structure.

Step 0 — Bootstrap (mandatory)

Read and execute .agents/skills/matstudylab-bootstrap/SKILL.md before any other step. Do not proceed until bootstrap completes (skip, setup/update, or warn-and-continue).

Completion criterion: bootstrap outcome identified (skip, setup/update OK, or warn-and-continue).

Step 1 — Parse invocation

User inputBehavior
/explainResolve a single .m under explain/, or list choices if several
/explain <script.m>Study that script (paths under explain/, codes/, new/, modify/)
/explain <script.m> <question>Same + answer the question in Your questions

No grill-me — didactic, one-way mode.

Completion criterion: target script path is identified.

Helper:

./scripts/explain-resolve.sh list
./scripts/explain-resolve.sh resolve <hint>

Step 2 — Read context

Read LORE.md for companion language and lab context. Read the target .m and its base companion .md when present (codes/ is read-only context).

Apply zoom-out when the script is long, has non-obvious dependencies or toolboxes, or the user gave a hint — read related files under the same bundle before writing.

Completion criterion: script purpose and optical context are understood.

Step 3 — Write explain doc (explain/ only)

Resolve output path:

./scripts/explain-resolve.sh resolve <hint>

Scaffold if needed, then fill content in the user's language:

./scripts/explain-resolve.sh scaffold <hint> "<optional question>"

Required sections (see docs/templates/explain-doc.md):

  • Possible improvements (not implemented) — ideas only, no code changes
  • MATLAB concepts — plain-language teaching
  • Your questions — when the user provided a hint

Completion criterion: explain_<stem>.md exists under explain/ with all required sections; no .m file was modified.

Step 4 — Recommend /accept explain

If a matching bundle exists in codes/<type>/<bundle>/, recommend:

/accept explain

or /accept explain <type> <bundle> when scope should be one bundle. This copies explain_<stem>.md into the catalog (see .agents/skills/accept/SKILL.md).

If the script has no catalog bundle yet, suggest /build or /new first, then /accept for the staging bundle.

Completion criterion: user knows the next command to attach the study doc.

Safety (non-negotiable)

  • Write only under explain/.
  • Never modify .m files.
  • Never edit codes/ in situ.

Reference

  • Wayfinder spec: .scratch/matstudylab/issues/09-grilling-comando-explain.md
  • Explain template: docs/templates/explain-doc.md
  • Handoff: use .agents/skills/handoff/SKILL.md to compact context before generating the doc when zoom-out applies

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