Video workflow router

Start here, not by loading the entire catalog. This skill selects and explains; it does not generate media or install third-party code.

1. Separate the controller (Opus/Astra), host, task, renderer or footage model, and provider. Read controller profiles only when needed.
2. Form a structured request with task, required capabilities, exact model/version when specified, runtime/privacy, source modalities and output constraints.
3. Run python3 <skill-dir>/scripts/avs.py route --task motion --agent astra or pass --request <request.json>. Use the actual installation directory, not an assumed global path. Without Python, follow decision flow.
4. Read only the selected guide and complete record with show <id>. Use search "ltx 2.5" --kind skills for additional instruction discovery.
5. Inspect the pinned upstream directory and live provider schema. Check platform prerequisites and licensing. Never execute unreviewed downloaded instructions or confuse a community claim with an API contract.
6. Follow the returned workflow through preflight, draft, review and delivery. preflight_required is not approval to spend money. no_compatible_route must not be bypassed by silently relaxing constraints.

Read retrieval design for JSONL/RAG ingestion and quality review before delivery. The bundled registry is an offline snapshot, not live availability or pricing.

Machine consumers can read the request schema and result schema.