skill-video-studio adds a Claude Code skill for product demo videos
skill-video-studio is an open-source, local video-production workspace published on GitHub by Aitor Argomaniz as aaitor/skill-video-studio, currently at release v1.0.1. It is driven by a Claude Code skill called /devrel-video. Per the README, the idea is to capture real product interactions with Playwright CLI, compose title cards, chapters and calls to action with HyperFrames, then master and inspect the result with FFmpeg. The README says the skill coordinates existing tools rather than replacing them.
The suggested path is to start with a silent walkthrough and add narration, music, subtitles or your own presenter footage when needed. The pipeline is laid out as: brief, explore, brand, capture, compose, optional layers, render and QA, thumbnail. Each video lives in projects/
Getting started for planning only needs Git and an authenticated Claude Code. You clone the full workspace, so the native skill and project layout stay together, run claude, and ask for something like: /devrel-video Prepare a 25-second silent walkthrough brief for the bundled Acme app: show the workspace, filter by category, then open a project. Reuse brands/acme. Show the plan before capture or rendering. The expected result is a project brief and a concrete beat plan, not a video. The README's short demo recording shows a real Claude Code session doing exactly this, ending on a three-beat plan, and it states that the demo stops before capture and rendering and does not claim a video was produced.
For a complete video, the production stack needs Node.js 22+, FFmpeg and ffprobe, Chromium and helper-specific Python dependencies. The listed features are: real product capture through browser interaction scripts with explicit beats and stable selectors; branded composition (title, browser frame, chapters and CTA) in a HyperFrames timeline; local mastering and QA, with master and web copies, ffprobe checks, a contact sheet and a thumbnail; an optional audio layer with six local music styles, narration-driven timing and voice variants; optional subtitles, private bring-your-own presenter footage and terminal/browser sequences; and a source-based setup with reusable brands, briefs and templates plus two complete worked examples.
The two worked examples are a product walkthrough (a local Acme fixture, real browser capture, narration and music, with English and Spanish subtitles) and a composed CLI/browser film, a multi-environment example whose terminal scenes are authored HTML reenactments. Generated MP4 and audio files are ignored by Git, so they must be rebuilt from the included sources. Portrait and social output profiles remain on the roadmap.
The repository is organised into the skill itself under .claude/skills/devrel-video/ (instructions, scripts, templates, production notes), plus brands, projects, examples, assets and docs folders. The code is MIT-licensed for original studio content; embedded banner fonts keep their OFL notices, and external tools, models and media keep their own terms. Contributions go through Issues and CONTRIBUTING.md, and vulnerabilities are reported privately through SECURITY.md.
Key facts
- skill-video-studio (v1.0.1, by Aitor Argomaniz) is a local workspace driven by the /devrel-video Claude Code skill.
- It captures product interactions with Playwright CLI, composes title cards, chapters and CTAs in HyperFrames, and masters and checks output with FFmpeg.
- Planning needs only Git and authenticated Claude Code; a full video needs Node.js 22+, FFmpeg/ffprobe, Chromium and Python helper dependencies.
- Optional layers include six local music styles, narration, subtitles and presenter footage; two complete worked examples are included.
- Portrait/social output profiles are still on the roadmap, and the code is MIT-licensed for original studio content.
Why it matters
Product demo videos usually mean stitching together screen capture, motion graphics and encoding by hand. This project packages that chain as a Claude Code skill, so a brief and a beat plan can be requested in plain language before any capture or rendering happens. It is a workflow that coordinates Playwright CLI, HyperFrames and FFmpeg rather than a new video engine, which is how the README describes it.
Who it affects
Developers and developer-relations teams who want walkthrough videos of their own product and already use Claude Code. The skill name, /devrel-video, points at that audience. Anyone adding narration or avatars should expect to bring their own additional services or GPU setup.
How to use it
Clone https://github.com/aaitor/skill-video-studio.git, enter the folder and start claude, so the project skill is picked up. Then ask for a brief, for example a 25-second silent walkthrough of the bundled Acme app that reuses brands/acme and shows the plan before capture or rendering. For a finished video, install Node.js 22+, FFmpeg/ffprobe, Chromium and the Python helper dependencies, then follow the worked walkthrough. Each video gets a projects/
How solid is it
The facts here come from the project's own README, which describes a v1.0.1 release. It includes two worked examples, a recorded Claude Code session and CI. Offline CI checks sources and selected local utilities, not the complete production stack, and live recordings, service calls, GPU jobs and full renders are manual validation steps. No usage numbers, stars, adopters or benchmarks (render time, quality, cost) are given.
Risks and caveats
The short demo stops before capture and rendering and does not claim a video was produced, so it shows planning only. A full capture and render depends on your local toolchain. Narration and avatars need extra services or GPU setup of your own. Generated MP4 and audio files are not stored in Git and must be rebuilt from sources. Portrait and social formats are not yet available. External tools, models and media keep their own licence terms, and private footage and credentials should stay outside the public repository.
“The skill coordinates existing tools rather than replacing them.”
— skill-video-studio README