Skill Locker
All skills
v1.3.03 loop iterations

Keynote Story Arc

Most keynotes are information delivery with a few jokes — the speaker shares what they know, the audience nods politely, and everyone forgets by lunch. The Keynote Story Arc builds the structure that turns expert knowledge into one unforgettable idea, with the opening loop, the framework, and the closing callback engineered to be remembered.

What this skill does

A keynote is the highest-stakes speaking opportunity most experts will ever have. Thirty to sixty minutes on stage, one-to-many, with an audience that chose to be there. The talk that follows determines whether the audience thinks of you as "interesting" or "transformative." The difference isn't talent or charisma — it's structure. The most naturally gifted speakers fall flat without a narrative arc, and technically average speakers deliver unforgettable talks when the structure carries them. Your job is to build the structure.

The one-idea rule is non-negotiable. A keynote delivers ONE transformative idea. Not three. Not seven. The audience will remember at most one thing from any talk, so talks that try to cover five end up with the audience remembering zero. The thesis has to pass three tests — surprising (contradicts what the audience currently assumes), specific (not "believe in yourself"), actionable (implies something they can think or do differently). Every story, every data point, every example in the talk has to serve that single idea. If it doesn't, it's cut.

The three-act structure is opinionated. Open with a story, not a thank-you, not your credentials, not an agenda. Personal, emotionally connecting, 3-5 minutes for a 30-minute talk, and crucially — unresolved at the open. The story creates a loop the closing will resolve. When multiple candidate stories exist, the skill ranks them on relevance to the ONE idea, emotional range, and audience identification. The strongest becomes the opener; the others become micro-stories in the body. State the thesis early — clarity beats mystery for keynotes. Act 2 builds the case through three elements: an evidence story (proves it works), a framework or reframe (the part the audience shares with others next week), and additional proof. Act 3 returns to the opening — closes the loop, gives one specific CTA, and ends on a deliberately written closing line.

The framework matters disproportionately because it's the shareable artefact. The skill includes naming patterns that work — "The [Noun] [Noun]" (The Trust Triangle), "The [Number] [Noun]s" (The 3 Levers), "The [Adjective] [Noun]" (The Quiet Advantage). The test is whether someone could reference it in conversation a week later. If they'd say "that framework she talked about" instead of the actual name, it isn't memorable enough. The framework also gets a "before/after" reframe: most people think about this like THIS — but what if we thought about it like THIS?

There's a duration-specific timing guide (10/18/20/30/45/60 minute versions, each block timed individually), an emotional arc map (curiosity → surprise → belief → understanding → confidence → resonance → determination), and a post-keynote Q&A preparation block with 5-7 anticipated questions, bridging technique for off-topic questions, and the discipline of ending Q&A on the speaker's terms rather than a random questioner's. Rehearsal techniques are specific — timed run-through (most speakers run 10-20% long on first rehearsal), opening-story drill (rehearse five times independently), transition practice (where speakers lose flow), and the "no slides" test (if the talk falls apart without slides, you're reading from slides rather than speaking from structure).

When this triggers

  • ·You've got a 20-45 minute keynote slot and your draft is currently a list of topics, not a talk
  • ·You're speaking at a conference and want the audience to actually remember the idea a week later
  • ·You're preparing a TEDx and need the structural discipline TEDx demands (one idea, story-led, 18 minutes)
  • ·You've got three good stories and don't know which one belongs at the top
  • ·You can't write a closing line — your draft ends with 'so, yeah, thank you'

Example

Trigger

User: '30-minute conference keynote in 6 weeks. Topic: how I shipped a product after burning out. Audience: 400 founders. I have three candidate opening stories.'

Output

The ONE-IDEA TEST — your thesis in one sentence that's surprising, specific, actionable: "The founders who ship after burning out aren't the ones who push harder — they're the ones who let go of the wrong project." OPENING STORY SELECTION (ranked by 3 criteria): 1. Hospital visit story → relevance HIGH (frames the talk), emotional shift YES (denial → reckoning), audience can identify YES — USE AS OPENING 2. Co-founder argument story → save as Element 1 evidence story 3. The unanswered-email story → micro-story between Element 2 and 3 THREE-ACT STRUCTURE (30 min): Act 1 (5 min): Hospital story → unresolved tension Thesis drop (1 min): the one-sentence claim Act 2 (21 min): · Element 1 (7m) — co-founder argument as evidence · Element 2 (7m) — "The Letting-Go Matrix" framework, named so the audience can reference it next week · Element 3 (5m) — the relaunch metrics Audience interaction every 7-10 min (3 moments built in) Act 3 (3 min): · Return — close the hospital-story loop · CTA — one thing they do Monday morning · Closing line — callback, deliberately written Plus: emotional arc map, Q&A prep with 5-7 anticipated questions and bridging technique, rehearsal protocol (timed run-through, opening-story drill, "no slides" test).

Get this skill + 4 more

Get the full Presentations pillar (5 skills) or the complete library.

Get the full stack — $299

What you get

  • 224-line SKILL.md, ready to drop into ~/.claude/skills/
  • Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
  • Triggers automatically when relevant — no command to remember
  • Lifetime updates as the skill is refined further

More from Presentations

Browse the full library

297 skills across 31 categories. One purchase, lifetime updates.

See all bundles