CtrlK
BlogDocsLog inGet started
Tessl Logo

jbaruch/speaker-toolkit

Six-skill presentation system: ingest talks into a rhetoric vault, run interactive clarification, generate a speaker profile, create presentations that match your documented patterns, produce the deck illustrations + thumbnail visual layer, and publish talk pages to a Jekyll shownotes site. Includes a 111-entry Presentation Patterns taxonomy (81 observable: 62 patterns + 19 antipatterns; 30 unobservable: 21 patterns + 9 antipatterns) for scoring, brainstorming, and go-live preparation.

Quality

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

carnegie-hall.mdskills/presentation-creator/references/patterns/deliver/

id:
carnegie-hall
name:
Carnegie Hall
type:
pattern
part:
deliver
phase_relevance:
publishing
vault_dimensions:
12, 14
detection_signals:
polished delivery, well-timed pacing, smooth transitions between sections, confident recovery from disruptions
related_patterns:
crucible, retrieval-beat
inverse_of:
difficulty:
foundational
observable:
No

Carnegie Hall

Summary

"Practice, practice, practice." Dedicate four structured rehearsals with escalating goals before the real performance to achieve polished, confident delivery.

The Pattern in Detail

The name comes from the classic joke: a tourist asks a New Yorker "How do I get to Carnegie Hall?" and receives the answer "Practice, practice, practice." This pattern codifies rehearsal not as a vague suggestion but as a structured, multi-phase process with specific goals at each stage. The key insight is that different rehearsals serve different purposes, and conflating them reduces the effectiveness of all.

The four-rehearsal framework works as follows. Rehearsal one focuses on pacing and timing: run through the entire presentation and note how long each section takes. Identify where you consistently run long or short. This is a mechanical pass — do not worry about delivery polish yet. Rehearsal two shifts focus to delivery concerns: vocal variety, body language, slide transitions, and the handling of demos or live code. This is where you notice that you always stumble on that one transition or that a particular joke falls flat. Rehearsal three is the audition pass: incorporate all the fixes from the first two rehearsals and run the talk as if performing live. Ideally, do this in front of a small audience — coworkers bribed with lunch make excellent guinea pigs. Rehearsal four is about finding the groove: by this point the mechanics are solid, and you can focus on the intangible qualities of flow, energy, and connection.

Start by presenting to cats (or an empty room), then graduate to friendly colleagues. Record yourself on video during at least one rehearsal and force yourself to watch it, painful as that may be. Video reveals habits you cannot detect in the moment: fidgeting, vocal tics, reading from slides, pacing patterns. Neal Ford has talks he has presented fifty or more times, and each delivery still benefits from the rehearsal investment.

The rehearsal process also builds muscle memory for your presentation flow. When you have rehearsed enough, you no longer need to think about what comes next — your brain handles transitions automatically, freeing you to read the room, adapt to audience reactions, and recover gracefully from disruptions. This is the difference between a speaker who delivers content and a speaker who performs.

Many speakers skip rehearsal because they "know the material." Knowing the material and being able to deliver it compellingly are entirely different skills. A jazz musician knows music theory, but still practices before a gig. Your presentation deserves the same respect.

Rehearse by Retrieval, Not Rereading

The four-rehearsal framework says how many times to practice and what to aim at each time. It does not say what practice is, and the default answer most speakers reach for is the one that does the least good: open the deck, advance through it, talk over each slide until the whole thing feels smooth.

That is rereading with extra steps, and its smoothness is a lie. Each slide cues the words that go with it, so the speaker never once has to produce the talk from memory — the deck produces it for them. What builds across those run-throughs is fluency in the presence of the cue, and the speaker experiences that fluency as mastery. Then the cue changes. The clicker fails, the projector shows the wrong slide, a question arrives two sections early, the fire alarm eats six minutes and the deck has to be re-planned live — and the fluency evaporates, because it was never in the speaker. It was in the slides.

This is the fluency illusion aimed at its own author, and it is the exact mechanism _anti_nodding-room.md describes on the audience side. The room mistakes recognition for learning; the speaker mistakes a cued run-through for knowing the talk. Both are betrayed by the same finding: the feeling of ease is produced by the presence of the cue, not by the strength of the memory.

