agentsclimarketplace

Keynote storytelling

Skill philister16/keynote-skills/skills/keynote-storytelling

Apply story frameworks and narrative micro-techniques to craft compelling stories, anecdotes, and narrative arcs inside keynote presentations and other high-stakes spoken formats. Use whenever the user wants to develop a story for a talk, find or apply a story framework, structure an anecdote, build a narrative arc for a presentation, apply the Pixar Story Spine, Duarte's Sparkline, Andy Raskin's Strategic Narrative, SCQA, Hero's Journey, or other story structures, sharpen a controlling idea, or make a section of a presentation more story-driven. Triggers on phrases like "story for my keynote", "anecdote for my talk", "narrative arc", "story spine", "story framework", "make this more story-driven", "tell this as a story", "what story should I use", "this section feels flat". Topic-agnostic; works for any spoken format. Pair with keynote-architect (which owns the talk-level spine) and is invoked while drafting individual stories inside the body of a talk.From its SKILL.md

Install
npx -y skills add philister16/keynote-skills --skill keynote-storytelling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

10.9 KB, as published. Nobody here has run it

Keynote Storytelling

Stories are not decoration on top of a talk — they are the talk's primary delivery mechanism for meaning. Arguments persuade; stories are remembered. This skill is the working toolkit for crafting the stories inside a high-impact keynote.

Use this skill after the spine is locked (via keynote-architect) and during the drafting of individual movements. Each movement of a 45-minute keynote typically needs one anchoring story; the cold open is almost always a story.

The three mechanics every story needs

Every story that works — across every framework, in every culture, in every era — pulls on the same three mechanics:

  1. Desire — a specific character wants a specific thing
  2. Obstacle — something concrete makes the wanting hard
  3. Transformation — the character (or the audience watching them) changes because of the struggle, at a cost

If a story you're telling lacks any of these three, it is not a story yet. It is an anecdote, an example, or a data point dressed in narrative clothes. Frameworks are different scaffoldings of these three things. Pick the framework that fits your material; don't force material to fit a framework.

Default framework: the Pixar Story Spine

Use this as your workhorse for individual stories inside the body of a talk. Most stories should fit this seven-sentence structure:

Once upon a time… Every day… Until one day… Because of that… Because of that… Until finally… And ever since then…

If you can't fill all seven sentences, the story isn't ready. Diagnostic notes on each sentence:

  • "Once upon a time…" — establish the character (often the speaker, or a named other person) in concrete terms. Avoid abstractions.
  • "Every day…" — the stable world. The status quo before the disruption. The audience needs to feel this stability so the disruption matters.
  • "Until one day…" — the inciting incident. The specific moment when normalcy breaks. Specificity is critical here — "one day in 2019" is weak; "a Tuesday afternoon in March 2019, at 4:47 PM" is strong.
  • "Because of that…" — the first consequence. What did the inciting incident cause?
  • "Because of that…" — the second consequence. The chain of causation is what makes a story feel inevitable rather than coincidental.
  • "Until finally…" — the resolution. The moment of change or insight.
  • "And ever since then…" — the meaning. What changed in the world, and why does it matter to the audience?

Fill out the worksheet at assets/story-spine-worksheet.md for each story you plan to tell.

Talk-level arc: Duarte's Sparkline

For the arc of the entire keynote, use Nancy Duarte's Sparkline (from Resonate). This is owned by keynote-architect, but understand it here so individual stories can support it.

The shape: open with "what is" (the current state). Contrast with "what could be." Oscillate — what is, what could be, what is, what could be — with the gap widening at each cycle. End at the new bliss — a vivid, sensory picture of life on the other side.

Stories you tell inside the talk should be assignable: each one should clearly belong on either the "what is" side (illustrating the cost of the status quo) or the "what could be" side (illustrating the promised land). Stories that don't belong to either side are usually stories that need to be cut.

Strategic Narrative: for business and ideas talks

Andy Raskin's "Greatest Sales Pitch" frame, also owned by keynote-architect, but powerful at the story level too. Five beats:

  1. Big shift — name a tectonic change happening in the world
  2. Winners and losers — there will be both, depending on how people respond
  3. Promised land — paint what the winners look like, in concrete terms
  4. Obstacles — what stands between here and there
  5. Magic — present your idea as the way through

The crucial property: this frame puts the audience in the role of protagonist, not the speaker. When you craft stories inside a Strategic Narrative arc, the audience should always be able to map themselves onto a character in the story — usually onto the person facing the obstacle.

SCQA: for arguments inside a movement

From Barbara Minto's Pyramid Principle. Use SCQA whenever you're making an argument, not telling a story:

  • S — Situation: state the context everyone already agrees on
  • C — Complication: introduce the fact that breaks the agreement
  • Q — Question: raise the question the complication forces
  • A — Answer: deliver your claim

