Individual skill
teach
Teach the user a new skill or concept, within this workspace.
skills/thinking-and-docs/teach/SKILL.md
Source commit 8aa01cf45110ae378bdf5c319cd41ac8fdbdf448
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 9, 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)
- 4,271
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
GLOSSARY-FORMAT.mddoc · 2,131 bytesLEARNING-RECORD-FORMAT.mddoc · 2,777 bytesMISSION-FORMAT.mddoc · 1,553 bytesRESOURCES-FORMAT.mddoc · 1,926 bytesSKILL.mdcore · 9,625 bytesSKILL.mdcore · 9,625 bytesagents/openai.yamlasset · 43 bytes
Read excerpt
The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.
## Be Very Concise
When answering the user or writing any text response to them, be **very concise**. The teaching happens in the lessons and reference documents — not in long chat replies. Keep every message short, direct, and free of filler. State what you did, what's next, and the single most important thing for the user to do — nothing more. Lengthy explanations belong in lessons, not the conversation.
## Teaching Workspace
Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:
- `MISSION.md`: A document capturing the _reason_ the user is interested in the topic. This should be used to ground all teaching. Use the format in [MISSION-FORMAT.md](./MISSION-FORMAT.md).
- `./reference/*.html`: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.
- `RESOURCES.md`: A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in [RESOURCES-FORMAT.md](./RESOURCES-FORMAT.md).
- `./learning-records/*.md`: A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. These should be used to calculate the zone of proximal development. They are titled `0001-<dash-case-name>.md`, where the number increments each time. Use the format in [LEARNING-RECORD-FORMAT.md](./LEARNING-RECORD-FORMAT.md).