Skill

Route video production requests to the right pipeline

Skill that locks a video request to Generate, Compose, Edit, or AUTO before production starts, without producing media itself.


81
Spark score
out of 100
Updated 14 days ago
Version 15.12.0

Add to Favorites

Why it matters

Classify incoming video production requests and lock the correct execution path-generate AI footage, compose motion graphics, edit supplied media, or orchestrate an end-to-end multi-axis workflow-before any rendering begins.

Outcomes

What it gets done

01

Classify whether a video brief needs generated footage, HTML composition, editing of supplied media, or a cross-modal AUTO pipeline

02

Lock the primary production axis and aspect ratio based on the dominant work object in the request

03

Route explainer and animation requests to the Compose line with optional AI b-roll generation

04

Prepare unexecuted production packages with storyboards, scripts, and asset provenance when rendering is unavailable

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-video-router | bash

Overview

Video Router

A routing skill that classifies a video brief into one of three capability axes - Generate, Compose, or Edit - or an AUTO cross-modal route, and locks that choice before any production, generation, or editing work begins. Use it before any video-production task to pick and lock a route; not for actually generating, composing, editing, or rendering the video itself.

What it does

This skill decides and locks which video-production line a request should use before work begins - it's read for routing guidance and doesn't touch tool mechanics, media generation, editing, or rendering itself. It's an AAS-ready adaptation that preserves the routing rules from the official OrkasVideoStudio video-router skill at a pinned upstream commit, adding catalog metadata, examples, and limitations without bundling the OrkasVideoStudio runtime. It defines three orthogonal capability axes: Generate (A) for AI-generated footage/imagery, Compose (B) for deterministic HTML composition like explainers and motion graphics, and Edit (C) for intelligent editing of supplied footage. A request is classified by its dominant work object into one primary axis, or routed to AUTO end-to-end when the deliverable genuinely needs more than one axis woven together - AUTO still names a primary via the plan's delivery_promise (source_led/motion_led/compose_led/hybrid) and sequences the axes through one cross-modal plan (stage-plan builds the EDL, stage-assemble walks it).

When to use - and when NOT to

Use it before production whenever a request asks to make, compose, generate, edit, repurpose, or finish a video, or when a mixed brief needs one explicit primary path or an AUTO route. Do not use it to actually author compositions, generate assets, edit media, or render output - hand those off to the relevant production skill after the route is locked. Once a primary axis is locked, it should not be silently switched mid-run; if a later step reveals the wrong choice, surface it to the user and re-confirm.

Inputs and outputs

Input: a brief's topic, aspect ratio, language, and duration, plus, for supplied reference media, whether the relationship is reproduce, edit, or guide. Output: a locked primary route (Generate, Compose, or Edit) or an AUTO cross-modal plan with a named delivery promise, plus the target canvas derived from aspect ratio (16:9 to 1920x1080, 9:16 to 1080x1920, 1:1 to 1080x1080). If production or rendering tools are unavailable, it still returns a complete unexecuted production package - assumptions, script/narration, timed storyboard, exact copy and captions, visual/audio direction, asset provenance, export target, and a QA checklist.

Integrations

Adapts the upstream OrkasVideoStudio video-router skill pinned at commit dd4a0f40b2bc6c6b0fe6f2e732c9540ffffefe08, reviewed under the upstream MIT license, along with its stage-plan/stage-assemble workflow stage names, which require the user to separately install or supply a compatible OrkasVideoStudio runtime - this skill only routes and locks, it never executes generation, composition, or edit stages itself.

Who it's for

Teams and agents handling video requests that could span multiple production paths, who need one explicit, named route locked before any downstream generation, composition, or editing work starts.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.