# Seedance Pipeline

> This skill should be used when the user asks about Seedance 2.0 workflow operations, API planning, BytePlus ModelArk, Dreamina/Jimeng surfaces, provider/router APIs, China-facing surfaces, ComfyUI, post-production, stitching, batch workflow, or integration planning.

- Skill: `emily2040/seedance-pipeline` (Agent Skill)
- Install (CLI): `npx skillmds@latest add emily2040/seedance-pipeline`
- Raw SKILL.md: https://api.skillmd.com/api/skills/emily2040/seedance-pipeline/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: emily2040 (https://skillmd.com/u/emily2040)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/emily2040/seedance-pipeline

---


# seedance-pipeline

Use this for operational workflows, APIs, web surfaces, post-production, and integration planning.

## Intent

Behind every API question is a person with a deadline, a budget, and something at stake on this working tomorrow. The soul of this skill is being the one voice in the room that answers with dates, sources, and a path instead of optimism. Reliability is the kindness this user needs.

## Status Rule

Always load [api-status](../../references/api-status.md) for current API and platform claims. Load [model-name-map](../../references/model-name-map.md) when a user says Pro, Fast, V2, or a wrapper model ID. Do not rely on old release-status memory.
Load [api-workflow](../../references/api-workflow.md) for implementation planning, task lifecycle, Runway/Volcengine/provider field differences, pricing caveats, upload handling, and production readiness.
Load [pro-filmmaking-standards](../../references/pro-filmmaking-standards.md) for professional film, commercial, agency, localization, post, and delivery workflows. Load [delivery-qc](../../references/delivery-qc.md) before saying an asset is delivery-ready.

## Workflow Split

1. Web workflow: Dreamina/Jimeng surface, references, prompt, output review.
2. API workflow: Volcengine, BytePlus, Runway, fal, or provider/router docs, model ID, auth, file handling, task creation, polling/querying, cancellation/deletion, task ledger, and retrieval.
3. Professional production workflow: treatment, shot list, continuity ledger, reference rights map, review loop, post handoff, and delivery/QC.
4. Post workflow: edit, conform, stitching, stabilization, audio cleanup, captions/subtitles, color, localization, versioning, textless, and delivery.
5. First/last-frame workflow: map first frame, last frame, transition action, identity locks, and ending target.
6. Runway workflow: model `seedance2`, `runway://` uploads, audio-reference combination rules, plan/region caveats, and SDK type lag are Runway-specific.
7. Provider/router workflow: EvoLink, OpenRouter, Kie.ai, PiAPI, LaoZhang, Runware, ModelsLab, AI/ML API, MuAPI, SeeGen, Segmind, or similar surfaces must be labeled provider-specific and rechecked before code or pricing guidance.
8. China-facing workflow: prefer official ByteDance/Volcengine/BytePlus/Doubao/Jimeng/Jianying sources; workflow hosts, Chinese-language blogs, and business-partner news are not public API providers without provider-owned docs.
9. Community workflow: ComfyUI or unofficial nodes must be labeled community/unverified unless sourced.
10. Corpus-mining workflow: classify sources before reuse; extract structure and vocabulary, not unsafe raw prompts.

## Output Contract

Return the workflow path, source status, required inputs, production phase, validation steps, delivery assumptions, and risks. For professional jobs, include the next artifact to create: brief, shot list, continuity ledger, prompt batch, review packet, localization matrix, or QC preflight.