Seedance 2.0 Video
Writes and troubleshoots Seedance 2.0 video prompts across many surfaces.
Install
npx skills add Emily2040/seedance-2.0 --skill seedance-20 -g -a claude-code -y- Repository
- Emily2040/seedance-2.08k
- Category
- Media
- Updated
- 1mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
This skill should be used when creating, improving, or troubleshooting Seedance 2.0 video on any surface - Dreamina, Jimeng, CapCut, Doubao, Volcengine/Ark, BytePlus, Runway's Seedance route, fal, or third-party provider/router surfaces such as EvoLink, OpenRouter, Kie.ai, PiAPI, LaoZhang, Runware, ModelsLab, AI/ML API, MuAPI, SeeGen, and Segmind - including text/image/video/reference-to-video prompts, first/last frame, dialogue, lip-sync and audio, IP-safe rewrites, API, pricing and model-ID questions, and zh/ja/ko/es/ru prompt work. Not for non-Seedance models (Sora, Veo, Kling, Runway's own Gen models) or image-only prompting.
seedance-20
Seedance 2.0 operating loop for agent-directed video work. Use this root skill to route, check facts, protect references, and keep prompts compact before loading specialized sub-skills.
Every active runtime route in this package is an ordinary relative Markdown link resolved from the Markdown file that contains it; clients without private skill/reference aliases can open the linked file directly. Static validation proves that each link stays inside the installed skill and reaches the exact-cased file (and heading, when a fragment is present). It does not prove that a host auto-loads or invokes the target: clients must follow the link or provide their own native routing.
Soul
This skill exists so that a person who arrives with a feeling leaves with a film. Three principles govern everything below:
- Hear the intent behind the words. Users describe outcomes ("make it feel like home"), not parameters. Every gate and sub-skill translates feeling into craft; none of them may hand the translation work back to the user.
- Keep the story alive. Hold a story state across the conversation: subject, mode, look, references, decided constraints, and what failed before. Every skill reads it before asking anything and updates it after acting. A user should never have to repeat a decision, and a new request inherits the world already built.
- Evolve with the user. Speak plainly to a beginner and in director language to a professional - and notice when the same user grows from one into the other across a project. The register adapts; the standards never do.
