Slides: every skill has SKILL.md → live demo → what a skill can carry → check before you trust.

For a room that has already made skills elsewhere (a Cowork course, say). Don't explain what a skill is.

Where skills live (1.5 min): use the yellow Part 1 · Skills & automations label as the visual transition from the three-concept overview, then say: "You've made skills before. In Claude Code, every skill has a SKILL.md instruction file that you can open. A global skill works in every project; a project skill works only here." Presenter: open ~/.claude/skills/ as the global skills folder, then a project's .claude/skills/. Learners do not need to name either path: ask, "Who saved a skill during the pre-work?" One question decides the place: every project, or only this one?
Demo (4 min): in the restock-planner, paste the prompt from the slide. It asks for a global skill, not a path. Expected: Claude creates ~/.claude/skills/project-status/ with SKILL.md inside and shows the file. Open it: the description at the top is what Claude reads to know when the skill applies; the steps follow. Type / in the Claude panel: the skill is listed. Then run it immediately. The useful payoff is a plain-language snapshot: what this project is for, what changed recently, the next action and any blockers.
What a skill can carry (2 min): show the two folder shapes. SKILL.md is always the instruction file; a small skill can stop there. Add images, templates or references when Claude needs reusable material for the job. Add a Python or other code script when a repeated step must be exact and reliable. Ask the room which supporting file would help one of their skills.
Check before you trust (1.5 min): a new skill is like a new colleague's first report: check one result against something you know is right before you rely on the rest. It can be a number: a stock figure, date or total. Or it can be a non-numeric check: an approved template, source file or expected action. The result matches: use the skill. It does not: fix the skill, then run the same check again.

Expected: project-status appears when you type /; when run, it names the project’s purpose, recent work, next action and blockers. If it doesn't appear, close VS Code completely and reopen it.

Fallback: it still doesn't appear → show the file anyway, then ask: "Use the project-status skill."