Ai Slide Demo Script Board

SKILL.md

---
name: "AI Slide Demo Script Board"
description: "Turns user-provided slide or demo context into a timed presentation script board with speaker notes, demo beats, claim checks, and fallback lines while flagging unverifiable claims."
version: "1.0.0"
type: prompt-flow
tags: ["presentation", "demo script", "slides", "speaker notes", "AI productivity", "claim review"]
---

# AI Slide Demo Script Board

## Overview

Use this prompt-only skill when a user needs to turn a slide deck, outline, or product demo plan into a clear presentation script board.

The skill organizes each slide or demo moment into purpose, talk track, visual cue, timing, transition, demo action, proof needed, and fallback line. It must only use facts supplied by the user or clearly marked as assumptions. Unverifiable claims are flagged instead of invented.

## When to Use

Use this skill when the user says things like:

- "Help me script this slide deck."
- "Make a demo script from these slides."
- "I need speaker notes and transitions."
- "Turn this product walkthrough into a timed script."
- "Check my presentation claims before I demo."
- "Build a script board for a sales, training, investor, or internal demo."

## Required Inputs

Ask for only the details needed to build the board:

- Audience and their likely level of context
- Goal of the presentation or demo
- Time limit and target pace
- Slide titles, slide text, screenshots, outline, or a pasted deck summary
- Demo steps, product areas, or live actions to show
- Facts, metrics, customer names, dates, or claims that are approved to use
- Required tone, such as executive, teaching, technical, sales, launch, or workshop
- Speaker constraints, such as single speaker, handoff points, or Q&A time
- Risks, sensitive topics, or claims that must be avoided

If the user has not provided enough facts for a claim, ask for the source or mark the item as needing verification.

## Workflow

1. **Confirm the presentation frame.** Restate the audience, goal, time limit, tone, and available slide or demo material.
2. **Segment the material.** Break the deck or outline into slide-by-slide or beat-by-beat rows.
3. **Assign intent.** For each row, name what the audience should understand, feel, or do next.
4. **Draft the talk track.** Write concise speaker notes in the user's requested tone.
5. **Add demo actions.** Note exactly what to click, show, pause on, or skip. If no demo action is available, write "none provided."
6. **Add visual cues.** Tie each talking point to visible slide text, chart areas, screenshots, or UI moments supplied by the user.
7. **Check claims.** Label each metric, customer statement, comparison, promise, or performance claim as verified from user input, needs source, assumption, or remove.
8. **Create transitions.** Add a short bridge from each slide or beat to the next.
9. **Prepare risk and fallback lines.** Add recovery language for loading delays, missing data, demo failure, timing pressure, or audience objections.
10. **Balance timing.** Estimate seconds or minutes per row and trim low-value detail when the time limit is tight.
11. **End with next step.** Include closing line, call to action, and Q&A handoff if relevant.

## Output Format

Produce the script board with these sections:

1. **Presentation Frame**
   - Audience
   - Goal
   - Time limit
   - Tone
   - Materials used
2. **Slide Demo Script Board**
   - Slide or beat number
   - Title or moment
   - Audience takeaway
   - Talk track
   - Visual cue or demo action
   - Timing
   - Transition
   - Claim status
3. **Claim Check List**
   - Claim
   - Status: verified from user input, needs source, assumption, or remove
   - What proof is needed
   - Safer wording if proof is missing
4. **Demo Risk Board**
   - Risk or failure point
   - Prevention note
   - Fallback line
5. **Timing Trim Plan**
   - Must keep
   - Can shorten
   - Can skip if time runs short
6. **Opening and Closing Lines**
   - Opening
   - Closing
   - Q&A handoff or next step
7. **Missing Inputs**
   - Any details needed before this is presenter-ready

## Example Prompts

Copy and paste one of these into your AI assistant with your slide details filled in:

1. **Sales demo script:** "I have a 15-minute product demo for a sales call with 8 slides. Audience is a VP of engineering and their team. Here are my slide titles: [Problem, Current Pain, Our Approach, Architecture, Key Features, Customer Example, Pricing, Next Steps]. Build a script board."

2. **Investor pitch:** "I need a 20-minute investor pitch script from my deck outline. Tone should be confident but measured. I have 12 slides plus a Q&A slide at the end. Here's each slide's key message: [paste outline]."

3. **Training walkthrough:** "Turn this training deck into a 30-minute script board with live demo beats. Audience is new users who just signed up. I'll be showing the actual product UI. Here are my slides and demo steps: [paste deck summary and demo flow]."

## Safety Boundary

- Do not invent facts, product capabilities, metrics, case studies, customer names, dates, compliance claims, benchmarks, prices, roadmap promises, or competitive comparisons.
- Flag unverifiable claims clearly and give safer wording such as "early results suggest" only when that wording still matches user-provided evidence.
- Do not claim to have viewed slides, screenshots, analytics, or product screens unless the user supplied them or an available tool actually opened them.
- Do not fabricate speaker credentials, legal approvals, security certifications, customer permission, or production readiness.
- Mark assumptions and placeholders visibly.
- If the deck involves medical, legal, financial, safety, hiring, or regulated claims, recommend source review by the relevant qualified owner before presenting.
- Do not provide scripts that mislead the audience about demo limitations, known outages, unreleased features, or unavailable data.

## Quality Checklist

A strong result should:

- Fit the audience, goal, tone, and time limit
- Provide slide-by-slide or beat-by-beat speaker notes
- Include demo actions and visual cues grounded in supplied material
- Identify every risky or unverifiable claim
- Offer safer wording for unsupported claims
- Include transitions, timing, fallback lines, and trim options
- Make missing inputs obvious before the user presents