Skip to content

oliverv/caro / .agents/skills/oma-video

oma-video

Unverified

Create short, explainer, or recorded-demo videos through the OMA video CLI. Use for scripts, narration, assets, composition, and video delivery.

resources/checklist.md

View on GitHub
# Checklist: before you run `oma video generate`

- [ ] Mode is set or inferable (shorts / explainer / demo) and the topic/source is clear (see `prompt-tips.md`).
- [ ] `--aspect` matches the mode (9:16 shorts, 16:9 explainer/demo) or is `auto`.
- [ ] Duration ≤ 180s and the script stays ≤ 40 scenes.
- [ ] `--out` is inside the project, or `--allow-external-out` is set.
- [ ] For `demo`: `--capture <path>` exists, is absolute + inside `$PWD`, and is a valid video format — or you accept the guided protocol.
- [ ] Provider readiness checked with `oma video doctor` (Node/Chromium/FFmpeg · Voicebox MCP · oma-image vendors · Pixelle-MCP · Cap).
- [ ] Paid visuals (Pexels / Pixelle) have their env key set, OR you accept the key-free oma-image fallback.
- [ ] Pixelle-MCP, if used: one-time explicit consent + source review done; `--max-usd` set for RunningHub credits.
- [ ] Estimated cost is acceptable. Run `--dry-run` first for unfamiliar combinations.
- [ ] Secrets are not in the brief, or `--no-brief-in-manifest` is set.

# Checklist: after the run

- [ ] The run directory contains `script.json`, `timing.json`, `render-spec.json`, `captions.srt`/`.vtt`, the `<mode>-<slug>.mp4`, and `manifest.json`.
- [ ] Every asset-bus schema validates (`schemaVersion: "1.0"`).
- [ ] `manifest.json` records each provider, asset `sha256` hashes, cost breakdown, and the exit code.
- [ ] `warnings[]` annotates any fallback taken (e.g. Pexels key absent -> oma-image stills, translator absent -> source locale).
- [ ] External assets were copied into the run dir and hashed (no URL refs).
- [ ] The mp4 has a video stream and positive duration (the CLI ffprobe check passed). A deterministic placeholder is valid only under `OMA_VIDEO_MOCK=1` tests and is never a deliverable.
- [ ] Re-rendering with `oma video render <runDir>` reproduces the same output from `render-spec.json`.
- [ ] If results are consumed downstream, the consumer parses the `--format json` stdout envelope `{exitCode, runDir, manifestPath, scriptPath, renderSpecPath, warnings, error}` (there is no `outputs` key) and reads output/asset paths from the manifest at `manifestPath`.
- [ ] Old run directories under `.agents/results/videos/` are pruned **manually** when no longer needed — every run adds a new dir and the CLI never auto-deletes them.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall