Menu

Individual skill

demo-script

0upvotes

Builds a product demo script around the buyer's discovered pain - a 60-second situation recap opening, three to four before/after "moments" mapped to the buyer's metric, and a close that ends before the slot does. Use when someone asks "help me script this demo", "how should I structure tomorrow's product walkthrough", "turn these discovery notes into a demo plan", or before any live or recorded demo. Do NOT use for staging and directing the demo environment, data, and rehearsal - use product-demo-director instead. Do NOT use when discovery hasn't happened yet - run discovery-call-prep first, because a demo without known pain is a feature tour.

skills/demo-script/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Demo Script

A feature tour is not a demo. Buyers do not care about features - they care about outcomes, and the job of a demo is to make the buyer see themselves solving a specific problem they described in discovery. The costly failure this skill prevents is the tour that fills the whole slot, impresses the presenter, and leaves the buyer with no reason to take a next step.

## Operating procedure

The order is fixed: inputs gate everything (no discovery, no demo), moments are selected before the open is written (the recap promises what the moments deliver), and pacing is set last.

### Step 1: Gather inputs - the three-fact gate

Pull the discovery notes and extract:

1. The primary pain the buyer named, in their words.
2. The current workaround they use today.
Back to top