seedance-2.0

Turn an idea into a directed video prompt. Seedance 2.0 Skill OS is an agent skill for planning shots, binding references and continuing from an accepted clip. Your video provider handles generation and its costs.

Try a first prompt · Install · Choose a workflow · Evidence status

v6.7.0 · MIT · Changelog · Emily / Iamemily2050

Read in your language: English · 中文 · 日本語 · 한국어 · Español · Русский

Start Here

After installation, tell your agent what happens and what must stay fixed:

Use seedance-20. A person finishes a paper fan at a workbench. Keep it quiet, with one static shot and no music. Give me the prompt only.

One possible draft:

Locked tabletop shot. Two hands
finish the last fold of a paper
fan and let go. The fan settles
on the wood. Hold still for one
beat. Warm desk-lamp light;
dry paper rustle and room tone.
No music.

Why these choices: one visible action, a clear endpoint, a fixed camera and an explicit sound choice. Duration and aspect ratio belong in your provider's controls when that surface owns them. This is an unrendered teaching example; it does not establish successful folding, motion or audio generation.

For another treatment, choose calm observation, a playful gag or a step-by-step demonstration. Tell the agent which one you want to keep. A draft can be revised without submitting a paid generation request.

AI-generated teaching concept, not Seedance output. The still illustrates material, framing and light; it does not prove the action or sound will render. Image provenance and prompts.

More examples: performance and dialogue, product and process, reference and continuity.

Choose a workflow

What you have What to provide next A rough idea The action, feeling and delivery format; ask for a few distinct choices. A prompt to improve The draft and constraints you want preserved. Image, video or audio references Actual files and the role each should control. An accepted clip to continue Its observed ending and the next action. A result that missed The failed requirement and your remaining revision budget.

Start with the quickstart, reference workflow, continuation guide or retake protocol.

Install

Get a local copy, then run the installer from that folder. This example selects Codex user scope; other clients and replacement details are below.

git clone https://github.com/Emily2040/seedance-2.0.git
cd seedance-2.0
python scripts/install_codex_skill.py --client codex --scope user

Download ZIP also works: extract it and run the installer inside that folder. Restart your client, then select seedance-20. Review the security policy before configuring optional provider tools. Prompt preparation does not authorize paid generation.

Installation by client, replacement and recovery details

Client support for Agent Skills is still tool-specific. See observed compatibility and the host smoke protocol for tested revisions and explicit gaps. Codex documents a skill as a directory with a required SKILL.md, optional scripts/, references/, assets/, and optional agents/ metadata.

Codex scans .agents/skills locations from the working directory upward, plus user/admin/system skill locations. A repository root with SKILL.md is shaped like a skill folder, but it still needs to be installed/copied under a scanned skills directory or distributed as a plugin for automatic discovery.

Step 1 — get the files

Every install path below runs from inside a local copy of this repository, so start here:

git clone https://github.com/Emily2040/seedance-2.0.git
cd seedance-2.0

Without git installed, use the green Code → Download ZIP button on the repository page, unzip it, and change into the unzipped folder instead. Nothing else on this page works until one of those two has happened.

Step 2 — install it into your client

The installer is not Codex-only. Choose a client and scope below, or point --dest at another client's documented skills parent directory:

# Codex — user scope at ~/.agents/skills
python scripts/install_codex_skill.py --client codex --scope user

# Claude Code — personal install at ~/.claude/skills
python scripts/install_codex_skill.py --client claude-code --scope user

# One existing project, outside this source checkout
python scripts/install_codex_skill.py --client codex --scope project --project-root /path/to/project

# Any other client — use its documented skills parent directory
python scripts/install_codex_skill.py --dest /path/to/client/skills

Choose either --dest or --client with --scope; project scope requires an existing --project-root and never guesses from your current directory. The scope guide explains the paths. No-option commands preserve the historical $CODEX_HOME/skills or ~/.codex/skills default for existing workflows; they do not migrate old copies. Use the same destination options with the read-only install_doctor.py before deciding on replacement.

