seedance-pipeline

Plans Seedance 2.0 API workflows, provider integrations, and post-production delivery pipelines.

40|6|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/LeoYeAI/seedance-skills --skill seedance-pipeline-leoyeai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seedance-pipeline
Source: https://github.com/LeoYeAI/seedance-skills/tree/main/skills/seedance-pipeline
Command: npx skills add https://github.com/LeoYeAI/seedance-skills --skill seedance-pipeline-leoyeai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams integrating Seedance 2.0 video generation face fragmented API surfaces across Volcengine, BytePlus, Runway, and third-party routers, with unclear model IDs, task lifecycles, and delivery requirements. This Skill provides sourced, up-to-date workflow guidance instead of stale assumptions. ## Core Features & Use Cases - API Workflow Planning: Covers task creation, polling, cancellation, file handling, and task ledgers across Volcengine, BytePlus, Runway, fal, and provider/router APIs like OpenRouter and PiAPI. - Surface & Model Mapping: Resolves Pro, Fast, V2, and wrapper model IDs, and distinguishes Dreamina/Jimeng web surfaces from China-facing and community (ComfyUI) workflows. - Professional Production Pipeline: Supports treatment, shot lists, continuity ledgers, post-production (editing, stitching, color, captions, localization), and delivery QC. - Use Case: A studio planning a batch of Seedance 2.0 clips via Runway asks for the correct model ID, upload rules, and a delivery checklist; the Skill returns the workflow path, source status, required inputs, and the next artifact to create. ## Quick Start Ask the agent to plan a Seedance 2.0 API integration workflow for your chosen provider, including model IDs, task lifecycle, and delivery QC steps.

Frequently Asked Questions about seedance-pipeline

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

FAQPage Schema
How do I integrate the Seedance 2.0 API into my application?▼

Plan the API workflow by selecting a provider (Volcengine, BytePlus, Runway, fal, or a router), confirming the model ID and auth method, then implementing task creation, polling, cancellation, and result retrieval. The Skill returns required inputs, validation steps, and risks for each provider.

What is the difference between Seedance on Runway and Volcengine?▼

Runway uses the model ID seedance2 with runway:// uploads, audio-reference combination rules, and plan or region caveats, while Volcengine and BytePlus follow the official ByteDance task lifecycle. Field names, pricing, and SDK support differ and should be rechecked per provider.

Can I use third-party router APIs like OpenRouter or PiAPI for Seedance?▼

Yes, but router providers such as EvoLink, OpenRouter, Kie.ai, PiAPI, and similar surfaces must be labeled provider-specific. Their docs, pricing, and model IDs should be rechecked before writing code or giving pricing guidance.

Are ComfyUI Seedance nodes officially supported?▼

ComfyUI and unofficial nodes are community workflows and must be labeled community or unverified unless backed by sourced documentation. Prefer official ByteDance, Volcengine, BytePlus, or Jimeng sources for production decisions.

What steps are needed before a Seedance video is delivery-ready?▼

A delivery-ready asset requires post-production steps such as editing, stitching, stabilization, audio cleanup, captions, color, and localization, followed by a delivery QC preflight. Professional jobs also need a continuity ledger, review packet, and reference rights map.