Plan and produce video assets with ak:video

Use ak:video to move a marketing video from a brief to a production-ready script, a storyboard with frame assets, or a generated and assembled video pack. The Skill routes one of three subcommands and coordinates creative direction, scene prompts, audio directives, platform shape, review gates, and file output. It does not make generated media accurate, rights-cleared, or published by default.

Choose the stage you need

Use ak:video when

• You need a video script with scene, camera, visual, on-screen text, audio, and platform guidance.
• You need a storyboard from an approved script or bounded concept.
• You want to generate scene frames, video clips, voiceover, music, captions, or platform exports and can approve the required providers and tools.
• You have a clear goal, audience, platform, CTA, and authority boundary.

Choose another workflow when

• You only need a YouTube thumbnail. Use ak:youtube-thumbnail-design.
• You want to repurpose an existing YouTube source into other content. Use ak:youtube.
• You need only a voice or sound effect through ElevenLabs. Use ak:elevenlabs.
• You do not yet have permission for the scripts, source media, likenesses, voices, music, product claims, or provider processing the run would require.

Prepare the production route

Every route should have a goal, audience, platform, target length, CTA, and approved brand or claim constraints. The create route also needs the tools and services required by the selected production plan:

• GEMINI_API_KEY and network access for Gemini frame, analysis, speech, or Veo requests used by the packaged workflow.
• Python packages google-genai, python-dotenv, and pillow when the multimodal path requires them.
• Node.js and permission to run the pinned package command npx -y -p @mrgoonie/multix@0.2.0 multix. If the package is not cached, this can download and execute external code.
• ffmpeg when clips or audio layers will be assembled or exported.
• Any additional provider account, credential, quota, billing, or licensing needed for generated music, voice, or other media selected by the plan.
• A writable project and enough storage for PNG, WAV, MP4, SRT, Markdown, and JSON artifacts.

Read Runtime adapters before assuming the same production surface everywhere.

Run the Skill

Put the routed stage first. This example asks for a script pack only, so it creates planning artifacts without authorizing generation or publication.

/ak:video script-create reel "A 30-second product walkthrough for privacy-conscious analytics teams" Audience: technical founders. CTA: review the local demo. Use only approved product claims. Create the script pack only; do not generate media or publish

/ak:video script-create reel "A 30-second product walkthrough for privacy-conscious analytics teams" Audience: technical founders. CTA: review the local demo. Use only approved product claims. Create the script pack only; do not generate media or publish

$ak:video script-create reel "A 30-second product walkthrough for privacy-conscious analytics teams" Audience: technical founders. CTA: review the local demo. Use only approved product claims. Create the script pack only; do not generate media or publish

Select the routed stage

create detects whether a path looks like a script or storyboard and starts at that stage. A text prompt starts earlier. Confirm the detected route before a provider call or file creation begins.

Follow the production stages

1. Confirm the brief. The Skill resolves platform, aspect ratio, goal, audience, CTA, length, claims, art direction, rights, and stopping point.
2. Create or load the script. script-create produces the video brief, scenes, prompts, on-screen text, audio direction, platform pack, evaluation, and unresolved decisions.
3. Create or load the storyboard. storyboard-create turns scenes into machine-readable data, start/end frame prompts, motion, audio, timing, and optional character portraits and frame images.
4. Generate approved media. The full route can request frame images, voiceover, music, sound effects, and Veo clips. The packaged Veo wrapper uses model ID veo-3.1-generate-preview and supports 16:9, 9:16, or 1:1 production shapes through the workflow.
5. Assemble and export. FFmpeg can concatenate clips, join voiceovers, mix music, and create master.mp4; optional helpers can produce platform exports and captions.srt.
6. Review the evidence. Inspect continuity, text, claims, likenesses, intelligibility, audio levels, captions, rights, aspect ratio, and reported failures before any publishing decision.

Keep generation, spend, and publishing gated

Obtain rights and consent for every script, logo, product image, actor, face, voice, recording, music track, sound effect, and reference frame. Do not clone or simulate a person without authorization. Verify testimonials, comparisons, performance statements, and product demonstrations against approved evidence.

Review outputs and evidence

A full production can create:

content/video/{type}/{date}-{slug}/script.md
assets/storyboards/{date}-{slug}/storyboard.md
assets/storyboards/{date}-{slug}/storyboard.json
assets/storyboards/{date}-{slug}/scene-01-start.png
assets/storyboards/{date}-{slug}/scene-01-end.png
assets/videos/{date}-{slug}/scene-01.mp4
assets/videos/{date}-{slug}/voiceover-scene-01.wav
assets/videos/{date}-{slug}/music.wav
assets/videos/{date}-{slug}/master.mp4
assets/videos/{date}-{slug}/captions.srt
assets/videos/{date}-{slug}/analysis-marketing.md

Not every route creates every file. The final report should name the actual artifacts, provider requests and failures, generation settings, review findings, source and consent records, skipped stages, and external actions still pending. Inspect the media itself; a path or automated analysis is not proof that timing, continuity, speech, text, or claims are correct.

Troubleshoot safely

Continue with the Marketing Kit overview, Projects, artifacts, and checkpoints, or Installing kits.

Know the current limits

• The public router exposes create, script-create, and storyboard-create; helper scripts are implementation support, not additional Skill subcommands.
• Model IDs, resolutions, API behavior, quotas, safety filters, billing, and provider availability can change independently of the packaged workflow.
• Generated frames can drift between scenes; speech, music, captions, and audio mixing can contain artifacts or timing errors.
• A generated or reviewed video is not automatically licensed, accessible, truthful, platform-compliant, or ready to publish.
• Platform dimensions, duration limits, metadata rules, and posting guidance can change. Verify current requirements at distribution time.
• The workflow does not guarantee watch time, ranking, engagement, conversion, revenue, production quality, or provider acceptance.