home / skills / openclaw / skills / demo-video
This skill helps you create polished product demo videos by automating browser interactions and encoding frames into shareable formats.
npx playbooks add skill openclaw/skills --skill demo-videoReview the files below or copy the command above to add this skill to your agents.
---
name: demo-video
description: Create product demo videos by automating browser interactions and capturing frames. Use when the user wants to record a demo, walkthrough, product showcase, or interactive video of a web application. Supports Playwright CDP screencast for high-quality capture and FFmpeg for video encoding.
---
# Demo Video Creator
Create polished product demo videos by automating browser interactions.
## Overview
1. **Plan** the demo sequence (pages, interactions, timing)
2. **Record** frames using Playwright CDP screencast
3. **Encode** to video with FFmpeg
## Quick Start
### Prerequisites
- Clawdbot browser running (`browser action=start profile=clawd`)
- App accessible via browser (localhost or remote)
- FFmpeg installed for encoding
### Recording Workflow
1. Start the Clawdbot browser if not running
2. Navigate to the app manually or via `browser action=open`
3. Customize `scripts/record-demo.js` for the target app
4. Run: `node scripts/record-demo.js`
5. Encode: `bash scripts/frames-to-video.sh`
## Planning a Demo
See `references/demo-planning.md` for guidance on:
- Structuring demo sequences
- Timing and pacing
- Interaction patterns
- What makes demos compelling
## Scripts
### `scripts/record-demo.js`
Template Playwright script that:
- Connects to Clawdbot browser via CDP
- Starts screencast capture (JPEG frames)
- Executes demo sequence (navigation, clicks, hovers, typing)
- Saves frames to output directory
**Customize for each demo:**
- `DEMO_SEQUENCES` array - define pages and interactions
- `OUTPUT_DIR` - where to save frames
- `FRAME_SKIP` - skip every Nth frame (lower = more frames)
### `scripts/frames-to-video.sh`
FFmpeg encoding script with presets:
- `mp4` - H.264, good quality/size balance (default)
- `gif` - Animated GIF for embedding
- `webm` - VP9, smaller files
Usage: `./frames-to-video.sh [input_dir] [output_name] [format]`
## Interaction Patterns
```javascript
// Navigation
await page.goto('http://localhost/dashboard');
await page.waitForTimeout(2000);
// Click element
await page.locator('button:has-text("Create")').click();
await page.waitForTimeout(500);
// Hover (show tooltips, hover states)
await page.locator('.card').first().hover();
await page.waitForTimeout(1000);
// Type text
await page.locator('input[placeholder="Search"]').fill('query');
await page.waitForTimeout(500);
// Press key
await page.keyboard.press('Enter');
await page.keyboard.press('Escape');
// Scroll
await page.evaluate(() => window.scrollBy(0, 300));
```
## Tips
- **Timing**: 2s on page load, 0.5-1s between interactions, 1.5s to show results
- **Frame skip**: Use 3-5 for smooth video, 8-10 for smaller files
- **Quality**: 85-90 JPEG quality balances size and clarity
- **Resolution**: Browser window size determines output resolution
- **Loops**: GIFs should loop seamlessly - end where you started
This skill automates browser interactions to create polished product demo videos. It captures high-quality frames via Playwright CDP screencast and encodes them with FFmpeg into MP4, WebM, or GIF outputs. Use it to record walkthroughs, feature showcases, or interactive app demos with repeatable, scriptable sequences.
The skill connects to a running browser instance and starts a CDP screencast to capture JPEG frames. A customizable script defines navigation, clicks, hovers, typing, and timing to produce a deterministic demo sequence. Captured frames are saved to an output directory and then encoded into the chosen video format using FFmpeg presets.
What prerequisites are required to record?
A running browser instance reachable via CDP, the target app accessible in that browser, and FFmpeg installed for encoding.
How do I control timing and pacing?
Configure explicit waitForTimeout calls between interactions and follow recommended timings: ~2s for loads, 0.5–1s between actions, 1.5s to show results.