/teach adds npx install and primary-source lessons

• the launch post says /teach is live now, installs with npx skills add mattpocock/skills --skill teach, and is framed as a general-purpose teaching skill, not just an engineering helper.
• In the step-by-step setup post, the recommended workflow is unusually concrete: make a fresh directory, start Claude there, and hand /teach a long prompt about becoming a more strategic programmer.
• the follow-up update says every lesson now recommends primary-source reading, which lines up with the skill docs' broader emphasis on resource gathering and self-guided study in the teach SKILL.md.
• According to a later repo note, /teach may move into its own repository, with plans for 100 example prompts plus longer docs on the teaching principles behind it.

You can read the launch walkthrough, inspect the current skill spec, and compare that with the strategic-programmer prompt thread. The interesting bit is that /teach is being pitched less like a one-shot explainer and more like a stateful workspace, with mission files, glossaries, and progress tracking baked into the skill definition.

The install story is now simple: the repo-level skills quickstart still points people at npx skills@latest add mattpocock/skills, while the focused /teach post adds the narrower per-skill command, npx skills add mattpocock/skills --skill teach.

That same post also shows the intended usage pattern. Instead of asking for a generic lesson, the example prompt tells the agent exactly what kind of capability shift it should optimize for: moving from day-to-day coding toward planning, QA, and codebase design.

The underlying teach SKILL.md describes /teach as a stateful workspace, not a chat macro. It stores a MISSION.md for the learner's goal, a GLOSSARY.md for terms, and other workspace files so later sessions can pick up where earlier lessons stopped.

The matching AI Hero walkthrough says the skill should capture the mission, gather resources, generate interactive lessons with audio and quizzes, and keep a learning record. That is a more ambitious structure than the launch tweets alone suggest.

One day after the launch thread, the update post said every /teach lesson now recommends primary-source reading. That shifts the skill a little away from being a closed teaching loop and a little toward acting like a guide into original material.

The same update also ties into a broader workflow change. In the attached thread context, mattpocockuk says the pre-PRD phase of AI-assisted work needs more structure, which helps explain why /teach is being tightened around source-first learning instead of pure agent exposition.

The last new wrinkle is packaging. the repo plan post says /teach may leave the main skills repo and get its own home, with two concrete additions already named: 100 example prompts and guides on the principles behind the skill.

If that happens, /teach stops looking like a side utility inside a larger engineering toolkit and starts looking like a standalone teaching product with its own prompt library and docs surface.