Capsule Cinema — скилл

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