⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
seedance-vocab-es
This skill should be used when the user asks for Spanish Seedance 2.0 prompt wording, Spanish cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Spanish.
// RATINGS
// README
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
Languages: English (this page) · 中文 · 日本語 · 한국어 · Español · Русский
Five-minute quickstarts: 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 are in the table 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.
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 user ~/.agents/skills/seedance-20/; no-option installer keeps its historical path |
| Google Antigravity | .agents/skills/seedance-20/ (workspace) or ~/.gemini/config/skills/seedance-20/ (global across Antigravity products) |
| OpenClaw | workspace skills/seedance-20/ or ~/.openclaw/skills/seedance-20/ via openclaw skills install (ClawHub-compatible; skills already carry openclaw: metadata) |
| Hermes Agent | ~/.hermes/skills/seedance-20/ (primary); a project skills/seedance-20/ directory is discovered only after its parent is added to skills.external_dirs in ~/.hermes/config.yaml |
| Gemini CLI-style workspace | .gemini/skills/seedance-20/ |
| GitHub Copilot workspace | .github/skills/seedance-20/ |
| Cursor workspace | .cursor/skills/seedance-20/ |
| Windsurf workspace | .windsurf/skills/seedance-20/ |
| Trae (ByteDance) | .trae/skills/seedance-20/ |
| Qwen Code (Alibaba) | .qwen/skills/seedance-20/ or ~/.qwen/skills/seedance-20/ |
| OpenCode | .opencode/skills/seedance-20/ (also reads .claude/skills/ and .agents/skills/) |
| Amp (Sourcegraph) | .agents/skills/seedance-20/ or ~/.config/agents/skills/seedance-20/ |
| Goose (Block) | .agents/skills/seedance-20/ (also .goose/skills/seedance-20/) |
| Junie (JetBrains) | .junie/skills/seedance-20/ or ~/.junie/skills/seedance-20/ |
Several of these clients share the .agents/skills/ convention — Codex, Google Antigravity, OpenCode, Amp, and Goose all read it — so one install under .agents/skills/seedance-20/ can serve them together, and .claude/skills/ is read by many as a compatibility path. Install once as the seedance-20 root skill; its sub-skills and references resolve by relative path.
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/pro
// HOW IT'S BUILT
KEY FILES