What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Chat-to-Result Launch Film

When to use

• You're launching a chat-based product and screenshots of bubbles don't show what it actually delivers
• Your demo needs to answer "so what does the chat actually produce?" in under two minutes
• You have a launch-day video slot and want the audience to see the full journey: ask → chat → result
• Your product's magic is the last step — the booking confirmed, the document drafted, the task done
• You need one canonical film that sales, support, and marketing all point to when explaining the product

Workflow

1. Pick the one conversation (input: product capabilities → output: hero flow)
   Choose a single realistic conversation that ends in a concrete result — not a tour of everything the bot can do. The hero flow has a relatable ask ("I need a dentist appointment Thursday"), a short exchange (3–6 turns), and a result the camera can show (the confirmed booking). If the flow needs explaining, it's the wrong flow.
2. Script the exchange (input: hero flow → output: full script)
   Write the chat like real messages: short, human, with the typos and shorthand real people use. The assistant's replies show work, not just words — it checks, confirms, and acts. Every turn must move toward the result; small talk gets cut. Read the exchange aloud as two people — if it sounds like a brochure, rewrite it as a conversation.
3. Stage the result moments (input: script → output: shot list)
   The film's payoff is the result, so stage it: the confirmation screen, the drafted document appearing, the calendar event landing, the "done" state. Plan each result as its own shot — full-screen, held long enough to read, with a small visual cue (a check, a highlight) marking the moment it happens. The chat is the journey; the result is the destination the audience remembers.
4. Assemble the film (input: script + captures → output: rough cut)
   Cut to the script: hook (the ask, 5 seconds), the exchange (chat bubbles animating in real time, no faster than a person can read), then the result moments in full. Use real product captures for both chat and result — no mockups that the product can't actually produce. Music stays low; the message-arrival sounds are part of the rhythm. Target 60–120 seconds total.
5. Polish and ship (input: rough cut → output: final film + launch kit)
   Final pass: captions for every message (many viewers watch muted), consistent timing on the bubbles, end card with the product name and one call to action. Export 16:9 for the launch page and keynote, plus a vertical cut for social. Ship with a launch kit: thumbnail showing the result moment, one-paragraph description, and the one-line version of the flow for anyone introducing it.

Output spec

Template preview

Chat-to-Result Launch Film — Template

One conversation = one film, one result. Fill this in before scripting.

Launch: {product} — {launch date}

Hero flow (one line): {e.g. User asks for a dentist appointment Thursday → confirmed booking}

Result the film ends on: {e.g. confirmed appointment on screen}

The exchange (3–6 turns, realistic messages)

Read-aloud check: [ ] Sounds like two people, not a brochure | Every turn moves toward the result: [ ]

Result moments (shot list — each held long enough to read)

Production checklist

• [ ] Hook: the ask lands in the first 5 seconds
• [ ] Bubbles animate at reading speed, not faster

Buy the full skill pack — $4.99 Pro — all 471 skills