Explains code and subsystems by combining how and why skill investigations into plain-language teaching.
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill teach-mmdmcy
Please help me install this Agent Skill. Skill: teach Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/teach Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill teach-mmdmcy
how and why skills in parallel to gather mechanism and rationale, then weaves the findings into one coherent explanation. - Audience-Calibrated Depth: Chooses what to teach based on why the person is asking (about to change it, reviewing it, debugging it, new to it) and what they already know. - Progressive Visual Teaching: Builds understanding through a series of small diagrams that each add one part, using mermaid for flows and generated whiteboard-style images for spatial ideas. - Use Case: A developer joining a team asks "teach me how the virtualization layer works" and receives a plain spoken explanation of what it is, how it renders and evicts items, and why it was designed that way, with diagrams that build up step by step. ## Quick Start Ask the assistant to use the teach skill to explain how a specific subsystem or recent change in your repository works and why it is built that way.High-intent search queries and answers about installing and using this skill.
Ask for an explanation of the specific subsystem or change, and the teach skill runs the how and why skills to investigate the code, then blends the findings into one plain account. It leads with the main point and adds depth only when you ask.
The how skill explains how something works and the why skill explains why it was built that way. Teach sits on top of both, invoking them as real skill runs and weaving their findings into a single teaching-oriented explanation.
Yes. For anything with three or more moving parts, it draws a series of small diagrams where each one adds a single part. It uses mermaid for flows and structure, and generated whiteboard-style images for spatial ideas like layout or scroll position.
No. The goal is understanding, not changing anything. It reads code to get oriented and delegates investigation to the how and why skills, then delivers only an explanation.
Use it when you need to understand both the mechanism and the rationale behind a change or subsystem, such as before modifying unfamiliar code, reviewing a large diff, or onboarding to a new area of the repository.
yiminllinAnalyze a git commit diff and generate a structured review.
cursorExplains code and subsystems plainly by combining how and why skill investigations.
awood45Finds sourced, concise answers to focused factual questions using web search and fetch.
videojsWrites compact Video.js architecture and decision records with non-inferable rationale.