Prepare a talk from scratch: audience analysis, time boxing per section, outline structure, speaker notes, rehearsal strategy, Q&A preparation, and nervous system management. Use for conference talks, team presentations, demos, and webinars of any length.
From clarcnpx claudepluginhub marvinrichter/clarc --plugin clarcThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Before writing a single slide, answer these four questions:
Write the answer to question 4 in one sentence — this becomes the talk's thesis.
| Talk type | Pace | Buffer |
|---|---|---|
| Technical / code-heavy | 1 slide per 2 min | +10% |
| Keynote / story-driven | 1 slide per 3 min | +10% |
| Workshop / interactive | 1 slide per 5 min | +15% |
Live runs 15% slower than rehearsal. Budget for it.
For a 30-minute talk:
Opening hook: 2 min (no agenda slide)
Context / setup: 4 min
Main point 1: 7 min
Main point 2: 7 min
Main point 3: 5 min
Conclusion + CTA: 3 min
Buffer: 2 min
─────────────────────────────
Total: 30 min
Adjust ratio to content — demo-heavy talks may spend 60% on one section.
Slide count ≈ Talk duration (min) / Pace (min per slide)
Example: 30 min technical talk = 30 / 2 = 15 slides
A talk outline has five components:
Talk: [Title]
Audience: [Role, level]
Duration: [X] minutes
Thesis: [One sentence — what the audience will think differently after]
Opening (X min)
Hook: [Specific question, stat, or story — write it out in full]
Why this matters to them: [explicit audience relevance]
Section 1: [Name] (X min)
Key point: [One sentence]
Supporting evidence: [Data, example, demo]
Transition to next: [Exact bridging sentence]
Section 2: [Name] (X min)
[same structure]
Section 3: [Name] (X min)
[same structure]
Closing (X min)
Takeaway 1: [Most important insight]
Takeaway 2: [Second insight]
Takeaway 3: [Third insight]
CTA: [One specific action]
Q&A Prep
[See below]
Speaker notes exist to prevent going blank — not to be read aloud.
WRONG — prose that gets read verbatim:
"In this section I will explain how the system works by walking you
through the architecture diagram and then I will show you the key
components including the API gateway and the message queue."
CORRECT — keywords + timing markers:
[2 min] → gateway → queue → show diagram
→ "this is the part that surprised us" [pause for effect]
→ demo: open terminal, run `make demo` → wait for output
→ transition: "so how does this affect you?"
[1:30] at points where you need to be at that time[pause] or [breath] after key pointsThree rehearsal passes, in order:
After Pass 1: if you ran >10% over, cut content. If >20% under, add depth or slow down — rushing is a sign of nerves.
Generate 10 questions before the talk — you will get most of them.
Pattern: Acknowledge → Reframe → Redirect
"That's a fair concern. [Acknowledge the validity of the pushback.]
In our context, [explain your specific constraint or assumption].
We've found [your evidence]. Happy to discuss more after the talk."
It is better to say "I don't know — I'll find out and post on the conference Slack" than to guess and be wrong publicly. Prepare this exact phrase.