Demo Script Skill

Feature-tour demos die politely: "here's the dashboard, here's settings, here's our AI" — a museum walk through someone else's house. The demo that lands is a story about the audience's day: their actual workflow, with its familiar pain, walked through the product — pain first (recruit the deck-narrative-arc tension), the wow moment inside the first three minutes (attention is front-loaded; demos that save the best for last perform it to phones), and every click scripted on a rehearsed golden path with the contingency kit standing by — because live demos break, and the difference between a stumble and a disaster is whether the recovery was pre-built.

What This Skill Produces

• The storyline — the audience-persona's task, start to done, with the pain named before the product answers it
• The click-path script — every step: the click, the talk-track line, the thing to point at
• The wow placement — the moment chosen for this audience, landed by minute three
• The contingency kit — the reset state, the backup recording, the narration bridges for every known fragility

Required Inputs

Ask for these if not provided:

• The audience and their workflow — who's watching (the user? their boss? an exec who'll never touch it?) and the task they actually do; the demo walks their Tuesday, and exec audiences get outcomes-dense, click-light versions
• The wow candidate — the moment that reliably drops jaws for this audience type (the migration that takes seconds, the answer that used to take a day) — chosen deliberately, not discovered mid-demo
• The product's fragilities, honestly — what's slow, what's flaky, what needs data seeded; the kit is built from the real list
• The demo environment — live product, staging, or sandbox; and whether the data in it tells the story (demo data is a script character — "Acme Corp, 47 orders" beats "Test test 123")