Capsule Cinema skill
A short video studio skill: series recipes with storyboards, generation channels, quality gates and shot-level rework
- 235 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The skill runs FFmpeg and scripts in the workspace and calls paid generation APIs with your keys
- Generation channels spend money from your keys on every generation
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/capsule-cinemaDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skill runs FFmpeg and scripts in the workspace and calls paid generation APIs with your keys
- Generation channels spend money from your keys on every generation
This is third-party code. Review the repository files before installing.
What it does
Capsule Cinema installs into a coding agent and turns a series of short videos into a portable recipe: show structure, storyboard rules, generation channels, quality gates and rework experience. For the next episode you change the topic and materials while the process stays the same. It is not a button-style website or a source of compute: everything runs in your agent and a local workspace, and media is generated through your own keys. The repository ships ready recipes: an industry workflow explainer, a plush diorama science clip, a life-simulator story, a product showcase, art animation, felt ASMR, Chinese history, growth cards, a GitHub repository showcase and a music video. A storyboard can be reviewed before generation, a failed shot is redone on its own, and a quality check runs before release. Channels attach by capability: Seedream, Seedance, Agnes, MiniMax, Doubao voice, RunningHub and local FFmpeg. The first video needs no API key.
Who it is for. Creators and teams who run short video series, columns or product clips and want to repeat the process without rebuilding it.
Good fit when
- A clip series comes out weekly and structure, voice and shot rules must repeat
- You need a clip showcasing a GitHub repository or an agent skill from real screenshots
- The storyboard is reviewed before generation and a failed shot is redone separately
- The process moves between models: a recipe is built once and repeated on others
Not a fit when
- You want a one-button web generator: the project runs inside your agent
- You have no Python 3.12 and FFmpeg and the agent cannot install them
- You need compute: the project provides none and uses your APIs
Example request
Use Capsule Cinema and make a 15-second clip with the product showcase recipe; show the storyboard firstLimitations
Python 3.12 and FFmpeg are required; project showcase clips also need a browser that takes screenshots. Paid channels (Seedream, Seedance, MiniMax, Doubao voice, RunningHub) need your own keys and spend your budget, and free-tier terms change, so confirm them with the provider. Recipes target Chinese short video, other markets need adjustment. After installation the agent must be fully restarted or it will not see the skill.
How to disable. Delete the capsule-cinema skill folder from the agent's skills directory and restart the agent. Finished videos and recipe files stay in your workspace.
FAQ
Do I need API keys for the first video?
No. The first trial runs without keys; keys are needed when you want AI images, video or voice. The self-check reads only whether variables are set and calls no paid API.
What is a recipe in Capsule Cinema?
A package of show structure, storyboard rules, declared channel capabilities, checks and rework experience. For a new episode you change topic and materials.
Which agents work?
Any agent with Skills support: Codex, Claude Code, OpenClaw, Cursor, Trae, Hermes Agent and others. The agent installs it from the docs/install.md instruction.
How do I redo one bad shot?
Tell the agent which shot failed: the project keeps intermediate results per step and rebuilds only that one without spending budget on the rest.
Which generation channels are supported?
Images via Seedream and Agnes, video via Seedance, MiniMax H3 and Agnes, voice via Doubao and MiniMax, motion and lip transfer via RunningHub, and editing and QA locally via FFmpeg.
Discussion
No questions or reviews yet.
Related
SkillsA Claude Code skill that turns one sentence into a vertical AI micro-drama, from script and storyboard to video
A local short-video studio: topic, script, CC0 images, voice-over and MP4 with subtitles, driven by Claude Code or Codex
A local video studio for your coding agent: describe a video in one sentence, the agent directs, your machine renders with no cloud
An agent edits short talking-head videos: transcript, subtitles, B-roll and export for Xiaohongshu, Douyin and WeChat Channels
The agent writes the script, renders every frame in code with headless Chrome and returns an MP4: shorts, ads, explainers.
Skills for faceless video channels: one topic becomes a video with voiceover, subtitles, covers and per-platform copy.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Capsule Cinema (this card) | no | 235 | |
| Video Production Skills | no | 710 | a toolkit for assembling video, while Capsule Cinema has series recipes and shot-level rework |
| HyperFrames | no | 83,283 | renders video from HTML, while Capsule Cinema runs a series from storyboard to QA |
README in short
The README, in Chinese with an English version, covers the recipe idea, a three-step quick start, a stuck section, cross-model run records, built-in recipes, quality gates with targeted rework, connecting your own generation channels and the community.
README badge
Original SKILL.md
---
name: capsule-cinema
description: Plan, generate, revise, assemble, and quality-check local AI short videos with reusable Capsule Cinema recipes. Use when the user asks to make a video, design a storyboard, generate scenes, voiceover, subtitles or BGM, reproduce a reference-video workflow, repair a failed scene, review a release, or create, update, package, install, and reuse a video capsule.
---
# Capsule Cinema
Use Capsule Cinema as a recipe-driven local video studio. Keep planning, generation, targeted rework, assembly, QA, and reusable production knowledge auditable in one workspace.
## Resolve the runtime
Resolve the runtime before reading references or running commands:
1. If `{baseDir}/scripts/capsule.py` exists, use `{baseDir}` as `CAPSULE_CINEMA_ROOT`. This is a standalone Codex, Claude Code, or OpenClaw installation.
2. Otherwise, if `{baseDir}/../../scripts/capsule.py` exists, normalize `{baseDir}/../..` and use it as `CAPSULE_CINEMA_ROOT`. This is an OpenClaw plugin or source checkout.
3. Otherwise run `bash {baseDir}/scripts/bootstrap-runtime.sh`. Use the absolute path printed on stdout as `CAPSULE_CINEMA_ROOT`. The bootstrap clones the public runtime into the installed skill without reading or moving credentials.
4. Change to `CAPSULE_CINEMA_ROOT` before using relative paths in this skill.
If the runtime was just cloned, verify the prerequisites and install Python dependencies before production:
```bash
python3.12 --version
python3.12 -m pip install -r lib/requirements.txt
PYTHONPATH=lib python3.12 scripts/capsule.py list
```
FFmpeg is optional for recipe browsing and storyboard-only work, but required before rendering, audio mixing, subtitle burn-in, or final assembly.
## Orient a new user
Run `python3.12 scripts/quickstart.py` when the skill was just installed, when the user asks how to start, what they can make, or what is missing, and when a run stops on a missing prerequisite or credential. It reports the runtime, whether a browser for page capture was detected, which providers are configured, which starter routes are open, and a ready-to-send prompt for each. It checks only whether a variable is set and calls no paid API. Add `--lang en` for English output or `--json` for structured output.
Relay the result in the user's language as a short answer: what works now, the one cheapest next step, and the prompt to send. Do not paste raw JSON or the full capsule catalog. With no generation credentials, offer the `repo_signal_grid` project showcase or a storyboard-only run instead of asking the user to configure providers first. The showcase needs real browser captures: use your own browser tool when you have one, otherwise run `npx playwright install chromium` and capture with Playwright.
## Route the request
Read `references/production-guide.md` before planning or generating media. Use it to route to the narrower references for storyboard craft, production patterns, channel policy, tool recipes, capsule packages, assembly pitfalls, review gates, and workflow artifacts.
Classify the request before choosing tools:
- New AI video or storyboard
- Post-production or assembly from local media
- Reference-video analysis or remake
- Existing capsule production
- Targeted scene, voice, subtitle, BGM, or assembly repair