seedance-pipeline

Name: seedance-pipeline
Author: LeoYeAI

15stars2forks

How to install seedance-pipeline?

leoyeai/seedance-skills/seedance-pipeline

$npx -y skills add LeoYeAI/seedance-skills --skill seedance-pipeline

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# seedance-pipeline
2
3	Use this for operational workflows, APIs, web surfaces, post-production, and integration planning.
4
5	## Intent
6
7	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.
8
9	## Status Rule
10
11	Always load `[ref:api-status]` for current API and platform claims. Load `[ref:model-name-map]` when a user says Pro, Fast, V2, or a wrapper model ID. Do not rely on old release-status memory.
12	Load `[ref:api-workflow]` for implementation planning, task lifecycle, Runway/Volcengine/provider field differences, pricing caveats, upload handling, and production readiness.
13	Load `[ref:pro-filmmaking-standards]` for professional film, commercial, agency, localization, post, and delivery workflows. Load `[ref:delivery-qc]` before saying an asset is delivery-ready.
14
15	## Workflow Split
16
17	1. Web workflow: Dreamina/Jimeng surface, references, prompt, output review.
18	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.
19	3. Professional production workflow: treatment, shot list, continuity ledger, reference rights map, review loop, post handoff, and delivery/QC.
20	4. Post workflow: edit, conform, stitching, stabilization, audio cleanup, captions/subtitles, color, localization, versioning, textless, and delivery.
21	5. First/last-frame workflow: map first frame, last frame, transition action, identity locks, and ending target.
22	6. Runway workflow: model `seedance2`, `runway://` uploads, audio-reference combination rules, plan/region caveats, and SDK type lag are Runway-specific.
23	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.
24	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.
25	9. Community workflow: ComfyUI or unofficial nodes must be labeled community/unverified unless sourced.
26	10. Corpus-mining workflow: classify sources before reuse; extract structure and vocabulary, not unsafe raw prompts.
27
28	## Output Contract
29
30	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.

People who liked this also viewed

6 picks

Type

seedance-pipeline

15stars2forks

View on GitHub

How to install seedance-pipeline?

leoyeai/seedance-skills/seedance-pipeline

$npx -y skills add LeoYeAI/seedance-skills --skill seedance-pipeline

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# seedance-pipeline
2
3	Use this for operational workflows, APIs, web surfaces, post-production, and integration planning.
4
5	## Intent
6
7	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.
8
9	## Status Rule
10
11	Always load `[ref:api-status]` for current API and platform claims. Load `[ref:model-name-map]` when a user says Pro, Fast, V2, or a wrapper model ID. Do not rely on old release-status memory.
12	Load `[ref:api-workflow]` for implementation planning, task lifecycle, Runway/Volcengine/provider field differences, pricing caveats, upload handling, and production readiness.
13	Load `[ref:pro-filmmaking-standards]` for professional film, commercial, agency, localization, post, and delivery workflows. Load `[ref:delivery-qc]` before saying an asset is delivery-ready.
14
15	## Workflow Split
16
17	1. Web workflow: Dreamina/Jimeng surface, references, prompt, output review.
18	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.
19	3. Professional production workflow: treatment, shot list, continuity ledger, reference rights map, review loop, post handoff, and delivery/QC.
20	4. Post workflow: edit, conform, stitching, stabilization, audio cleanup, captions/subtitles, color, localization, versioning, textless, and delivery.
21	5. First/last-frame workflow: map first frame, last frame, transition action, identity locks, and ending target.
22	6. Runway workflow: model `seedance2`, `runway://` uploads, audio-reference combination rules, plan/region caveats, and SDK type lag are Runway-specific.
23	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.
24	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.
25	9. Community workflow: ComfyUI or unofficial nodes must be labeled community/unverified unless sourced.
26	10. Corpus-mining workflow: classify sources before reuse; extract structure and vocabulary, not unsafe raw prompts.
27
28	## Output Contract
29
30	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.

People who liked this also viewed

6 picks

Type