Agent skill · vm0-ai
intro-video
Turn a prompt, a screen recording, or mixed source files into one verified intro-video MP4. Renders click-driven camera moves when a recording ships a .clicks.json sidecar, compiles the user's brief into a HeyGen Video Agent prompt on the Okou-managed native route by default, and switches to Okou-orchestrated composition only when the brief needs controls HeyGen cannot honor (no narration, original audio, exact pages, frames, timing, or verbatim script with exact timing).
What it needs
About 9k tokens when loaded.
What this skill does
Intro Video Deliver one playable, verified MP4 that communicates the user's idea. Three routes produce it: the Okou-managed HeyGen Video Agent authors a whole new video, okou video camera polishes a screen recording the user already made, and Okou composes the timeline itself when the brief needs control HeyGen cannot give. Use only Okou-managed commands and credits; the platform holds the provider credentials. Step 1 — Normalize the request into a brief The entry form sends free text, source files, and the user's Style / Avatar / Voice / Output format choices. It never asks for duration, language, intent, or CTA: resolve them in the brief and carry them into the prompt under its script-mode rules. Native verbatim mode uses the script-following directive in place of a numeric duration. Follow brief for the fields, the inference order, and the input adapters. Prompt-only requests are the fast path; for attachments, download once, probe cheaply, and inventory each file's role before any conversion. One attachment pair decides the route by itself: a video with a synchronized same-stem .clicks.json sidecar. Record it in the brief and read screen recording. Read this file and brief, then select the route before opening execution guidance. Each route has one execution reference: screen recording, native, or controlled composition; the native presenter compiler is not part of the other two paths. Native submissions also need prompt compiler, and recipes when its story arc helps the selected build. The rest have triggers: catalogs only when a choice is delegated, an exact ID needs a compatibility check, or the form gave no preview size for the selected look and crop risk still has to be computed — with all three supplied and the preview size on the form, query nothing; input preparation only with attachments; QA only after a job returns; provider boundaries only for a capability the route does not cover. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vm0-ai/intro-video