원클릭으로
public-speaking
Public speaking techniques for developer conferences, meetups, and presentations
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Public speaking techniques for developer conferences, meetups, and presentations
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Developer relations career development, growth paths, and professional advancement
Effective communication strategies for developer audiences across channels
Building and nurturing thriving developer communities
Creating compelling technical content for developer audiences
Planning and executing developer events, conferences, and meetups
Measuring and demonstrating DevRel impact through data and analytics
| name | public-speaking |
| description | Public speaking techniques for developer conferences, meetups, and presentations |
| sasmp_version | 1.4.0 |
| version | 2.0.0 |
| updated | 2025-01 |
| bonded_agent | 06-developer-advocate |
| bond_type | PRIMARY_BOND |
Master 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.