SCQA makes an argument feel inevitable rather than asserted. The audience experiences you as responding to a question they suddenly have, rather than as lecturing them.

For deeper notes on these and other frameworks (Hero's Journey, Three-Act, Story Circle, Save the Cat), read references/frameworks.md.

The controlling idea: the test under every story

Every story should map to a single causal sentence: "X happens because Y." Not a topic, not an aspiration — a claim about cause.

  • "Vulnerability creates connection because it gives others permission."
  • "The default path is dangerous because it accumulates invisible debt."
  • "Generative AI is reshaping work because the bottleneck shifted from execution to judgment."

If you can't write that sentence for a story, the story isn't done. This is the most useful single test.

Micro-techniques: where most of the work happens

Frameworks are scaffolding. These small moves are what make individual sentences land. Apply them line by line during script editing.

Specificity beats abstraction

"Tuesday at 4:47" beats "one day." "Maria, a billing manager at a 200-person logistics company in Memphis" beats "a customer." Specificity is what makes a story feel real; abstraction is what makes it feel like a corporate brochure.

Rule of thumb: in any sentence, if you can replace a generic noun with a specific one — do it. "A team" → "the seven of us in that conference room." "A long time" → "three years and four months."

Start in medias res

Drop the audience into a moment of action; back up to explain after.

✓ "I was halfway across the parking lot when my phone rang…" ✗ "Last year, I was working on a project, and one day…"

The first sentence pulls; the second loses.

Show the moment, then extract the lesson — never reverse

✓ "Here's what happened, and here's what I learned…" ✗ "Here's a principle. Let me illustrate it…"

Order matters enormously. The lesson lands harder when the audience feels they discovered it inside the story.

The rule of three

Three escalating examples land better than two (too thin) or four (one too many). Three is the smallest number that creates pattern recognition. Use three customer examples, three signals, three steps.

Callbacks

Plant a phrase, image, or named person early. Pay it off later. Audiences love noticing that you were always going somewhere — it gives them the click of a completed story. The single highest-leverage callback is the bookend: plant in the opening, pay off in the close.

Curiosity gaps

Introduce a question. Delay the answer. The unanswered question is the tractor beam pulling the audience through the next five minutes. "I'll come back to what happened that Tuesday in a minute — but first…"

The tactical disclosure

Name a specific thing you got wrong. Not vague "I've made mistakes." A specific moment, a specific bet, a specific person you let down. Specificity is the credibility.

Sensory detail

Engage at least two senses in any extended story. What did the room smell like? What was the texture? What sound was in the background? Audiences experience stories more vividly when other senses besides sight are activated.

Named characters

Use real names whenever possible (with permission). "Sarah" beats "a colleague." Named people feel real; unnamed people feel like rhetorical devices.

For more detail on each technique with examples, read references/micro-techniques.md.

How to use this skill

  1. For the whole-talk arc: the Sparkline or Strategic Narrative is already chosen by keynote-architect. Confirm it.
  2. For each movement that needs a story: apply the Pixar Story Spine. Don't move on until all seven sentences are filled.
  3. For arguments inside a movement: apply SCQA.
  4. For every sentence: stress-test against the micro-techniques. Replace abstractions with specific images, names, times, places.
  5. For the talk overall: verify every story maps cleanly to the controlling idea ("X because Y"). Cut anything that doesn't, no matter how good.

What to cut, even when it hurts

The single hardest discipline in storytelling is cutting material you love. The test: does this story bend toward the controlling idea? If it's interesting but doesn't, it has to come out. Keep a "darlings" file for cut material — you'll use it in another talk.

A useful heuristic: if a story makes you laugh in rehearsal but the audience can't immediately see how it advances the thesis, it's almost certainly a story for a different talk.

A working order for crafting stories

For each movement of the talk that needs a story:

  1. Identify the claim this movement makes (from the spine).
  2. Write the controlling-idea sentence for the story: "_____ because _____."
  3. Find a real, specific incident from your experience (or a credible second-hand account) that demonstrates that causal claim.
  4. Fill out the Pixar Story Spine worksheet.
  5. Stress-test against micro-techniques: every abstract noun replaced with a specific one, every cliché cut, in medias res opening, lesson extracted after the moment.
  6. Time the story aloud. Stories in keynotes are typically 90 seconds to 4 minutes — shorter than people think.
  7. Identify the call-back hook in the story — a phrase, image, or detail you might return to later.

This process is slower than improvising and faster than redrafting after rehearsal goes wrong.

Keep looking

Skills are one crate of 608,352. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.