Public speaking techniques for developer conferences, meetups, and presentations
Generates complete talk preparation packages for developer presentations. Creates structured outlines, slide counts, and speaker notes when you specify talk type, topic, and audience details.
/plugin marketplace add pluginagentmarketplace/custom-plugin-devrel-engineer/plugin install devrel-engineer-plugin@pluginagentmarketplace-devrel-engineerThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/talk-template.yamlreferences/SPEAKING_GUIDE.mdscripts/talk_planner.pyMaster public speaking for developer conferences, meetups, and technical presentations.
parameters:
required:
- talk_type: enum[lightning, standard, keynote, workshop]
- topic: string
optional:
- duration_minutes: integer
- audience_level: enum[beginner, intermediate, advanced]
- demo_included: boolean
output:
talk_prep:
outline: markdown
slide_count: integer
speaker_notes: array[string]
delivery:
hook: string
key_messages: array[string]
closing_cta: string
First 30 seconds determine if audience stays engaged:
- Start with a problem statement
- Ask a provocative question
- Share a surprising statistic
- Tell a brief story
Setup → Conflict → Resolution → Takeaway
Example:
"We had 10,000 API errors per day..."
"We tried caching, it made it worse..."
"Then we discovered rate limiting patterns..."
"Here's how you can implement it too..."
| Technique | Description | Best For |
|---|---|---|
| PechaKucha | 20 slides, 20 seconds each | Quick overviews |
| Problem-Solution | Pain → Fix → Proof | Technical tutorials |
| Demo-First | Show working, then explain | Product showcases |
| Repetition | Key phrases for emphasis | Key concepts |
| Type | Duration | Slides | Prep Time |
|---|---|---|---|
| Lightning | 5 min | 5-10 | 2-4 hours |
| Standard | 20-30 min | 20-40 | 1-2 weeks |
| Keynote | 45-60 min | 40-60 | 3-4 weeks |
| Workshop | 2-4 hours | 30-50 | 4-6 weeks |
retry_patterns:
tech_failure:
strategy: "Switch to backup slides/demo"
fallback: "Continue without demo, describe visually"
lost_place:
strategy: "Pause, check notes, summarize so far"
recovery: "As I was saying... [pick up thread]"
audience_disengaged:
strategy: "Ask question, add interactive element"
| Failure Mode | Detection | Recovery |
|---|---|---|
| Slides won't load | Black screen | Use backup USB/PDF |
| Demo crashes | Error message | Pre-recorded backup |
| Running over time | 5 min warning | Skip to conclusion |
| Mic issues | No audio | Project louder |
□ Talk outline reviewed?
□ Slides tested on actual display?
□ Demo rehearsed 3+ times?
□ Backup slides on USB?
□ Speaker notes ready?
□ Water at podium?
□ Mic tested?
□ Timing practiced?
test_public_speaking:
unit_tests:
- test_timing:
input: "Full rehearsal"
assert: "Within ±2 min of target"
- test_key_messages:
input: "3 takeaways"
assert: "Audience can recall"
integration_tests:
- test_full_delivery:
scenario: "Complete run-through"
assert: "Smooth flow, on time"
metrics:
- audience_size: integer
- talk_rating: float
- on_time_finish: boolean
- demo_success: boolean
See assets/ for talk templates and references/ for presentation guides.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.