Individual skill
b2b-demo-builder
Use this skill when building a pre-recorded demo script or preparing for a live demo. Covers intake, scripting, talk tracks, objection handles, and fallback planning. Trigger on "build a demo", "demo script", "prep me for a demo", "record a demo", "product walkthrough", or any request to demonstrate a product to prospects, investors, or customers.
skills/monica-dinu/b2b-demo-builder/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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)
- 237
- Repository last updated
- Oct 20, 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
SKILL.mdcore · 5,254 bytesreferences/live-demo-prep.mddoc · 5,470 bytesreferences/pre-recorded-demo.mddoc · 4,743 bytes
Read excerpt
Build demo scripts and prep materials that start with the outcome, lead with the magic, and go deep only when earned. Grounded in Monica Dinu's Outcome-First Demo Framework, synthesizing Cohan, Falcone, Efti, Dunford, and Gong.io research.
---
## Phase 0: Pre-Work
**Tier 1 -- Must have before scripting.** Ask if not provided.
1. **Product**: What is the product and what does it do?
2. **Capabilities**: Full list of capabilities. Use existing docs if available. Never demo a capability not on this list.
3. **Audience**: Role, seniority, buying stage, technical sophistication.
4. **Industry**: Which vertical or segment? Always ask. Shapes data, language, use cases, and pain points.
5. **Primary outcome**: The #1 thing this audience wants to achieve. Success for THEM, not the product.
6. **Mode**: Pre-recorded or live?