kit-explain
Skill6 starsChanged 27 days agoMITView on GitHub
Problem / Solution / How it works plus one compact mermaid for a PR or short HLD. Use to explain a change — not for ASCII brainstorm boards or full design grilling.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- kit-audit-metricsSkill
- kit-audit-skillsSkill
- kit-capture-lessonSkill
- kit-challenge-designSkill
- kit-check-blastSkill
- kit-create-prSkill
- kit-debate-decision-treeSkill
- kit-debug-prodSkill
- kit-decisionsSkill
- kit-evolveSkill
- kit-learn-repoSkill
- kit-minimizeSkill
- kit-optimize-contextSkill
- kit-planSkill
- kit-proveSkill
- kit-reviewSkill
- kit-strip-diffSkill
- kit-triage-commentsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Very specific: line 13
Not a substitute for kit-challenge-design or kit-plan
- Distinctive: line 14
Not a gallery of diagrams — one diagram unless the user asks for more
- Distinctive: line 27
If the diagram exposes disagreement or a missing decision → stop and ask before more writing.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Explain
Reviewer-skim shape: Problem / Solution / How it works + one small mermaid.
What this is NOT
- Not a substitute for
kit-challenge-designorkit-plan - Not a gallery of diagrams — one diagram unless the user asks for more
Output shape
- Problem — 2–4 sentences.
- Solution — what we do and what we don’t.
- How it works — short steps.
- Mermaid — prefer
sequenceDiagramfor request/cred/flows;flowchartfor branching decisions. Minimal nodes/labels. - Optional: open questions with proposed options (no bare open questions).
Rules
- Diagram must match the prose — no decorative boxes.
- If the diagram exposes disagreement or a missing decision → stop and ask before more writing.
- For publish targets that don’t render mermaid, say so and offer image export — keep mermaid as source when in-repo.
- Generic names only in public examples (no employer hosts/paths).
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.

