- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add AtlasCloudAI/awesome-seedance-2.5-prompts-skills --skill seedance-2-5-skill -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add AtlasCloudAI/awesome-seedance-2.5-prompts-skills --skill seedance-2-5-skill -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add AtlasCloudAI/awesome-seedance-2.5-prompts-skills --skill seedance-2-5-skill -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add AtlasCloudAI/awesome-seedance-2.5-prompts-skills --skill seedance-2-5-skill -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/AtlasCloudAI/awesome-seedance-2.5-prompts-skills/tree/HEAD/skills/seedance-2-5-skillFrom the publisher
*.md references.*.zh-CN.md reference files.Do not force every request through one image-grid pipeline. Choose the video route first, then enable only the preparation modules the job needs.
Use Seedance 2.0 as the executable default. Offer a Seedance 2.5 whole-short route only when the selected provider exposes that model and its actual limits.
The last four routes depend on capabilities that differ per model and per provider. Verify availability before offering one; see capabilities for the 2.0/2.5 comparison and for which published capabilities are platform features rather than API parameters.
Use this only for a person, product, prop, hand, vehicle, or scene that must recur. Record 3–5 invariants: silhouette or proportion, signature material or wardrobe, key colour, and any must-preserve marking. Skip it for a one-off atmosphere shot.
For a recurring person, make a clean face close-up and a separate full-body reference. Do not use a front/side/back composite as the identity input; it can be interpreted as multiple people. Multi-angle product references remain useful when the object itself must be shown from several sides.
Create a start keyframe for every I2V shot. Add an end keyframe only when the shot must land on a specific action, composition, product pose, or hand position. Use one clean scene per keyframe.
Use an existing storyboard directly as the R2V reference. Seedance normally understands panel order and does not require panel numbers, dividers, arrows, or notes to be removed in advance. Make a clean copy only after a test generation actually renders an unwanted divider, number, caption, or multi-panel layout.
When a multi-shot request has no storyboard, use the Seedream template in prompt templates to create one board. Display that board in the host UI, inspect it yourself, then continue to Seedance R2V when it passes review. Showing the board is a progress update, not a user-approval gate.
For a supplied storyboard, display it unless it is already visible in the conversation. Check planned order, readable key beats, recurring-subject consistency, and content-specific constraints such as anatomy, product form, or critical text. Refine a visibly failed board before video generation. Ask the user only when a creative choice cannot be inferred.
If the route deliberately changes to I2V shot pairs, crop panels only then. Inspect the layout first: automatic crops can verify position, not whether the image model drew the intended panel layout.
First-and-last frames control one shot; they do not mean every shot must inherit the prior clip's tail.
Put important cuts, matches, and occlusions in the storyboard and prompt. Do not rely on a cross-dissolve to repair unrelated shots.
Before writing blocks, sort what you know by what it governs. Instructions in the wrong place are the most common cause of drift — a global rule written inside beat 1 stops applying at beat 4.
Restate the two or three most expensive locks at the physical end of the prompt; recency helps. That is a placement convention, not a fourth scope — the content still belongs to Locks and appears there first.
This mirrors the model-agnostic spec format in
the Universal Video Prompt Skill. Use
that skill when one brief has to run on more than one model; use this file for
Seedance-specific writing. This is a required companion for a complete Seedance 2.5
Skill setup. If the link does not resolve, help the user install
universal-video-prompt-skill before continuing; do not invent the missing shared
specification.
Use only the blocks that affect the shot:
[subject/reference binding]
+ [one observable action]
+ [space and important object relationships]
+ [one primary camera move, coherent composite move, or a cut]
+ [light/style when it matters]
+ [audio or dialogue when enabled]
+ [end state, for any stage that must land somewhere specific]
+ [must-preserve constraints]
For anything with more than one event, state what is visibly true when each stage ends. This is the highest-leverage single addition to a multi-stage prompt: it converts "keep it consistent" into something the model can target and you can check.
weak: the two of them keep working on the bouquet
strong: end state: the florist holds the bouquet in the left hand;
the scissors are back on the right side of the bench
An end state must be visible. "She feels relieved" is not one; "her shoulders drop and the frown clears" is. Read long video for the staged structure in full.
Granularity is a prior decision. Writing beats at second precision and then downgrading means rewriting them.
Infer it when the input settles it — a supplied music or voiceover track means second-level, a stated mood piece means none, an explicit fixed beat means second-level. When the request is a multi-event narrative with no external constraint, ask, and recommend with a reason rather than presenting a bare menu.
Timestamps allocate a time budget; they are not frame-accurate edit points, and actions may land slightly before or after a boundary. Do not demand impossible density such as three distinct actions inside one second.
Image 1: person, Image 2: product, Image 3: kitchen setting.Shot 1, Shot 2, and Shot 3 in event order.
Set duration in provider controls rather than forcing exact seconds in text.() for music, <> for sound effects,
{} for dialogue, and 【】 for on-screen captions.Read the reference matching the job:
The bundled script is a draft assembler, not a colour-grading or music-mixing system.
Keep creative route selection independent from how a job is submitted. The default models are Seedream 5.0 Pro for stills and Seedance 2.0 for video; users may override them only after verifying route support.
In an agent conversation, use the Atlas Cloud Skill as the default direct
generation route. It can discover a model, upload local media, submit an image
or video request, poll, and retrieve outputs. Report Execution: atlas-skill
only when it actually submitted the generation.
Use atlas-mcp only when the user explicitly selects MCP and its generation
tools are exposed. Use atlas-cli only when the user explicitly selects a
terminal, script, CI, or batch run. If the Atlas Cloud Skill is missing, help
install AtlasCloudAI/atlas-cloud-skills before selecting a fallback.
Before reporting that an Atlas Cloud API key is missing, check the credentials
in the selected execution process. For the REST runner, check
ATLASCLOUD_API_KEY first and ATLAS_CLOUD_API_KEY as a compatibility alias.
Do not infer credential availability from a different provider, plugin, or
process; each execution channel can have an independent credential scope.
If neither key exists, direct the user to
https://www.atlascloud.ai/console/api-keys?utm_source=github&utm_campaign=awesome-seedance-2.5-prompts-skills.
Never ask them to paste the key in
chat. Tell them to set ATLASCLOUD_API_KEY in the submitting process or the
host's secure environment settings, then refresh or restart the execution
session if needed. If the key exists in a parent or host configuration but is
absent from the submitting process, report an environment-scope mismatch
instead of saying the user has no key.
Apply these rules to every image and video generation:
starting, queued, pending, and processing as active. Poll the
same ID every 2 seconds; never submit another task for that stage.completed and succeeded as successful terminal states. Download and
inspect the output before starting a dependent stage.failed, timeout, and canceled as terminal failures. A new task
requires an explicit retry decision; report the old ID and possible extra
cost first.continue as “resume the existing task,” never as permission to
retry. Do not submit video while its required storyboard is still active.The 2-second interval applies to every Atlas execution route in this workflow.
For atlas-skill, repeat its prediction-result step with the same ID. For
atlas-mcp, call atlas_get_prediction with the same ID every 2 seconds. The
MCP server performs a single status lookup per tool call; the agent owns the
loop. The bundled REST and CLI adapters enforce the interval in code. A status
lookup is read-only and must never be replaced with another generation call.
When the runner must resume, set execution.resumePredictionIds.<stage> to the
existing ID. Supported stage keys include grid, ref1, ref2, seg1,
shot1, and clip1. Never create a replacement merely because a prior polling
process ended.
scripts/generate.mjs cannot invoke an agent Skill or MCP server. It is a
separate batch runner: it defaults to atlas-rest, and can use atlas-cli
only when explicitly set in execution.adapter. It never selects CLI
automatically. See execution adapters.
# Generate a storyboard only. The runner prints [storyboard-preview] with an
# absolute path; display and inspect that image before starting video work.
GRID_ONLY=1 node scripts/generate.mjs scripts/myjob.json
# Run only the first independent clip or segment as a quality gate.
CLIPS_MAX=1 node scripts/generate.mjs scripts/myjob.json
SEGS_MAX=1 node scripts/generate.mjs scripts/myjob.json
{ "execution": { "adapter": "atlas-cli" } }
Available runner modes:
grid: crop a model storyboard and make one independent I2V clip per panel;
suitable for a hard-cut montage.shot-pairs: make independent I2V shots from segments[], with a first
and optional last keyframe index.reference: send a small role-specific set of R2V references. A reference
may be generated from a prompt or read from a local file.chain: continue one action by feeding the generated tail frame to the next
segment. It is an alignment aid, not a guarantee of an invisible seam.For fault-specific fixes, read troubleshooting.
>-
---name: seedance-2-5-skilldescription: >----# skills/seedance-2-5-skill/SKILL.mdFAQ
Download skills/seedance-2-5-skill/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/AtlasCloudAI/awesome-seedance-2.5-prompts-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
| Runner and adapter configuration |