From se-skills
This skill should be used when the user asks to "build a demo script", "create a demo", "prepare a product demonstration", "generate a demo narrative", "plan a customer demo", or needs to structure a customer-facing technical demonstration with step-by-step instructions, fallback plans, and environment checklists. Incorporates Tell-Show-Tell rhythm, persona-driven vignettes, and demo hierarchy (Standard → Custom → POC → POV).
How this skill is triggered — by the user, by Claude, or both
Slash command
/se-skills:demo-builderThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a structured demonstration script from customer scenario and feature requirements. The output includes scene-by-scene narrative, operation steps, expected results, fallback plans, and environment/data preparation checklists.
Generate a structured demonstration script from customer scenario and feature requirements. The output includes scene-by-scene narrative, operation steps, expected results, fallback plans, and environment/data preparation checklists.
At minimum, the customer's industry and a list of features to demonstrate are required. If either is missing, prompt the SE to provide them before proceeding.
The following optional inputs enhance the result:
outputs/discovery/<customer>-call-plan.md — for personalized scenario designknowledge/oss-feature-matrix.md — for verifying feature availability in the OSS versionknowledge/cases/ — for real-world success stories to weave inExtract from SE input:
| Field | Description | Required |
|---|---|---|
| customer | Customer name | Yes |
| industry | Industry | Yes |
| scenario | Demo scenario description | Yes |
| features | Features to showcase | Yes |
| duration | Total time in minutes | No, default 30 |
| audience | Technical / Business / Executive | No |
| pain_refs | Known pain points (can read from call-plan) | No |
Classify the demo into one of four levels. Downstream structure adapts to the level:
| Level | Effort | When to Use | Customization |
|---|---|---|---|
| Standard Demo | Low | First call, broad interest | <10%, OOTB gallery, education + vision setting |
| Custom Demo | Medium | Validated pain, specific use case | >10%, requires discovery write-up and buyer sign-off |
| Technical POC | High | Technical validation needed | SSO, integrations, security review (~30 days) |
| Proof of Value (POV) | Highest | Structured evaluation with business outcomes | Success criteria, mutual action plan, measurable results |
Structure the demo in three acts, using Tell-Show-Tell rhythm within each scene:
[Pain Resonance 20%] → [Solution Walkthrough 60%] → [Wow Moment 20%]
Each scene follows Tell → Show → Tell:
Alternative pattern: "Do the Last Thing First" (Great Demo! method): Instead of building up to the outcome, start with it. Open the demo on the finished dashboard, report, or solved state that executives care about most. Then peel back layers only in response to prospect questions — "How did we get here? Let me show you."
Persona-driven vignettes (for Standard and Custom demos): Build the narrative around a single persona (e.g., "Sofia, the operations manager"). Walk through her daily struggle, the moment she uses your solution, and the victory. The customer is the hero; the product is the helper.
Audience-adaptive design (the "3 brains" model):
| Brain | Role | Demo Application |
|---|---|---|
| Reptilian | Filters for threat | Avoid creating urgency via fear; stay composed |
| Limbic | Drives emotion | Stories and vignettes hit here — make them feel the transformation |
| Neocortex | Handles logic | Keep it simple — this is where they justify the emotional decision |
Output outputs/demo/<customer>-demo-script.md:
---
skill: demo-builder
date: <YYYY-MM-DD>
inputs: <SE input>, <referenced call-plan/case/feature-matrix>
status: draft
---
# Demo Script — <Customer Name>
## Basic Info
- **Duration**: N minutes
- **Audience**: Technical / Business / Executive
- **Goal**: <One sentence: what the audience should believe after the demo>
## Data Preparation Checklist
> Confirm all data is ready before the demo
| # | Data Item | Description | Done |
|---|-----------|-------------|------|
| 1 | <Industry> dataset | <Specific content> | ☐ |
| 2 | User/role configuration | <Roles, permissions> | ☐ |
| 3 | ... | ... | ☐ |
## Environment Checklist
| # | Check | Verification | Done |
|---|-------|-------------|------|
| 1 | <Service/module> running | curl / page check | ☐ |
| 2 | Network connectivity | ... | ☐ |
| 3 | Correct version | git tag / version endpoint | ☐ |
## Demo Flow
### Scene 1: <Scene Name> (Pain Resonance, ~N min)
**Persona**: <Who is the protagonist of this scene>
**Tell** (Set context):
<Remind them of the problem — use their own language, reference discovery insights>
**Show** (Demonstrate):
1. Open <page/terminal> → enter <command/parameters>
2. Click <button/menu> → display <content>
3. ...
**Tell** (Recap impact):
<Connect what they just saw to a measurable outcome. "This means your team can..." >
**Expected Result**:
<What the screen should show>
**Fallback**:
If <step X> fails:
- Plan A: Switch to pre-recorded GIF (path: ...)
- Plan B: Verbal explanation + screenshot (path: ...)
- Plan C: Skip, transition phrase: "..."
**Composure note**: If something breaks, acknowledge it casually — "This is my demo instance acting up" — and pivot to conversation about their problem. Never panic. Prospects mirror your emotional state.
### Scene 2: <Scene Name> (Solution Walkthrough, ~N min)
...
### Scene N: <Scene Name> (Wow Moment, ~N min)
...
## Transition Quick-Reference
| From | To | Transition Line |
|------|----|-----------------|
| Scene 1 → 2 | "We just saw the problem — here is how we solve it..." | ... |
| Scene 2 → 3 | ... | ... |
## Q&A Ammo
> Common post-demo questions with prepared responses
| Customer may ask | Response direction | Reference |
|-----------------|-------------------|-----------|
| Deployment complexity? | ... | feature matrix: deployment |
| Integration with existing system X? | ... | case: <case> |
| Performance benchmarks? | ... | ... |
/case-import or updating the discovery call plan<pause>), not read-from-script stifftest_user_1npx claudepluginhub futuretea/se-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.