Demo Video Creator
PassAudited by ClawScan on May 10, 2026.
Overview
This skill does what it claims—records browser-based demo videos—but users should run it only against a demo browser/app because it can control the browser, capture page contents, and overwrite its frame output directory.
This skill appears purpose-aligned for recording product demos. Before installing or running it, review and customize scripts/record-demo.js, use a non-sensitive demo browser profile, confirm the intended page is open, and keep the output directory dedicated to captured frames.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The recording script may perform real actions in the browser, such as creating items or submitting searches/forms, depending on how it is customized.
The script automates navigation, clicks, typing, and keypresses in the connected browser. This is expected for a demo-recording skill, but it can change state in the target web app if run against a real account or production environment.
await page.goto('http://localhost/dashboard'); ... await button.click(); ... await input.fill('example query'); ... await page.keyboard.press('Enter');Use a demo account or local test app, review the DEMO_SEQUENCES before running, and avoid recording against production systems unless the actions are safe.
If the connected browser is logged into sensitive services, the recording may capture private information or perform actions with that account's permissions.
The skill expects use of an existing browser profile. Browser profiles may already be logged in to applications, so the automation can inherit that session's permissions even though no credentials are hardcoded or exfiltrated.
Clawdbot browser running (`browser action=start profile=clawd`)
Use a dedicated demo browser profile with non-sensitive data, and confirm the intended page is open before starting the recording.
Installation may fail or require extra local tools that are not reflected in the registry requirements.
The registry metadata does not declare the runtime tools that the artifacts require, while SKILL.md and the scripts reference Node.js/playwright-core, a Clawdbot browser CDP endpoint, and FFmpeg.
Required binaries (all must exist): none ... Install specifications: No install spec — this is an instruction-only skill.
Before use, verify that Node.js, playwright-core, the Clawdbot browser, and FFmpeg are available from trusted sources.
A misconfigured output directory could cause local file loss.
Before saving frames, the script deletes the configured output directory recursively. The default is a local demo-frames folder, which is proportionate, but changing OUTPUT_DIR to an important directory could delete unrelated files.
if (fs.existsSync(outputDir)) { fs.rmSync(outputDir, { recursive: true }); }Keep OUTPUT_DIR pointed at a dedicated frame folder, and do not set it to a directory containing important files.