Skills

Workshop Style

Hands-on workshop, the learner works through the course instead of watching it, with...

Install

npx skills add THU-MAIC/OpenMAIC --skill workshop-style -g -a claude-code -y
Repository
THU-MAIC/OpenMAIC42.4k
Category
Documents
Updated
3d ago
License
MIT
Context cost
Lightabout 1,370 tokens
Runs scripts
No, instructions only

What it does

Hands-on workshop, the learner works through the course instead of watching it, with an exercise or a check every couple of pages, short slides that only set up the next task, guiding narration that asks more than it tells, and a closing page where the pieces come together in one small project. Use when the ask is a workshop, a bootcamp session, 「动手」「实操」「练中学」「边做边学」, or a skill the learner is meant to leave holding; also use when the user names this style. Not for a systematic explanatory course (that is `lecture-style`) and not for occupational procedure training with tools and safety gates (that is `vocational`).

Workshop design

You are designing a workshop. Nothing is explained for longer than it takes to set up the next thing the learner does, and every idea is followed immediately by a page where they try it. The learner leaves having built something, not having been told about it.

stage-design still governs how the stage is built, outline, roster, one page per generate_scene, audio before done. This skill governs what the stage contains and how it sounds.

The shape

  • Scene 1 is a slide, and it is short: what the learner will have made by the end, and the first thing they are about to try. No agenda, no history of the field.
  • Every concept is followed at once by a hands-on page. The rhythm is concept → do it, concept → do it: roughly one interactive or quiz page for every two pages in the course. If two explanatory pages ever sit next to each other, one of them is unnecessary.
  • interactive pages are the exercises. Each isolates one thing to build, vary or trace. Consecutive interactive pages must not reuse the same widgetType, as the learner moves from trying to predicting to applying, the modality moves with them.
  • quiz pages are quick self-checks, not exams, placed right after a hands-on page to make the learner state what they just observed. Short, two or three questions.
  • The last page is a small integrating project: one interactive page whose task needs several of the workshop's pieces at once, with the earlier exercises as its parts. Not a summary slide. This is the page the learner screenshots afterwards.

Slides are task briefs

A slide in a workshop exists to make the next exercise possible. Keep it to two or three keyPoints, the rule, the shape, the one gotcha, and put everything else in the exercise. A workshop slide that could be read on its own as a lesson is too long: cut it and let the interactive page teach.

widgetOutline

Read the whole SKILL.md on GitHub

More in Documents