oma-video

# Video Router ## Scheduling ### When to use Use this skill for a short/reel, README or code explainer, or demo walkthrough. | Request | Mode | Default aspect | Required source | |---|---|---|---| | Short, reel, social clip | `shorts` | `9:16` | Topic or brief | | README, code, data explanation | `explainer` | `16:9` | Topic or source path | | Demo or walkthrough | `demo` | `16:9` | Human recording via `--capture` | ### When NOT to use Use `oma-image` for a still image, `oma-slide` for a deck, `oma-voice` for audio only, and `oma-explanation` for an interactive HTML explainer. Editing an existing finished video and live streaming are out of scope. ## Structural Flow Inputs are a brief plus optional mode, aspect, locale, captions, visual, voice, music, duration, compositor, capture path, and seed. Outputs live in `.agents/results/videos/<timestamp>-<shortid>-<mode>/`: - `script.json`, `timing.json`, and `render-spec.json` form the deterministic asset bus. - Captions and acquired audio/visual assets are recorded in `manifest.json` with hashes, providers, cost, warnings, and exit code. - A successful real render contains `<mode>-<slug>.mp4`, an encoded video stream, and a positive ffprobe duration. `OMA_VIDEO_MOCK=1` is a test harness only. It can create deterministic text placeholders with an `.mp4` name; those files are never a user deliverable. A missing Remotion/MPT toolchain, an un-authored composition, a render error, or an invalid video fails with diagnost...