The fix costs nothing and changes the four rehearsals from the inside:

  • Close the deck and retrieve the spine. Before running the slides, say the talk's structure out loud from memory — sections, order, the point of each, the transitions between. Where you stall is where the talk is actually weak; the run-through would have papered over exactly that spot, because the slide would have told you what came next.
  • Rehearse the transitions cold. The joins are what the deck cues most aggressively and what fails first when anything goes wrong. Practice going from section three to section four with nothing in front of you.
  • Let it be uncomfortable. Closed-deck rehearsal feels markedly worse than an open-deck run-through. That is the tell that it is working, not a sign to stop; smoothness is the sensation the cue produces, and you have just removed the cue.

Space them. The four rehearsals crammed into the night before are massed practice, which produces the strongest possible feeling of readiness and the weakest retention — the same trade as cramming for an exam, with the same morning-after result. Four rehearsals across four days beat four rehearsals across one evening, and it is not close. The one that lands the day before does the least work of the four; the one that lands five days out, when the material has gone cold enough that retrieving it is genuinely hard, does the most.

This does not replace the four-rehearsal structure — pacing, delivery, audition, groove all still apply. It changes what happens inside each: retrieve first with the deck closed, then run it open to test what the retrieval revealed. The audition pass in front of colleagues remains the highest-fidelity rehearsal available precisely because a live audience is the one condition that removes every cue you have been leaning on.

When to Use / When to Avoid

Use this pattern for every presentation, scaling the number of rehearsals to the stakes involved. A keynote demands all four rehearsals; a familiar talk at a local meetup might need only a quick timing pass. Avoid over-rehearsing to the point where delivery becomes robotic — the goal is confident flexibility, not rote memorization. If you find yourself delivering lines identically every time with no room for spontaneity, you have crossed the line.

Detection Heuristics

  • Delivery flows smoothly without visible hesitation at transitions
  • Speaker recovers from interruptions without losing thread
  • Timing fits the allocated slot naturally, without rushing or padding
  • Body language appears natural and practiced, not stiff or uncertain

Scoring Criteria

  • Strong signal: Delivery is polished, well-timed, with smooth transitions and confident handling of any disruptions — clear evidence of multiple rehearsals
  • Moderate signal: Delivery is competent but shows occasional rough edges — timing slightly off, one or two awkward transitions
  • Absent: Delivery feels unrehearsed — stumbling over transitions, poor timing, reading from slides, visible uncertainty about what comes next

Relationship to Vault Dimensions

This pattern maps to Vault Dimension 12 (Delivery Mechanics) through the direct improvement of pacing, transitions, and physical delivery, and to Vault Dimension 14 (Speaker Craft / Professionalism) through the discipline and preparation that rehearsal represents.

Combinatorics

Carnegie Hall is the rehearsal counterpart to Preparation's logistics focus. Together they form the complete pre-performance foundation. Carnegie Hall directly enables Breathing Room (you can only place strategic pauses when you know your timing), supports Display of High Value (rehearsal builds the confidence that projects authority), and feeds into Crucible (post-delivery refinement builds on rehearsal insights). The Shoeless pattern can be incorporated into rehearsals to test comfort rituals.

It shares its central mechanism with retrieval-beat — closed-deck rehearsal is a Retrieval Beat the speaker performs on themselves — and its failure mode with _anti_nodding-room.md, which is the same fluency illusion seated in the audience instead of on the stage. A speaker who rehearses by rereading and a room that learns by nodding are making identical mistakes about what ease means.

Related Reading

  • Brown, P. C., Roediger, H. L., III, & McDaniel, M. A. (2014). Make It Stick: The Science of Successful Learning. Ch. 5 — "Avoid Illusions of Knowing" supplies the fluency-illusion mechanism behind cued rehearsal; Ch. 3 — "Mix Up Your Practice" supplies the massed-versus-spaced argument for distributing the four rehearsals across days rather than one evening. Belknap Press / Harvard University Press.

skills

presentation-creator

references

patterns

_index.md

alternate-entry-flows.md

deck-editing-setup.md

deckops-spec.md

idea-sourcing-wizard.md

pattern-history-authorization.md

phase0-intake.md

phase1-intent.md

phase2-architecture.md

phase3-content.md

phase4-guardrails.md

phase5-slides.md

phase6-publishing.md

phase7-post-event.md

SKILL.md

README.md

tile.json