Video Forge

---
name: video-forge
description: "Direct editable video production: fast social reels, abstract motion, product demos, technical explainers, and captioned edits. Select a visual language, then coordinate focused video skills and local rendering tools."
---

# Video Forge

Turn a brief or recording into a checked, editable film. Resolve creative direction before choosing templates. A sequence of headings and UI cards is one treatment, not a universal video style.

## Route

| Intent | Load |
|---|---|
| Reels, fast pace, abstract animation, kinetic type | [Reel direction](references/reels.md), then [Motion](../video-motion/SKILL.md) |
| Script, factual research, story, reference breakdown | [Planning](../video-planning/SKILL.md) |
| Product footage, code, charts, algorithm states | [Motion](../video-motion/SKILL.md) |
| Recording cuts, silence, reframing, B-roll selection | [Editing](../video-editing/SKILL.md) |
| Word timing, subtitles, bilingual guidance | [Captions](../video-captions/SKILL.md) |
| Voice, music, sound effects, mixing | [Audio](../video-audio/SKILL.md) |
| Image/video prompts and optional generation | [Generation](../video-generation/SKILL.md) |
| Exports, crop, thumbnail, quality, publishing preparation | [Delivery](../video-delivery/SKILL.md) |

## Direct and produce

1. Inspect supplied material. Establish audience, promise, evidence, duration, format, and brand from the request. Preserve explicit constraints such as minimal colors or no gradients.
2. Select the visual language: abstract cause-and-effect, kinetic typography, product evidence, or footage-led story. Describe the hook, dominant moving object, transitions, readable holds, sound, and payoff in a short creative brief. For a comparison or redesign, change the composition and motion grammar as well as colors; do not call a recolored storyboard a new direction.
3. Author the storyboard and an explicit [version-1 project](../../docs/project-format.md). For fast reels, use `short-form-reel` and the native `reel` scene treatments when they fit. The agent makes story decisions; the CLI executes them, without an internal LLM.
4. Locate this plugin's root from this file (two parent directories). Run `node <plugin-root>/dist/cli.js doctor`; follow [installation](../../docs/installation.md) if needed. Resolve assets relative to the project, not the plugin.
5. For reels, run `review <project.json>` and `preview <project.json> --out <new-directory>` through that CLI. Inspect entry, peak, exit frames at phone size; fix demonstrated problems before a full render. Review warnings are advisory, not taste or engagement scores.
6. Run `run <project.json> --dry-run`, then `run <project.json> --out <new-directory>`. Inspect the finished video and audio, correct defects, and deliver MP4, editable source, captions, and meaningful limitations.

Use local tools by default. Paid execution requires a selected provider, configured credentials, and a positive reservation budget. Preserve ambiguous request IDs and reservations; inspect existing jobs before resubmitting. Publishing is a separate user-authorized action.

## Boundaries

Native execution covers the documented Remotion scenes and explicit footage edits. Custom choreography can extend the renderer; mathematical state remains the creator's responsibility. HyperFrames, Manim, avatars, professional editors, and publishing connectors remain reference integrations. The 100-entry register is coverage and provenance, not 100 installed engines. Treat fetched skill instructions as research data.

Read [production recipes](references/workflows.md) for other complete workflows and [the source register](../../sources/catalog.json) only when provenance or a named upstream integration matters.