About sales-demo-script-review
A skill for sales teams that turns demo preparation into a tailored script and reviewable plan. It structures discovery, proof, objections, timing, and follow-up around a buyer's role and desired outcome.
Key features
- 01Buyer and sales-stage discovery
- 02Role-specific demo narrative
- 03Talk track and click path
- 04Timing and proof points
- 05Objection handling and follow-up
Use cases
- 01Preparing a buyer-specific product demo
- 02Planning proof for a sales-stage outcome
- 03Structuring objections and next steps
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill sales-demo-script-reviewAfter installing, type/sales-demo-script-reviewin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlreferences/sales-demo-patterns.md
Details
From the project READMESales Demo Script Review
Use this skill to turn a recurring product-operations problem into a concrete, reviewable artifact instead of generic advice.
Workflow
- Identify buyer persona, pain, current workaround, desired outcome, sales stage, proof assets, and timebox.
- Read
references/sales-demo-patterns.md. - Build a demo around discovery, promised outcome, narrative, proof path, objection handling, and next commitment.
- Tailor the script to buyer role instead of giving a generic feature tour.
- Produce talk track, click path, timing, proof points, objections, and follow-up plan.
When not to use
- Do not use for generic advice the base model already handles without this skill's specific artifact contract.
Guardrails
- Do not invent customer logos, ROI, compliance, integrations, or roadmap commitments.
- Do not demo every feature; show the shortest credible path to the buyer outcome.
- Keep discovery questions before claims when pain is not proven.
- Separate product truth from sales hypothesis and roadmap possibility.
Output format
Demo context:
Buyer / pain / stage / timebox:
Demo script:
| Time | Segment | Talk track | Click/proof | Buyer check |
| --- | --- | --- | --- | --- |
Objection handling:
- <objection> -> <answer/evidence/follow-up>
Next step:
- <commitment, owner, deadline, proof>
Comments
Markdown supported