Video Content Engine takes one grounded source, such as a URL, a file, a transcript or a recording, and works out the strongest justified portfolio of content from it. Without a production request it returns a brief with a source score, recommended modes, opportunity counts and the approval needed to begin.
When production is requested it covers edit maps, boundary audits, captions, packaging for each asset and a delivery folder checked by a validator script. It never publishes or schedules without explicit approval.
What You Get
- A diagnose-and-recommend brief with source score, editorial mode and first release wave
- A claim ledger, a rights ledger and a timestamped content-atom inventory
- Edit maps and boundary audits for long-form, mid-form and 15 to 90 second vertical assets
- Packaging for each asset: titles, thumbnails, hooks, covers, captions and calls to action
- A delivery folder with a manifest and a 24-hour, 72-hour and seven-day measurement plan
Common Use Cases
- Deciding how many clips and posts a recorded episode can support
- Planning a recut of a long video that opens weakly
- Checking claims and third-party media before a video is released
- Handing an editor a structured plan with timestamps and source mappings
What Makes It Unique
The skill refuses a fixed quota of derivatives. The opportunity inventory decides how many assets a source supports, and every asset needs its own promise and payoff. It separates technical integrity from editorial approval, so a passing validator never counts as a finished edit.
Under The Hood
The agent follows a long SKILL.md and reads reference files on routing, editing, quality gates and delivery as needed. It runs two Python validators from the shell, one for edit boundaries and one for the delivery folder, and may run the repository telemetry helpers described in the preamble, which log locally with opt-in remote reporting. It can fetch a supplied video URL or transcript, transcribe media and write files such as renders and manifests, but the package has no editor or render service of its own. Publishing, uploading and scheduling need your explicit approval.