The command stages and validates the repository before promoting it to <dest>/seedance-20, then prints where it landed. Concurrent installers sharing that destination are serialized. Add --force only to replace a complete existing install. Automatic retry is limited to states for which every authority record required by the phase reached is present, has flushed file contents and, on POSIX, a flushed containing-directory publication, and still validates. Each payload file is first written under a transaction-derived sibling name, bounded by the recorded size, synced, checked against the recorded digest, atomically published at its final stage pathname, and followed by a containing-directory sync on POSIX. A crash therefore leaves that final pathname absent or complete, never truncated. The copy-sibling basename is capped at 34 ASCII bytes, shorter than the provenance marker already created before copying; on POSIX it shortens further if the stage reports a smaller component limit. Shortened names retain a transaction-and-path digest, and any namespace collision makes staging fail closed before payload copying begins. This bound applies only to copy siblings: the installer still requires the filesystem to represent its longer stage and authority names, so it makes no end-to-end claim for unusually small component limits. Recoverable states include an exact empty stage before provenance publication; after complete provenance publication, source-identical final payload files plus the one exact transaction- bound in-progress sibling; an exact torn prefix of the installer's expected provenance or completion record; and a deletion workspace bound by its external transaction journal (plus the exact empty terminal workspace left if that journal was already removed). Malformed, swapped, or otherwise untrusted records and late or unexpected bytes are preserved for inspection. A truncated file at an expected final payload pathname and an unbound temp-like file are likewise never claimed for automatic cleanup. So are the deliberately fail-closed hard-death windows after a quarantine is renamed but before its authority marker is published, or after a private deletion workspace is created but before its external journal is published. During replacement, the previous copy remains available for rollback until the validated stage is promoted. Restart your client afterwards so seedance-20 appears in its skill list.

On Windows, authority and deletion handles share reads only and remain open through their consuming action; a pre-existing or newly requested writable or deletion handle therefore makes the installer fail closed. On POSIX, verified objects are moved into a journal-bound mode-0700 workspace before unlink, which excludes other OS accounts and narrows the deletion namespace. POSIX flock and owner-only directory permissions are not mandatory isolation from a hostile process running as the same account. Such a process may retain or open writable descriptors and mutate either the workspace or its containing skills directory; all of those capabilities are outside the portable guarantee. The installer preserves mismatches it observes, but makes no stronger exclusion claim against that same-account adversary.

On POSIX, authority records are flushed before their containing directory, and transaction namespace renames and removals are followed by directory fsync. Each copied payload file is individually fsynced before its atomic rename, and that file's containing stage directory is fsynced after the rename. The transaction does not recursively flush the supplied skills-directory ancestry; that ancestry is assumed to have the durability expected by the caller.

Only manifest-declared files and their implied directories are created. Source permissions are not inherited: POSIX stage/live directories are normalized to 0700 and files to 0600. Named streams, extended attributes, and resource forks on the source root, declared files, or implied directories are refused before transaction authority is published, because the portable install contract cannot represent them. Installs skip the quarantined references/migrated/ history, the image gallery (about 18 MB of PNGs), the test suite, and the network-capable evaluator. The installer replaces the omitted gallery embeds with one repository link, so the installed README does not contain broken local asset targets.

A destination inside this repository is refused rather than attempted because it would mutate the source authority domain while the payload is being authenticated. For a project-local install, run the script from the project you are installing into, by absolute path, as above.

This repository keeps dense facts in references so the active skill stays small.

For a client that imports a local skill folder, first prepare the filtered payload in a new staging directory outside this checkout:

python scripts/install_codex_skill.py --dest /absolute/path/to/new-staging/skills

Import the resulting skills/seedance-20/ folder, or run the installer with --dest set directly to the skills parent directory your client scans. Keep the directory name seedance-20 and its relative layout. A raw repository clone or a client-managed GitHub import may include the evaluator, provider helpers, tests and archives; it does not carry the installer's filtered-payload guarantee. Inspect how that client packages files before using a direct import. See manual transfer and verification.

Treat the table below as common local targets to verify in your own client, not a universal support guarantee.

Platform Typical install target (verify in your client) Claude Code ~/.claude/skills/seedance-20/ (personal) or .claude/skills/seedance-20/ (project) — both via scripts/install_codex_skill.py --dest Codex project .agents/skills/seedance-20/ or u