Agent skill · creative production · hkuds
cli-hub-matrix-video-creation
Capability-based multi-tool matrix for video production. Agents pick providers (CLI-Anything harnesses, public CLIs, Python libs, native binaries, cloud APIs) per capability rather than marching through fixed stages, including storyboard planning, story/audio direction, source triage, internet video/music search/download, capture/generation, analysis, sound design, high-end caption design, NLE/render doctor investigation, review, and packaging.
Why this skill is useful
Adds a comprehensive capability-based matrix for video production that includes executable commands for installation and provider selection, enhancing the AI's ability to manage complex workflows.
What it needs
Requires cli-hub installed locally. About 12k tokens when loaded. Last updated 2026-08-03. 46,739 stars on the source repository.
What this skill does
Video Creation Matrix (v3 — capability-based) This matrix describes capabilities the agent can compose on demand — not a fixed pipeline. A "video creation" workflow picks a recipe (which capabilities it needs) and, per capability, picks a provider from the task requirements and preflight facts below. Schema: docs/cli-matrix/matrixregistry.schema.md. Install (installable portion) Not everything in this matrix is installed by cli-hub matrix install. Cloud APIs, Python packages, native binaries, third-party public CLIs, and external skills are first-class providers too, but install them only after the task actually needs that provider. Do not hand-write pip install ...#subdirectory=... for CLI-Anything matrix members; install the supported harnesses through cli-hub matrix install video-creation, then use preflight to see what else is already available. --- Provider selection constraints (agent: evaluate per capability) 1. Use preflight as an availability report, not as a provider selector. 2. Choose providers from the user's goal, quality bar, budget, offline needs, credential state, install cost, and requested workflow. 3. Treat registry/provider order as documentation order only; do not assume the first provider is the correct one. 4. Install Python libs, native binaries, harness CLIs, public CLIs, or agent skills only when they fit the task constraints. 5. Escalate to paid or metered APIs only when the user has supplied credentials or explicitly consents. Never silently call a paid API. 6. If a task falls into a genre with a mandatory provider rule, the provider is not optional. Do not substitute a cheaper/easier fallback just because it is locally convenient. Offline context? Filter to offline: true providers only. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills hkuds/video-creation