skill-video-studio README

The project's README from github.com/aaitor/skill-video-studio. As one markdown file: README.md.

Video Studio Skill — from product workflow to polished demo

Video Studio Skill

From product workflow to polished demo.

v1.0.1 release · aaitor/skill-video-studio

Quick start · Worked videos · Usage · Contribute

MIT license Offline source and documentation checks

A local video-production workspace driven by the /devrel-video Claude Code skill. Capture real product interactions with Playwright CLI, compose title cards, chapters, and CTAs with HyperFrames, then master and inspect the result with FFmpeg. Start with a silent walkthrough; add narration, music, subtitles, or your own presenter footage when needed.

Demo

Install Video Studio Skill and prepare a real walkthrough brief in Claude Code

A real Claude Code session using the installed project skill: clone the studio, prepare an Acme walkthrough brief, and inspect the three-beat plan on a black background. This short demo stops before capture and rendering; it does not claim a video was produced. The recording guide includes the actual generated brief and reproduction command.

Quick start

For planning: Git and authenticated Claude Code. Clone the full workspace so its native skill and project layout stay together:

git clone https://github.com/aaitor/skill-video-studio.git
cd skill-video-studio
claude

Ask Claude:

/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.

Expected result: a project brief and a concrete beat plan. For a complete video, install the capture/render prerequisites and follow the worked walkthrough. The production stack needs Node.js 22+, FFmpeg/ffprobe, Chromium, and the helper-specific Python dependencies. Optional narration and avatars require your own additional services or GPU setup.

Features

Portrait/social output profiles remain on the roadmap. Full capture/render depends on your local toolchain; offline CI checks sources and selected local utilities, not the complete production stack. See workflow and usage.

Worked videos

Product walkthrough: a local Acme fixture, real browser capture, narration/music, and EN/ES subtitles. Source and commands · Watch with sound.

Acme product walkthrough

Composed CLI/browser film: a multi-environment example whose terminal scenes are authored HTML reenactments. Source and explanation · Watch with sound.

Composed terminal and browser example

The longer examples remain intact. Generated MP4/audio files are ignored; rebuild them from the included sources. See usage prompts for silent, narrated, avatar, voice-swap, and multi-environment requests.

Configuration

Each video uses projects/<slug>/brief.yaml, brand tokens under brands/<name>/, and generated output under its project folder. Optional private settings live outside Git, selected by DEVREL_VIDEO_ENV.

Setting Purpose
brief.yaml Product URL, audience, message, beats, brand, duration, and optional layers
ORPHEUS_URL / ORPHEUS_KEY Your optional narration endpoint and token
AVATAR_HOST / LS_DIR Your optional SSH GPU host and LatentSync checkout
BGM_STYLE Local background-music style; default corporate

See configuration, the actual brief template, and security/privacy guidance. Keep private footage and credentials outside this public repository.

How it works

Brief → explore → brand → capture → compose → optional layers → render/QA → thumbnail. The skill coordinates existing tools rather than replacing them. Detailed production steps are in the workflow guide and production notes.

Repository layout

.claude/skills/devrel-video/  Skill instructions, scripts, templates, production notes
brands/                     Brand tokens and logos
projects/                   Curated public examples; private projects stay ignored
examples/                   Real harness recording, public input, generated brief
assets/                     Shared banner, social card, and short terminal GIF
docs/                       Onboarding, usage, configuration, troubleshooting

Documentation

Contributing and support

Use Issues for questions, bugs, and ideas. Read CONTRIBUTING.md and CODE_OF_CONDUCT.md; report vulnerabilities privately through SECURITY.md.

Install requirements-dev.txt in a virtual environment and run python3 scripts/check.py. See CHANGELOG.md for changes. Live recordings, service calls, GPU jobs, and full renders are manual validation steps.

License

MIT for original studio content. Embedded banner fonts retain their OFL notices; external tools/models/media retain their own terms. See licensing.

Built by Aitor Argomaniz · LinkedIn · More open source

skill-video-studio (aaitor/skill-video-studio)

Searching Database…

333 ·GitHub
Skill-video-studio
What is this?A local video-production workspace for product demos, driven by the /devrel-video Claude Code skill. It records real browser interactions with Playwright, composes title cards and CTAs with HyperFrames, and masters the output with FFmpeg.
Is it a standalone app or a skill for Claude Code?It is a Claude Code skill inside a cloned workspace, so you ask Claude for a video from a brief instead of launching a separate program. It coordinates existing tools rather than replacing them.
Can I try it without installing the whole toolchain?Yes, for planning you only need Git and an authenticated Claude Code. Clone the workspace and ask Claude for a brief, and you get a project brief and a concrete beat plan, not a finished video.
What do I need for a complete video?Node.js 22+, FFmpeg with ffprobe, Chromium, and the Python dependencies of its helper scripts. Narration and avatars are optional and need extra services or a GPU setup.
Is there anything it can't do yet?Portrait and social-media output profiles are still on the roadmap. Full capture and rendering depend on your local toolchain, and offline CI only checks sources and selected utilities.
Where do my footage and credentials stay?Private footage and credentials are meant to stay outside the public repository. Optional private settings live outside Git and are selected through an environment variable.
Does it record the real product or fake the UI?It drives the product in a browser through Playwright CLI, using scripts with explicit beats and stable selectors, so the captures are real. Only the terminal scenes in one example are authored HTML reenactments.
What do the two worked examples show?One is a narrated EN/ES product walkthrough built on a local Acme fixture. The other is a multi-environment CLI and browser film. Generated MP4 and audio files are not in the repo, so you rebuild them from the included sources.
Can I reuse my own brand and presenter footage?Yes. Brands are reusable tokens under the brands folder, and presenter footage can be private bring-your-own media kept outside the repository.
How much of it can be checked automatically?Offline CI checks the sources and selected local utilities. Live recordings, service calls, GPU jobs and full renders are manual validation steps.
What are similar projects?herk-edit-kit, saas-motion-kit, procedural-film, motion-video-kit, mortiflix-oss, guizang-product-video-skill, onetake, creator-flow
Which topics is it in?video-production, video-editing, claude-code-skill, playwright, content-creation, harness, workflow, ffmpeg, browser-automation, video, developers, html
Creator
aaitor
Size
9.1 MB
Stars
333
Updated
CommitNov 02Releasev1.0.1Nov 02
Age
2mo
Commits · 90 Days