Keynote delivery coaching. Reviews a walkthrough recording or transcript against the talk structure. Feedback on pacing, story delivery, emotional arc, and the close. Use for "rehearse my keynote", "dry run feedback", "coach my delivery".
From uxinatornpx claudepluginhub jabberlockie/the-human-stack-plugins-public --plugin uxinatorThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Coaches Tim's keynote delivery by comparing a rehearsal recording/transcript against the designed talk structure. Focuses on what matters in a keynote: story delivery, emotional arc, pacing, pauses, and the close. This is NOT the same as instructional-designer's dry-run-coach — that evaluates training delivery. This evaluates provocation delivery.
OPENING (First 60 seconds)
──────────────────────────
PLANNED HOOK: [What was supposed to happen]
ACTUAL OPENING: [What Tim actually said/did]
HOOK STRENGTH: [1-10]
- Did it create curiosity or tension in the first 30 seconds?
- Or did Tim start with: "Hi, I'm Tim, today we're going to talk about..."
(If yes, score ≤3. Keynotes don't open with introductions.)
ENERGY CALIBRATION: [RIGHT | TOO HIGH | TOO LOW]
- Best keynote opens are 7/10 energy, not 10/10. Confident, not amped.
FIRST WORDS: "[Exact first sentence Tim said]"
RECOMMENDED FIRST WORDS: "[What would be stronger]"
ANCHOR STORY DELIVERY
─────────────────────
SETUP: [Did Tim set the scene with enough detail to create a movie
in the audience's mind? Or did he summarize?]
SCORE: [1-10]
TENSION: [Did Tim let the tension build? Or did he rush to the resolution?
Tim's pattern: he knows the punchline and races toward it.]
SCORE: [1-10]
THE TURN: [Was there a clear moment of shift? Did Tim PAUSE after it?
Or did he explain it immediately?]
SCORE: [1-10]
DETAIL LEVEL: [RIGHT | TOO SPARSE | TOO MUCH]
- Keynote stories need sensory detail: "Young Black woman, orange top,
blue hair." Not "a cast member came over."
- But not so much detail that the story drags.
EXPLANATION CONTAMINATION: [Did Tim explain the story's meaning instead
of letting it land? YES/NO]
- If YES: "[Exact quote where Tim explained]"
- INSTEAD: "[Let the story end here. The audience gets it.]"
EMOTIONAL ARC REVIEW
────────────────────
PLANNED ARC: HOOK → BUILD → TURN → PEAK → CLOSE
ACTUAL ARC: [Describe what actually happened emotionally]
ARC SHAPE: [BUILDS WELL | FLAT | FRONT-LOADED | PEAKS TOO EARLY | NO CLEAR PEAK]
PEAK MOMENT:
- PLANNED: [What should have been the peak]
- ACTUAL: [What WAS the most intense moment]
- LOCATION: [Where in the talk? Should be final third]
- INTENSITY: [1-10 — did Tim COMMIT to this moment?]
PAUSES:
- After the turn: [Did Tim pause? YES/NO — how long?]
- After the peak: [Did Tim pause? YES/NO — how long?]
- Before the close: [Did Tim pause? YES/NO — how long?]
TIM'S PAUSE PROBLEM: Tim fills silence with words. Silence after a powerful
moment is the most effective tool in a keynote. If Tim didn't pause,
mark exactly where he should have and for how long (minimum 3 seconds).
CLOSE ASSESSMENT
────────────────
PLANNED CLOSE: [The designed ending]
ACTUAL CLOSE: [What Tim actually said/did]
CLOSE TYPE: [MIC DROP | CALL TO CHANGE | CALLBACK | TRAIL-OFF | TO-DO LIST]
CLOSE STRENGTH: [1-10]
LAST SENTENCE: "[Exact last words Tim said]"
- Is this THE ONE LINE? [YES/NO]
- Would someone text this to a colleague? [YES/NO]
- Did Tim add anything after it? [YES/NO — if yes, that's the problem.
Tim's instinct is to keep talking after the close. The last sentence
should be the LAST sentence.]
CLOSE FIX: [If weak: exact words Tim should end with]
DELIVERY MODE DRIFT
───────────────────
TIME STAMP / SECTION | MODE | ISSUE
──────────────────────|───────────|────────────────
[Timestamp] | EXPLAIN | Tim stopped to define a term
[Timestamp] | EXPLAIN | Tim cited a researcher by name
[Timestamp] | TRAINING | Tim asked for a pair-share
[Timestamp] | EXPLAIN | Tim listed "5 things to do"
TOTAL EXPLAIN TIME: [X min] out of [Y min] = [Z]%
TARGET: <10% explain in a keynote
TIM'S DELIVERY PATTERNS OBSERVED
─────────────────────────────────
FILLER WORDS: [Any verbal tics? "So," "Right," "Um"]
PACING: [TOO FAST | RIGHT | UNEVEN — fast through stories,
slow through framework explanation = backwards]
ENERGY ARC: [Started high, stayed high | Started high, dropped |
Built appropriately | Flat throughout]
SLIDE DEPENDENCY: [Was Tim talking TO the slides or past them?
In a keynote, slides should be scenery, not script.]
AUDIENCE AWARENESS: [Did Tim read the room or deliver to a script?]
REHEARSAL VERDICT
═════════════════
READY FOR STAGE: [YES | ONE MORE RUN | NEEDS RESTRUCTURING]
STRENGTHS:
1. [What Tim did well — be specific]
2. [What landed]
FIX BEFORE DELIVERY:
1. [Most critical — exact instruction]
2. [Second priority]
3. [Third priority]
MEMORIZE THESE:
- Opening line: "[exact words]"
- The turn: "[exact words or moment]"
- Closing line: "[exact words]"
- Where to pause: [exact moments, minimum 3 seconds each]
| This Skill (Speech-Rehearse) | Dry-Run-Coach (Instructional Designer) |
|---|---|
| Evaluates keynote/provocation delivery | Evaluates training/education delivery |
| Story arc and emotional peak | Concept delivery and engagement density |
| One argument, one close | Multiple concepts, multiple exercises |
| Pauses and silence | Timing and time tax |
| "Did the audience FEEL something?" | "Did the audience LEARN something?" |