---
name: claude-product-demo-video
description: Script and direct product demo videos: pick one workflow, use real screenshots, plan zooms, cursor clicks and callouts, and match length to the channel. Use when the user asks for a product demo, walkthrough, product tour, feature video or onboarding video.
---

# Product demo video skill

A demo shows one job getting done. Everything else is a different video.

## Script template
1. Hook (2 s): the trigger moment. "Monday, 9:00, the report is due."
2. Promise (2 s): the outcome. "Acme builds it in 30 seconds."
3. Step 1, 2, 3 (5 to 8 s each): one action per step, shown on the real UI.
4. Proof (3 s): a number, a customer logo or a quote.
5. CTA (3 s): one action and the URL.

## Tour grammar
- Snap-zoom (0.4 to 0.6 s) onto the area that matters, hold, then release.
- A visible cursor and click on every action; numbered callouts (max 6 words each).
- Depth of field or dimming on everything outside the focus area.
- Never zoom on empty states or loading spinners; use a finished state.

## Rules
- Real UI only. Ask for the URL, screenshots or a recording; never invent screens.
- Hide personal data in screenshots (names, emails, tokens).
- One workflow per video. If there are three workflows, make three videos.
- Length: about 30 s for site and social, 60 to 90 s for onboarding and sales.

## Render with Claude Video (optional)
If the Claude Video MCP server is connected (tools: `guide`, `create_video`, `get_video`, `update_video`,
`edit_video_with_ai`, `preview_frame`, `render_video`, `get_job`):
1. Call `guide` once, then `create_video` with a brief (or a full VideoSpec as `spec`).
2. Check key moments with `preview_frame`, fix with `update_video` or `edit_video_with_ai`.
3. Only when it looks right, `render_video` and poll `get_job` for the MP4 link. Do not render drafts.
Setup: remote MCP server `claude-video`, URL `https://claudevideo.io/api/mcp`, header `Authorization: Bearer <API key>`.
