Explains how code works and why it was built that way in plain language.
npx skills add https://github.com/jnyross/pstack-muse --skill teach-jnyross
Please help me install this Agent Skill. Skill: teach Source: https://github.com/jnyross/pstack-muse/tree/main/skills/teach Command: npx skills add https://github.com/jnyross/pstack-muse --skill teach-jnyross
how and why skills in parallel to gather how the code works and the reasoning behind it, then weaves the findings into one account. - Audience-aware depth: Picks the few things you should walk away understanding based on why you are asking, and goes deeper only when you ask. - Progressive visuals: Builds understanding with a series of small diagrams that each add one part, using mermaid for flows and generated whiteboard-style images for spatial ideas. - Use Case: You are about to modify a virtualization module you have never touched. Ask for an explanation and get a plain account of its rendering and loading halves, how eviction works as items scroll, and the design reasons behind it. ## Quick Start Ask the assistant to teach you how a specific subsystem or recent change works and why it is built that way.High-intent search queries and answers about installing and using this skill.
Ask to be taught how the subsystem works. The skill runs the how and why skills to investigate the code and its design rationale, then combines the findings into one plain explanation matched to what you already know.
It explains the concrete mechanism and the reasons behind design decisions rather than listing functions and constants. It leads with the smallest complete answer and adds depth only when you ask for more.
Yes. The skill matches its investigation size to the question, running both how and why for a subsystem but often only one for a small change, keeping the why pass narrowly scoped by default.
Yes, when a picture lands faster than words. Flows and structures use mermaid diagrams, spatial ideas use generated whiteboard-style images, and complex systems are drawn as a series of small diagrams that each add one part.
Skip it when you only need a quick fact or a reference lookup, since the skill is built for understanding rather than changing code. It deliberately avoids quizzes, lectures, and walls of text.
mmdmcyExplains code and subsystems by combining how and why skill investigations into plain-language teaching.
cursorExplains code and subsystems plainly by combining how and why skill investigations.
Sma1lboyExplains how code works and why it is built that way in plain language.
sd0xdevAnswers codebase questions with intent classification and source-attributed context gathering.