Installs into .claude/skills of the current project.
Are you the author of Demo Narration?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wanfeng1028-demo-narration)
---
name: demo-narration
description: Write connected spoken narration for a product demo, with natural coverage of visible actions and claims grounded in evidence.
---
# Demo narration
Use this skill to write or revise the spoken track for an approved storyboard. The voice should sound like a capable colleague showing a real screen: concise, connected, and specific to the viewer's task.
Keep the exact product facts and accepted wording. Every visible click, typed entry, and drag needs nearby spoken coverage that explains what is changing and why it matters or what state follows. Explain the action without mechanically repeating the button label or narrating cursor movement.
## Workflow
1. Read the brief and storyboard; do not invent claims or change the story under the guise of copyediting.
2. Draft one connected arc from the opening question through decisions and visible proof to the payoff.
3. Map every active browser action to a verbatim, whole-word spoken anchor in the canonical narration. Take control names from the page's scouted accessible names, not from memory.
4. Read adjacent scenes aloud as one lesson. Fix repeated cadence, abstract transitions, and abrupt handoffs.
5. Preserve the approved canonical words in captions and send the exact draft to [demo-story-review](../demo-story-review/SKILL.md). Read [spoken narration guidance](references/spoken-narration.md) for detailed checks.
Name what is on screen instead of saying "this" or "here", and define each unfamiliar term the first time it is spoken. First person is useful when it conveys a real choice; use it where natural, not as a repeated “I’ll click” transcript. Never accelerate speech to fit a target runtime. Tighten the story or give the proof more room.
