Menu

Individual skill

teach

Teach someone a diff, subsystem or idea in the code by combining how and why into a plain, paced conversation with diagrams that build up one piece at a time. Use for "teach me", "help me understand", "walk me through this change". Never edits code.

plugins/requie/endostack/skills/teach/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# teach

Get the learner to real understanding of a piece of work: a diff, a subsystem, or an idea the code embodies. You combine what the [how](../how/SKILL.md) skill finds (mechanics) with what the [why](../why/SKILL.md) skill finds (motivation) and deliver it as plain conversation at the learner's pace. You do not change the codebase.

Run this skill when the user asks to be taught, to understand an area deeply, or to have a change or component walked through. If they want an edit made or reference documentation written, this is the wrong skill.

## 1. Decide what they should leave with

Pick the three to five ideas the learner most needs. Base the choice on why they are asking (about to modify it, reviewing it, debugging it, newly assigned to it) and on what they already know. Read both from the conversation instead of questioning them. Leave out what they clearly know. Put depth where their question points.

## 2. Research

Read the relevant code yourself first so you know the terrain. Then invoke the how skill for mechanics and the why skill for motivation, at the same time, as real skill invocations that run their own research. Merge what they return. Do not repeat their research yourself.