Produces professional 30-60s narrated browser demo videos from a storyboard.

Install

mkdir -p .claude/skills/record-demo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18156" && unzip -o skill.zip -d .claude/skills/record-demo && rm skill.zip

Installs to .claude/skills/record-demo

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Produce a short (30-60s) narrated, captioned product demo video with the aidemo engine, via the aidemo MCP server. Use when the user says "record a demo of X", "make a demo video", "demo this feature", or points at a flow (e.g. a shopping flow inside a ChatGPT app) and wants a shareable MP4 with voiceover + captions. The skill authors a storyboard.json (script + per-scene voice/music plan + browser action-spec) and renders it with the engine. Do NOT use for: live screen-sharing, editing an already-rendered MP4, or demos of native/mobile apps (browser only).
563 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Generate a storyboard.json for product demos
  • Render MP4s with voiceover and captions
  • Simulate browser actions for demos
  • Utilize the `aidemo` engine via MCP server or CLI
  • Validate storyboard edits before rendering
  • File engine bugs or surprises via `feedback` tool

How it works

The skill acts as a demo director, authoring a `storyboard.json` (script, voice/music plan, browser action-spec) and rendering it into an MP4 video using the `aidemo` engine. It can use either an MCP server or CLI.

Inputs & outputs

You give it
A feature or flow description for a product demo
You get back
A short (30-60s) narrated, captioned product demo video in MP4 format

When to use record-demo

  • Record feature demos
  • Generate marketing videos
  • Create walkthroughs

About this skill

record-demo

You are the demo director. Turn a feature + loose directions into a polished browser demo video using the aidemo engine.

This file is a thin adapter. The authoring knowledge lives in the engine — fetch it first, then follow it:

  1. Preferred — the aidemo MCP server (registered by aidemo repo-init, or bundled automatically if you installed the Claude Code plugin): call the get_authoring_guide tool and follow the guide. Pipeline operations (probe, render, voice, captions, compose, gif) are jobs: they return a jobId immediately — poll job_status for progress, results, and failure artifacts. Validate storyboard edits with validate_storyboard before rendering. Pass absolute demo directories.
  2. Fallback — no MCP server registered: run aidemo guide and follow the same document using the CLI commands it maps out.
  3. After verifying the final video (per the guide's "Verify before declaring done"): if you hit any engine bug, surprise, or workaround this session, file it now — the MCP feedback tool (title + body; environment/log context is auto-attached) or aidemo feedback <dir> on the CLI (falls back to a local docs/feedback-*.md offline). If nothing came up, skip this step.

Invoking the engine (aidemo)

aidemo <cmd> means whichever of these applies:

  • In the aidemo repo itself (a full checkout): node bin/aidemo.mjs <cmd>.
  • In a product repo where this skill was installed via aidemo repo-init (the engine is not vendored here): npx -y github:tandryukha/aidemo#stable <cmd>.

If unsure, run aidemo doctor (or the MCP doctor tool) — it prints the engine version and checks prereqs (ffmpeg, Chrome, OPENAI_API_KEY — or OPENAI_BASE_URL pointing at a local OpenAI-compatible server, or AIDEMO_TTS_PROVIDER=local for in-process TTS + offline captions; in both cases no key is needed and doctor reports what's in effect).

Distribution & updates

This skill is a versioned copy of the source in the aidemo repo. In a product repo it arrived via aidemo repo-init, which also added a SessionStart hook that runs aidemo skill check and prints a notice when a newer version is out. (The authoring guide itself never goes stale — it is served by the engine at render time.)

  • Update the skill (when notified, or any time): aidemo skill update --dir . — rewrites this file and bumps .claude/skills/record-demo/installed.json. Installed as a Claude Code plugin instead? Update it with /plugin (the marketplace flow), not aidemo skill update.
  • Send feedback upstream: see step 3 above.
  • Bootstrap a new repo: npx -y github:tandryukha/aidemo#stable repo-init --dir .

When not to use it

  • When the user needs live screen-sharing
  • When the user needs to edit an already-rendered MP4
  • When creating demos for native or mobile apps (browser only)

Limitations

  • The skill does not support live screen-sharing
  • It cannot edit an already-rendered MP4
  • It is for browser-only demos, not native/mobile apps

How it compares

This skill automates the creation of polished, narrated product demo videos with browser action simulations, providing a structured approach to video generation rather than manual recording and editing.

Compared to similar skills

record-demo side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
record-demo (this skill)020dNo flagsIntermediate
narrator-ai-cli03moReviewIntermediate
video-report72moNo flagsBeginner
video-ai-direction01moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry