Agent skill · Workflow & Productivity

sales-demo-script

Write a product demo script that tells a value story instead of a feature tour. Use when asked to write a sales demo script, structure a product demo, plan demo talk track and flow, or turn a feature list into a compelling demo. Produces a demo script — the setup and discovery hooks, a scene-by-scene flow tied to buyer pain, talk track, 'aha' moments, transitions, and a close with next steps.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill sales-demo-script --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/sales-demo-script/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Sales Demo Script Skill Write a demo that makes a buyer feel their problem being solved — a value story, not a click-through of every screen. The best demos show the shortest path to the "aha," anchored in the pain the buyer already told you about. ## What This Skill Produces - A demo objective and the one thing the buyer should feel by the end - Discovery hooks to tailor the demo live - A scene-by-scene flow tied to buyer pain, with talk track - Clearly marked "aha" moments and clean transitions - A close with a concrete next step ## Required Inputs Ask for these if not provided: - **Product** and the persona/buyer you're demoing to - **Their pain** — what problem they're trying to solve (from discovery) - **The value story** — the outcome the product delivers - **Key capabilities** to show (and which to skip) - **Proof** — data, before/after, or a realistic demo dataset - **Meeting context** — first demo, technical deep-dive, competitive bake-off; time available Use realistic sample data; don't imply results or claims you can't back — mark `[to confirm]`. ## Process 1. **Set the objective** — the single feeling/decision the demo should produce. 2. **Open with their world** — re

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Process
  4. Output Format
  5. Open (restate their world)
  6. Discovery Hooks (tailor live)
  7. Scene Flow
  8. Scene 1 — [Buyer outcome, not feature name]
  9. Scene 2 — [Buyer outcome]
  10. Handle Live Questions
  11. Close
  12. Quality Checks
  13. Anti-Patterns
  14. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the sales-demo-script skill do?

Write a product demo script that tells a value story instead of a feature tour. Use when asked to write a sales demo script, structure a product demo, plan demo talk track and flow, or turn a feature list into a compelling demo. Produces a demo script — the setup and discovery hooks, a scene-by-scene flow tied to buyer pain, talk track, 'aha' moments, transitions, and a close with next steps.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill sales-demo-script --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going