add-video-driver

Add and register new video drivers with a consistent BaseVideoDriver interface.

187|45|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/jeffstric/ZJT --skill add-video-driver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-video-driver
Source: https://github.com/jeffstric/ZJT/tree/main/.claude/skills/add-video-driver
Command: npx skills add https://github.com/jeffstric/ZJT --skill add-video-driver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

为在本项目中轻松新增、集成和注册视频生成驱动,解决对新 API 或供应商接入的重复实现工作。

Core Features & Use Cases

  • 提供从创建驱动实现到注册到驱动工厂的完整流程,包括配置加载、错误处理、单元测试和文档更新。
  • 支持添加 Happy Horse、Sora、Kling 等新驱动的示例与最佳实践。

Quick Start

创建并注册一个新的视频驱动(如 Happy Horse i2v),并运行单元测试以验证集成。

Frequently Asked Questions about add-video-driver

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

FAQPage Schema
How do I add a new video driver to an existing AI video generation project?

To add a new video driver, you need to implement the driver using a consistent BaseVideoDriver interface, register it within the driver factory, and update the project documentation to reflect the integration.

What is the standard process for registering a new video provider like Sora or Kling?

Registering a new video provider involves implementing the provider as a driver, dynamically loading its configuration, ensuring robust error handling, adding it to the driver factory, and verifying the setup with unit tests.

How does dynamic config loading work when integrating a new video generation API?

Dynamic config loading works by injecting the necessary API credentials and parameters during the driver instantiation phase, allowing the driver factory to seamlessly initialize new video providers without hardcoding values.

Do I need to write unit tests when implementing a custom video driver?

Yes, writing unit tests is required when implementing a custom video driver to verify the integration, ensure the driver adheres to the BaseVideoDriver interface, and validate that robust error handling functions correctly.

What's the best way to ensure a new video driver maintains a consistent interface?

The best way to maintain a consistent interface is to strictly inherit from the BaseVideoDriver interface, which standardizes method signatures across all video providers and ensures seamless integration within the driver factory.

Why does my newly registered video driver fail during dynamic config loading?

A newly registered video driver may fail during dynamic config loading due to missing API credentials or malformed configuration files, which the robust error handling mechanism should catch and report during unit tests.