teach
Skill102 starsChanged 34 days agoMITView on GitHub
Explain what was just built, a specific pattern or concept, or any topic the developer wants to learn — calibrated to their experience level. Asks once what level of explanation they want, then goes deep on the what, why, when, and tradeoffs. Works from code just written in the session, a pasted snippet, or a topic described from scratch.
194 other projects use a version of this.
Adopted by
Most recently taken up by
- TencentBlueKing/bk-litetheir own version, first seen Nov 16, 2026
- devdeepjs/kobayashi-marutheir own version, first seen Nov 16, 2026
- qelphybox/tg-mcptheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- adamos486/skultotheir own version, first seen Nov 16, 2026
- shiwenbin1617/pstacktheir own version, first seen Nov 16, 2026
Used with
Projects with it also use setup-pstack, principle-explain-the-number 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.
bnemaSkillsetup-pstack
Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.
Also in 22 projects that use this
ianclearySkillprinciple-explain-the-number
Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.
Also in 25 projects that use this
jaydubya818Skillpoteto-mode
Use when non-trivial work should follow the smallest rigorous Jstack workflow.
Also in 27 projects that use this
eryzerzSkillmake-bot-ui
Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.
Also in 17 projects that use this
jaydubya818Skillprinciple-never-block-on-the-human
Apply when safe reversible implementation details can proceed inside scope.
Also in 36 projects that use this
ianclearySkillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 12 projects that use this
- +6 more from jaydubya818
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- mattpocock/skills★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- withcoral/coral★ 5ksame name
- backnotprop/pstack★ 4.2ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 161 edited versions we read keep these.
8
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
- Distinctive: line 12
Before asking anything, figure out what the developer actually has.
- Distinctive: line 18
Read what was built. Identify two or three specific things worth teaching — patterns used, decisions made, approaches taken that a …
- Distinctive: line 33
Wait for their choice. Then go to Step 2.
- Distinctive: line 43
Do not present options. You already know what to teach.
- Distinctive: line 63
Wait for their answer. Then go to Step 2.
- Distinctive: line 69
Ask once per session. If the level was already established earlier in this session, skip this and use the remembered level.
- Distinctive: line 166
After the explanation, ask one question to verify they followed — not a quiz, a prompt for genuine engagement:
- Distinctive: line 176
Do not ask multiple questions.
“Common” is measured: kept by at least 6 in 10 of the 161 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.
Files
Good code without understanding is just copy-paste with extra steps. This skill turns what was built — or what was pasted, or what was asked — into a real learning moment. Not a surface-level description of what the code does. The actual reasoning: why this approach, what it trades off, when you'd use it differently, and what a senior engineer would think looking at it.
Step 1 — Detect the Situation
Before asking anything, figure out what the developer actually has.
Situation A — Something was just built in this session
The conversation has recent code, a completed feature, or a finished implementation. The developer typed /teach with no specific topic.
Read what was built. Identify two or three specific things worth teaching — patterns used, decisions made, approaches taken that a developer might not fully understand even if they prompted for them.
Present the options:
I can see we just built [feature]. Here are the most
interesting things worth understanding from this session:
1. [Pattern or decision — one line description]
2. [Pattern or decision — one line description]
3. [Pattern or decision — one line description]
Which one do you want to dig into?Wait for their choice. Then go to Step 2.
Situation B — They pasted something specific or named a topic
The developer typed something like:
/teach why did you use a singleton here/teach explain this useEffect pattern/teach how does JWT authentication work/teach [pasted code snippet]
Do not present options. You already know what to teach. Go straight to Step 2 with their specific topic.
Situation C — Nothing to work from
The developer typed /teach with no argument and there is nothing recently built in this session to draw from.
Ask directly:
What do you want to learn about?
You can ask about something specific:
- A concept ("how does database indexing work")
- A pattern ("explain the repository pattern")
- A language feature ("what is TypeScript's type narrowing")
- A decision ("when should I use useCallback")
Or just describe what you're curious about and I'll go from there.Wait for their answer. Then go to Step 2.
Step 2 — Establish the Level
Ask once per session. If the level was already established earlier in this session, skip this and use the remembered level.
Before I explain — how do you want me to pitch this?
1. Plain English, no assumed knowledge — I'll explain
everything from the ground up
2. I know the basics, skip the fundamentals — assume
I understand core concepts
3. I'm comfortable with concepts, give me the depth —
tradeoffs, edge cases, the real reasoning
4. Peer level — don't simplify, treat me like a
senior engineer
Which fits?Remember this level for the rest of the session. Do not ask again on subsequent /teach calls.
Step 3 — Teach It
Now explain. The depth and language change based on level, but the structure is always the same. Every explanation covers five things — skip none of them, but calibrate how deep each one goes.
What it is
State what the pattern, concept, or approach actually is. No assumed knowledge at Level 1. Brief at Level 4.
Level 1 example: "A singleton is a pattern that makes sure only one instance of something ever exists. Think of it like a single shared whiteboard — everyone in the room reads from and writes to the same board, rather than each person having their own."
Level 4 example: "This is a module-level singleton — the Node.js module cache ensures the exported instance is only instantiated once per process, which is the idiomatic approach for shared resources like database connections."
Why this approach was chosen
This is the most important part. Not just what it is — why here, in this specific code, for this specific problem.
For Situation A (built in this session): tie it directly to the actual code. "We used this because..." not "this is used when..."
For Situations B and C: explain the most common reason this approach is chosen, and what problem it's solving.
At every level, name at least one alternative that was not chosen and briefly explain why this won over it.
When you would use this
Give the developer a mental model for when to reach for this pattern in their own future work.
Be specific. Not "use this when you need to share state" — "use this when you have an expensive resource to initialise once (database connection, config loader, cache) and multiple parts of your codebase need access to the same instance."
At Level 1 and 2, give a concrete real-world analogy first, then the technical version. At Level 3 and 4, go straight to technical criteria.
When you would NOT use this
This is what separates real understanding from surface knowledge. Every pattern has cases where it's wrong, and knowing those is what makes a developer trustworthy with the pattern.
Name at least one situation where using this approach would be a mistake and why.
At Level 1: keep it simple, one clear case. At Level 3 and 4: go into the failure modes, the subtle misuses, the cases that look like a fit but aren't.
What a senior engineer thinks about this
This section is what makes the JSM teach skill different. Not "here's what the code does" — here's how someone with years of experience would evaluate it.
Adapt by level:
Level 1 and 2:
A senior engineer looking at this would think: [positive
observation about what was done correctly, and one thing
they'd watch for as the codebase grows]Level 3 and 4:
Senior read on this: [honest assessment — what's good,
what's a potential footgun, what would make this cleaner,
and what the production concerns are at scale]Be honest here. If the pattern used has a real weakness in the specific context — say so. This is a learning moment, not a validation.
Step 4 — Check Understanding
After the explanation, ask one question to verify they followed — not a quiz, a prompt for genuine engagement:
Does that land?
If anything felt unclear or you want to go deeper on
[the most complex part of what was just explained] —
just say so.Do not ask multiple questions. One invitation to continue. If they have a follow-up question, answer it at the same level, using the same structure where it helps.
What This Skill Is Not
Not a code generator. This skill explains — it does not write new code, modify existing code, or fix bugs. If the developer needs code written, that belongs in the core loop with /plan and build.
Not a surface-level describer. "This function takes two parameters and returns their sum" is not teaching. Teaching is why that function exists, what it trades off, when you'd write it differently, and what breaks if you misuse it.
Not a one-size-fits-all explainer. The level the developer sets changes everything — language, depth, analogies, assumed knowledge. A Level 1 explanation that gets given to a Level 4 developer is condescending. A Level 4 explanation given to a Level 1 developer is useless. The level question is not optional ceremony — it is the most important input this skill receives.
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.

