agent-video-pipeline

Orchestrates a local pipeline from approved narration scripts to rendered videos with captions, motion, and QC.

98|16|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/JayceHuang/agent-video-pipeline --skill agent-video-pipeline-jaycehuang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-video-pipeline
Source: https://github.com/JayceHuang/agent-video-pipeline
Command: npx skills add https://github.com/JayceHuang/agent-video-pipeline --skill agent-video-pipeline-jaycehuang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, soundfile, PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve? Turning an approved narration script into a finished explainer video requires coordinating TTS voiceover, forced caption alignment, visual assets, semantic motion planning, rendering, and quality gates; this Skill automates that entire local pipeline with reproducible, debuggable stages. ## Core Features & Use Cases - End-to-end video production: Converts an approved spoken-script JSON into timed audio, word-level captions, visual asset manifests, semantic motion plans, rendered video, and delivery packages with publishing copy. - Externalized configuration: Keeps voice assets, brand, CTA, canvas, and machine runtime in a workspace-level .agent-video/ config root, frozen per project via a resolved profile with SHA validation. - Quality gates and debugging: Enforces staged QC gates (audio boundaries, voice stability, layout occlusion, AV alignment) with a single run_gates.py entry point and a step-ordered debug checklist. - Use Case: A creator has a confirmed Chinese narration script and wants a subtitled, animated 1080p video with consistent cloned voice; the pipeline generates the master audio, aligns captions, plans motion, renders, and validates the final MP4. ## Quick Start Use agent-video-pipeline to process my approved narration script at /path/to/spoken-script.json in workspace /path/to/workspace with project directory /path/to/workspace/my-video, checking the external config and resolved profile first.

Frequently Asked Questions about agent-video-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a narration script into a finished video with this pipeline?▼

Initialize a workspace config root with init_config_root.py, freeze the project config via resolve_profile.py, then hand the approved spoken-script JSON to the pipeline. It produces audio, captions, motion plans, renders, and a delivery package with QC reports.

What tools are required to run this video pipeline locally?▼

You need Python 3.10 or higher, ffmpeg and ffprobe, and the Python packages in requirements.txt (numpy, soundfile, PyYAML). Animation rendering additionally needs Node.js with HyperFrames, and local TTS or avatar features need their respective tools.

Can I use my own voice clone or digital avatar with the pipeline?▼

Yes. Place reference voice files in .agent-video/assets/voice/ and avatar media in .agent-video/assets/avatar/, then configure the provider and paths in workspace.yaml. Avatar compositing itself is handled by the separate compose-avatar-video Skill.

Why does the pipeline stop with an error about missing .agent-video config?▼

The pipeline refuses to run without a valid centralized .agent-video/ config root containing profiles, runtime.local.yaml, projects, assets, and resolved directories. Run init_config_root.py against your workspace and re-freeze the project with resolve_profile.py.

How do I debug a failed video production stage?▼

Run scripts/run_gates.py --stage all to execute all machine-checkable gates, then fix only the failing layer. The references/debug-checklist.md file provides an ordered checklist from prosody approval through final AV alignment.

Does the pipeline support long articles instead of ready-made scripts?▼

Not directly. Long-form articles must first be converted into an approved narration script using the separate adapt-longform-for-speech Skill; the video pipeline only accepts confirmed spoken-script JSON input.