Stats
Actions
Tags
From example-skills
Designs engaging workshops, conference talks, and educational presentations using structured arcs, learning objectives, slide principles, activity design, and facilitation techniques. Useful for talk structure or training prep.
How this skill is triggered — by the user, by Claude, or both
Slash command
/example-skills:workshop-presentation-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Teach effectively through structured experiences.
Teach effectively through structured experiences.
| Format | Duration | Audience Size | Interaction |
|---|---|---|---|
| Lightning talk | 5-10 min | Any | Low |
| Conference talk | 20-45 min | Large | Low-Medium |
| Workshop | 1-4 hours | 10-30 | High |
| Tutorial | 2-8 hours | 5-20 | Very High |
| Course | Multi-day | Varies | Structured |
Hook → Context → Core Content → Transformation → Call to Action
│ │ │ │ │
└────────┴───────────┴──────────────┴──────────────┘
One Clear Idea
0-5% HOOK
- Surprising fact, question, or story
- Why should they care?
5-15% CONTEXT
- Background needed to understand
- Where this fits in larger picture
15-85% CORE CONTENT
- 3-5 key points (rule of three)
- Examples and evidence for each
- Build logically
85-95% TRANSFORMATION
- What changes with this knowledge?
- The "so what?"
95-100% CALL TO ACTION
- What should they do next?
- Memorable closing
People remember three things. Structure around:
Principles:
Avoid:
Write objectives using Bloom's Taxonomy verbs:
| Level | Verbs | Example |
|---|---|---|
| Remember | List, define, recall | "List the 5 principles of..." |
| Understand | Explain, describe, summarize | "Explain how X affects Y" |
| Apply | Use, implement, solve | "Apply the framework to..." |
| Analyze | Compare, contrast, examine | "Analyze the trade-offs..." |
| Evaluate | Judge, critique, assess | "Evaluate which approach..." |
| Create | Design, build, produce | "Create a working prototype..." |
OPEN (10-15%)
├── Welcome, housekeeping
├── Learning objectives
├── Icebreaker/activation
└── Baseline assessment
EXPLORE (30-40%)
├── Core concept introduction
├── Demonstration
├── Guided practice
└── Check for understanding
PRACTICE (30-40%)
├── Independent/group work
├── Real-world application
├── Troubleshooting
└── Peer feedback
CLOSE (10-15%)
├── Debrief and discussion
├── Key takeaways
├── Resources for continued learning
└── Feedback collection
| Activity Type | Attention Span | Max Duration |
|---|---|---|
| Lecture | Low | 10-15 min |
| Discussion | Medium | 15-20 min |
| Hands-on | High | 30-45 min |
| Group work | Medium-High | 20-30 min |
Rule: Change modality every 15-20 minutes.
| Activity | Purpose | Group Size |
|---|---|---|
| Think-Pair-Share | Low-risk participation | 2 |
| Gallery Walk | Share work, get feedback | 4-6 stations |
| Jigsaw | Divide & teach | 4-6 per group |
| Fishbowl | Model discussion | Inner: 4-6 |
| Live Coding | Demonstrate process | Any |
| Code Review | Practice critique | 2-4 |
Cold calling alternatives:
Energy management:
| Situation | Response |
|---|---|
| Off-topic | "Great question—let's parking lot that" |
| Too advanced | "Let's connect after for that deep dive" |
| You don't know | "I don't know, but I'll find out" |
| Dominating questioner | "Let's hear from someone else" |
Types:
Quick feedback form:
1. What was most valuable?
2. What was least valuable?
3. What questions remain?
4. Net Promoter Score (1-10)
5-Minute Talk Structure:
0:00 - 0:30 HOOK
Surprising statement or question
0:30 - 1:00 CONTEXT
Why this matters
1:00 - 3:30 THE ONE THING
Your main point with evidence/example
3:30 - 4:30 IMPLICATIONS
What changes because of this
4:30 - 5:00 CALL TO ACTION
What they should do next
references/activity-library.md - Workshop activities catalogreferences/slide-templates.md - Slide design patternsreferences/facilitation-scripts.md - Opening/closing scriptsnpx claudepluginhub a-organvm/a-i--skills --plugin document-skillsProvides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.