demo-scripting

Structures a codebase into a timed demo storyboard with narration and capture actions.

3|1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/lukaskellerstein/claude-my-marketplace --skill demo-scripting-lukaskellerstein
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: demo-scripting
Source: https://github.com/lukaskellerstein/claude-my-marketplace/tree/main/plugins/demo-video-plugin/skills/demo-scripting
Command: npx skills add https://github.com/lukaskellerstein/claude-my-marketplace --skill demo-scripting-lukaskellerstein

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Demo videos fail when they show the wrong features or present them as a flat feature tour. This Skill turns a codebase into a decision-driven demo narrative, producing a validated demo/storyboard.json with beats, durations, narration, and capture actions before any recording happens. ## Core Features & Use Cases - Capability selection: Ranks product capabilities by demo value and cuts the script to 3-5 substantive sections that fit a 90-second target. - Beat structure and pacing: Provides beat templates for SaaS, developer tools, AI products, desktop apps, and changelogs, with per-section targetSeconds and a 2.2-2.5 words-per-second narration budget. - Narration and action writing: Enforces a narration style that explains why things matter instead of describing clicks, and writes intent-level capture actions with idleUpTo waits and gradeable successCriteria. - Use Case: Given a new repository, draft demo/brief.md from the codebase, confirm the audience decision, then write a validated storyboard.json ready for voiceover generation and screen capture. ## Quick Start Analyze this repository and write a 90-second demo storyboard with narration and capture actions for our three most important capabilities.

Frequently Asked Questions about demo-scripting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product demo script from a codebase?▼

Start by drafting a brief that names the audience decision, then rank capabilities by demo value rather than engineering effort. Structure 3-5 sections into beats like hook, core-flow, and wow, and write narration at 2.2-2.5 words per second to fit each section's targetSeconds.

How long should a product demo video be?▼

A 90-second demo holds 3-5 substantive sections and is the default target. Sixty seconds fits one core flow, 120 seconds allows a proof or integration beat, and anything over 150 seconds needs chapters or should be split into two videos.

What makes demo video narration effective?▼

Effective narration explains why something matters instead of describing visible clicks, using present tense, active voice, and concrete numbers from the actual domain. Avoid filler phrases like "as you can see" or "seamless", and write lines that also work as standalone captions for muted playback.

How do I structure a demo for a developer tool or CLI?▼

Use the developer tool beat template: open on a recognizable failure mode, show a short install, run it with real terminal output, demonstrate the flag handling the edge case, and close with one command to try it. Developers trust real output over polished summaries.

What happens when I revise an existing demo storyboard?▼

Section ids are the join key for media, so renaming an id orphans its clip and audio. Changing narration invalidates that section's audio, and changing targetSeconds or actions invalidates its clip, requiring re-capture or regeneration for affected sections only.