com um clique
shsk_lesson_smith-project
shsk_lesson_smith-project contém 7 skills coletadas de MacHu-GWU, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Foundation skill for authoring teaching repositories (hands-on IT learning courses). Defines the shared concept model, language/format conventions, and document templates that the whole lesson-smith-* skill family builds on. Load when creating or updating any course material — README.md, README-cn.md, TICKET.md, CLAUDE.md, TEACHING.md, Syllabus.md, about.md.
给一个 upskill 教学仓库收尾定型. 重写 README-ORIGINAL (Lesson 门面), 写出根目录的 README 与 TICKET (仓库总览加整门课验收清单, 一次产出全部语种), 再跑 lesson-smith sync 生成 SYLLABUS 与快照, 最后跑 lesson-smith lint 把关. 创作流的最后一步, examples 与 forge 都做完之后用. 关键词, finalize upskill, 重写 README-ORIGINAL, 写根 README TICKET, 生成 SYLLABUS, upskill 收尾.
On-call learning mentor for this upskill course. Walks you through the examples progression, unpacks any specific file or spot you are stuck on, and helps you decide what to learn next. Auto-loads when you mention or open any file under examples/, or say things like "walk me through this course", "explain this example", "I'm stuck here", "what should I learn next". Also invocable directly.
Interview-style quiz that checks whether you have truly internalized this upskill course (know-what and know-why). Auto-loads when you say "quiz me", "test my knowledge", "let's drill", when you mention the quiz, or when you mention the quiz mini task file under examples/. Also invocable directly.
带教程创作者从零创作一个符合 upskill 规范的 repo, 主要是 examples 下那一整套课程内容. 讨论规划, 试水前几篇锁风格, 迭代往后写, 收尾写 quiz 与梳理, 批量翻译, 最后交给 forge. 创作或续写 upskill 课程时用. 关键词, 写 upskill 课程, 创作 examples, 规划这门课.
为当前这个 upskill 教学仓库锻造出 "学这门课" 的工具链. 扫一遍 examples 渐进序列, 向创作者问清学习素材与考法, 写出 docs/upskill/ 下的 3 份文档 (learn, runbook, quiz), 并落下 upskill-learn 与 upskill-quiz 两个子 skill. 接手或刷新一个 upskill repo 的学习工具时用. 关键词, forge upskill, 生成 upskill 学习 skill, 刷新 upskill 文档.
How Agent Skills and Subagents differ and how to combine them — the skill-as-caller / subagent-as-doer best practice. Use when deciding whether a task should be a skill or a subagent, or when authoring a skill and subagent that work together (e.g. a /name skill that delegates to an isolated subagent).