video-edit

Route natural-language video editing intents to RunComfy CLI model calls.

12|2|Updated May 18, 2026
One-click install
npx skills add https://github.com/runcomfy-com/skills --skill video-edit-runcomfy-com
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: video-edit
Source: https://github.com/runcomfy-com/skills/tree/main/video-edit
Command: npx skills add https://github.com/runcomfy-com/skills --skill video-edit-runcomfy-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Video editing from natural-language intent is slow and error-prone because selecting the right underlying model and prompting pattern is difficult, especially when the goal is restyling versus motion transfer.

Core Features & Use Cases

  • Intent-based model routing: Automatically chooses between three editing routes based on whether you need general restyle/background/packaging changes, motion control, or lightweight identity-stable restyling.
  • Model-specific input handling: Supports route-specific schemas like video vs video_url, reference_image, and motion-control orientation constraints.
  • RunComfy CLI execution: Executes the correct runcomfy run <vendor>/<model>/<endpoint> call and downloads results to your output directory.

Use case: You want to keep a talking-head’s face and lip movement while swapping the background to a modern office and preserving the original audio; the skill routes you to the best-fit edit model and applies the appropriate prompting structure.

Quick Start

Ask the agent to edit your video by preserving face and motion while changing the background to a modern office, and include your source video URL.

Frequently Asked Questions about video-edit

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

FAQPage Schema
How do I route natural language video editing intents to the right model?

Identity preservation in video restyling maintains a talking-head's face and lip movement while changing the background or outfit. The skill routes your request to a lightweight restyle model that enforces identity-stable constraints across character-edit scenarios.

How do I transfer motion from a reference clip to a target video?

Model-specific input handling for video editing enforces valid schema fields like video versus video_url and reference_image based on the routed model. It ensures your JSON inputs match the exact requirements of the selected restyle or motion-control endpoint.

Can I use RunComfy CLI to execute video restyle and background packaging edits?

Yes, you can use natural language to request a video edit, such as preserving face and motion while changing the background to a modern office. The skill parses your intent, routes it to the best-fit edit model, and applies the appropriate prompting structure automatically.

What are the limitations of automated intent routing for video edits?

Automated intent routing for video edits is limited to restyle, background packaging, motion transfer, and identity-stable outfit changes. It enforces model-specific constraints, meaning unsupported edit types or invalid schema fields will fail the RunComfy CLI invocation.