Skywork AI Skyreels V3 Extend Video (Official Edition)

You finally got a 5-second clip that doesn't melt into goo. The obvious move is to loop it and call it a video - but loops read as loops, and Skywork's Skyreels V3 Extend node is the honest alternative: it watches the clip you feed it and keeps the story going forward instead of repeating it.

What this node does

BizyTRD_Skyreels_Official_VExtend_Video_Extend_API is the "Extend Video" member of the Skyreels family in BizyAirPlus. It takes an existing video as its start, reads the motion and composition, and generates a continuation - a new segment that flows out of the last frames rather than a copy of them. That's the difference between a music-video background loop and a take you can actually edit into a scene.

It's a cloud node, which is the whole point: the generation runs on BizyAir's servers, not your GPU. You build the workflow locally, flip the BizyAirPlus button ON, and this node uploads your clip, does the work remotely, and hands the result back. Zero VRAM, zero checkpoint downloads, zero "why does my 8GB card cry" threads.

The inputs that matter

• prefix_video - the clip to extend. This is the whole job; feed it the take you're happy with.
• prompt - what happens next. Skyreels reads the first clip, and your text steers the direction: new camera move, the subject walking out of frame, whatever.
• duration - 5 to 30 seconds (default 5). This is the generous one in the family; most Skyreels nodes cap out at 15s, but extension can run longer.

Notice what's not here: no resolution, no aspect ratio. The extension keeps the source video's framing, so there's one less thing to screw up.

Every BizyAir node also ships two optional inputs worth knowing. api_config lets you override the base URL and API key for a single request (handy if you're testing against a different endpoint), and skip_error makes the node emit an error placeholder instead of killing your whole workflow when a cloud call fails.

Outputs

• video - the finished extended clip. This is an output node, so wire it straight into a video preview or save node.
• request_id - the cloud task ID. Grab it if you ever open a support ticket.
• urls - the hosted URLs for the result, in case you want the file directly.

How to install

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAirPlus.git
cd BizyAirPlus
python -m pip install -r requirements.txt

Restart ComfyUI (or install the "BizyAirPlus" pack through ComfyUI Manager). Dependencies are bizyair-cloudberry and bizytrd - no model files, nothing heavy. First run: create an account at bizyair.ai, grab an API key, and enter it when the button prompts you (or Settings > BizyAirPlus > API Key; it's saved to ~/.BizyAirPlus/apikey.ini).

Where people get burned

The #1 gotcha isn't technical, it's trust: in mid-2025 ComfyUI Manager had a bug that auto-installed BizyAir for unrelated workflows (Nunchaku especially), and a chunk of Reddit still treats it as malware. It's a legitimate SiliconFlow pack. If you did install it by accident, don't just delete the folder - pip uninstall bizyair-cloudberry bizytrd in the same Python environment ComfyUI uses, or the packages linger in your venv.

The other one: if the BizyAirPlus button is missing entirely, your dependencies went into the wrong Python. Install with the same environment that runs ComfyUI, restart, and check with python -m pip show bizyair-cloudberry.