pixverse_upload_image

Upload an image to PixVerse via SeaCloud CLI and output a reusable img_id.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/SeaCloudAI/seacloud-cli --skill pixverse-upload-image
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pixverse_upload_image
Source: https://github.com/SeaCloudAI/seacloud-cli/tree/main/skills/video/pixverse_upload_image
Command: npx skills add https://github.com/SeaCloudAI/seacloud-cli --skill pixverse-upload-image

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Uploading and registering a source image to PixVerse to obtain a reusable img_id, enabling downstream video workflows without relying on raw image URLs.

Core Features & Use Cases

  • Generate a reusable img_id from a source image for PixVerse video tasks.
  • Serve as a preflight step before PixVerse image-to-video or transition generation.
  • Facilitate pipelines where subsequent PixVerse calls require img_id, first_frame_img, or last_frame_img.

Quick Start

Use pixverse_upload_image to generate an img_id from your source image prior to PixVerse video tasks.

Frequently Asked Questions about pixverse_upload_image

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

FAQPage Schema
How do I get an img_id for PixVerse image-to-video workflows?

To get an img_id for PixVerse workflows, you upload a source image via the SeaCloud CLI, which registers the image and outputs a reusable img_id for downstream video generation tasks.

What's the best way to prepare a first_frame_img for PixVerse video generation?

The best way to prepare a first_frame_img for PixVerse is uploading your source image to generate a reusable img_id, ensuring smooth handoffs for downstream video generation calls without relying on raw URLs.

Do I need to upload images to PixVerse before generating a video?

Yes, uploading images to PixVerse is a required preflight step before video generation, producing a reusable img_id that downstream workflows use for first_frame_img or last_frame_img inputs.

Can I use raw image URLs instead of an img_id for PixVerse CLI workflows?

No, PixVerse CLI workflows require a reusable img_id instead of raw image URLs, ensuring smooth handoffs between pipeline steps where subsequent calls expect img_id, first_frame_img, or last_frame_img.

Why does my PixVerse pipeline fail when passing a source image to video generation?

PixVerse pipelines fail when passing raw source images directly because downstream video generation calls require a preflight upload step to produce a reusable img_id for proper handoffs.

Does pixverse_upload_image support preflight validation before image-to-video generation?

Yes, pixverse_upload_image supports preflight validation before image-to-video generation by uploading the source image to PixVerse via SeaCloud CLI and outputting a validated img_id for downstream workflows.