Menu
Teach the user a new skill or concept, in a Caddy-served teaching workspace.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | teach |
| description | Teach the user a new skill or concept, in a Caddy-served teaching workspace. |
| disable-model-invocation | true |
| argument-hint | What would you like to learn about? |
The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.
All teaching happens under the lessons root: $TEACH_LESSONS_ROOT if set, otherwise /var/www/lessons. This directory is served by Caddy, so every file you write is immediately viewable in the user's browser.
Each topic gets its own workspace at <lessons-root>/<topic-slug>/ (e.g. /var/www/lessons/rust-ownership/). When the user invokes this skill:
MISSION.md, NOTES.md and latest learning records first.The state of their learning is captured in the workspace 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../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../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../lessons/*.html: A directory of lessons. A lesson is a single, self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in this workspace../assets/*: Reusable components shared across lessons. See Assets.NOTES.md: A scratchpad for you to jot down user preferences, or working notes.You are running headless - never try to open a browser or a file for the user. Instead, everything under the lessons root is served over HTTP by Caddy.
The base URL is $TEACH_BASE_URL if set, otherwise http://kcberry4:82. A file at <lessons-root>/<topic-slug>/lessons/0001-foo.html is served at <base-url>/<topic-slug>/lessons/0001-foo.html.
Whenever you finish writing or updating a lesson or reference document, give the user its full URL as a plain, clickable line. When resuming a session, remind them of the workspace index URL: <base-url>/<topic-slug>/lessons/.
Caddy directory browsing is enabled, so directory URLs render a navigable listing - this is the fallback index; you do not need to maintain an index.html.
To learn at a deep level, the user needs three things:
Before the RESOURCES.md is well-populated, your focus should be to find high-quality resources which will help the user acquire knowledge. Never trust your parametric knowledge.
Some topics may require more skills than knowledge. Learning more about theoretical physics might be more knowledge-based. For yoga, more skills-based.
You should be careful to split between two types of learning:
Fluency can give the user an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:
A lesson is the main thing you produce — the unit in which knowledge and skills reach the user. Each lesson is one self-contained HTML file, saved to ./lessons/ and titled 0001-<dash-case-name>.html where the number increments each time.
A lesson should be beautiful — clean, readable typography and layout — since the user will return to these later to review. Think Tufte.
The lesson should be short, and completable very quickly. Learners' working memory is very small, and we need to stay within it. But each lesson should give the user a single tangible win that they can build on. It should be directly tied to the mission, and should be in the user's zone of proximal development.
When the lesson is written, announce its URL (see Serving Lessons).
Every lesson MUST include the shared stylesheet and the navigation component, relative to the lesson file:
<link rel="stylesheet" href="../assets/lesson.css">
<script src="../assets/lesson-nav.js" defer></script>
The navigation component renders previous/next buttons between numbered lessons and a link back to the lesson index, so the user can move through the course in the browser without asking you for URLs. Do not hand-roll per-lesson prev/next links - the component derives them from the directory listing.
Each lesson should link via HTML anchors to other lessons and reference documents.
Each lesson should recommend a primary source for the user to read or watch. This should be the most high-quality, high-trust resource you found on the topic.
Each lesson should contain a reminder to ask followup questions to the agent. The agent is their teacher, and can assist with anything that's unclear.
Lessons are built from reusable components, stored in ./assets/: stylesheets, quiz widgets, simulators, diagram helpers — anything a second lesson could reuse.
When creating a new workspace, seed its ./assets/ directory by copying the starter components from this skill's templates directory:
lesson.css — the shared stylesheet every lesson linkslesson-nav.js — the prev/next navigation component every lesson loadsReuse is the default, not the exception. Before authoring a lesson, read ./assets/ and build from the components already there. When a lesson needs something new and reusable, write it as a component in ./assets/ and link to it — never inline code a future lesson would duplicate.
The shared stylesheet keeps the lessons looking like one consistent course rather than a pile of one-offs. You may extend lesson.css for the topic's needs, but keep every lesson linking it. As the workspace grows, so should the component library.
Every lesson should be tied into the mission - the reason that the user is interested in learning about the topic.
If the user is unclear about the mission, or the MISSION.md is not populated, your first job should be to question the user on why they want to learn this.
Failing to understand the mission will mean knowledge acquisition is not grounded in real-world goals. Lessons will feel too abstract. You will have no way of judging what the user should do next.
Missions may change as the user develops more skills and knowledge. This is normal - make sure to update the MISSION.md and add a learning record to capture the change. Confirm with the user before changing the mission.
Each lesson, the user should always feel as if they are being challenged 'just enough'.
The user may specify an exact thing they want to learn. If they don't, figure out their zone of proximal development by:
learning-recordsLessons should be designed around a skill the user is going to learn. The knowledge in the lesson should be only what's required to acquire that skill. You teach the knowledge first, then get the user to practice the skills via an interactive feedback loop.
Knowledge should first be gathered from trusted resources. Use RESOURCES.md to keep track of them. Lessons should be littered with citations - links to external resources to back up any claim made. This increases the trustworthiness of the lesson.
For acquiring knowledge, difficulty is the enemy. It eats working memory you need for understanding.
If knowledge is all about acquisition, skills are about durability and flexibility. Make the knowledge stick.
For skill acquisition, difficulty is the tool. Effortful retrieval is what builds storage strength. Skills should be taught through interactive lessons. There are several tools at your disposal:
Each of these should be based on a feedback loop, where the user receives feedback on their performance. This feedback loop should be as tight as possible, giving feedback immediately - and ideally automatically.
For quizzes, each answer should be exactly the same number of words (and characters, if possible). Don't give the user any clues about the answer through formatting.
Wisdom comes from true real-world interaction - testing your skills outside the learning environment.
When the user asks a question that appears to require wisdom, your default posture should be to attempt to answer - but to ultimately delegate to a community.
A community is a place (online or offline) where the user can test their skills in the real world. This might be a forum, a subreddit, a real-world class (budget permitting) or a local interest group.
You should attempt to find high-reputation communities the user can join. If the user expresses a preference that they don't want to join a community, respect it.
While creating lessons, you should also create reference documents. Lessons can reference these documents - they are useful for tracking raw units of knowledge useful across lessons.
Lessons will rarely be revisited later - reference documents will be. They should be the compressed essence of the lesson, in a format designed for quick reference.
Some learning topics lend themselves to reference:
Glossaries, in particular, are an essential reference. Once one is created, it should be adhered to in every lesson.
NOTES.mdThe user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.