Seedance
songguoxs/seedance-prompt-skill
This skill should be used when the user asks to "generate video prompts", "create Seedance prompts", "write video descriptions", mentions "Seedance", "seedance", "即梦", "即梦平台", "视频提示词", "视频生成"…
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause…
Install Seedance Troubleshoot
$ npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Emily2040/seedance-2.0 seedance-troubleshoot --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Emily2040/seedance-2.0.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seedance-troubleshoot .claude/skills/seedance-troubleshoot && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "seedance-troubleshoot" agent skill from https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshoot into .claude/skills/seedance-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seedance-troubleshoot", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshootType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Emily2040/seedance-2.0 seedance-troubleshoot --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Emily2040/seedance-2.0.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seedance-troubleshoot .agents/skills/seedance-troubleshoot && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seedance-troubleshoot" agent skill from https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshoot into .agents/skills/seedance-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seedance-troubleshoot", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Emily2040/seedance-2.0 seedance-troubleshoot --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Emily2040/seedance-2.0.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seedance-troubleshoot .cursor/skills/seedance-troubleshoot && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seedance-troubleshoot" agent skill from https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshoot into .cursor/skills/seedance-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seedance-troubleshoot", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Emily2040/seedance-2.0.git --path skills/seedance-troubleshoot--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Emily2040/seedance-2.0 seedance-troubleshoot --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Emily2040/seedance-2.0.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seedance-troubleshoot .gemini/skills/seedance-troubleshoot && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "seedance-troubleshoot" agent skill from https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshoot into .gemini/skills/seedance-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seedance-troubleshoot", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Emily2040/seedance-2.0 seedance-troubleshootInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Emily2040/seedance-2.0.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seedance-troubleshoot .github/skills/seedance-troubleshoot && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "seedance-troubleshoot" agent skill from https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshoot into .github/skills/seedance-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seedance-troubleshoot", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Emily2040/seedance-2.0 seedance-troubleshoot --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Emily2040/seedance-2.0.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seedance-troubleshoot .opencode/skills/seedance-troubleshoot && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seedance-troubleshoot" agent skill from https://github.com/Emily2040/seedance-2.0/tree/main/skills/seedance-troubleshoot into .opencode/skills/seedance-troubleshoot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seedance-troubleshoot", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
seedance-troubleshoot- GitHub stars
- 7.6k
- Used in
- 1 other repo
- Token cost
- ~1.9k tokens
- SKILL.md length
- 882 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- MIT
At a glance
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause…
- Tasks that involve AI video generation
- SKILL.md covers Intent, Diagnostic Tree, Repair Process and Conservative Retry Pattern, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Seedance Troubleshoot is an agent skill from Emily2040/seedance-2.0. This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative, covering AI video generation. It works with Seedance. The repository describes itself as: Comprehensive production pipeline for quad-modal AI filmmaking with Seedance 2.0. The licence is MIT.
When your agent uses it
- Tasks that involve AI video generation
Example prompts
- “/seedance-troubleshoot”
What it can do on your machine
Read from SKILL.md and the folder at commit 4668457. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Seedance Troubleshoot loads about 1.9k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 882 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Emily2040/seedance-2.0 at commit 4668457, republished under its MIT licence (© Emily2040). 882 words, ~1,887 tokens.
Download SKILL.mdSave it as
.claude/skills/seedance-troubleshoot/SKILL.md (or your agent's skills folder).- name
- seedance-troubleshoot
- description
- This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
- license
- MIT
- user-invocable
- true
- tags
- diagnostics, troubleshooting, seedance-20
- metadata.version
- 6.7.0
- metadata.updated
- 2026-08-01
- metadata.parent
- seedance-20
- metadata.author
- Iamemily2050 (@iamemily2050)
- metadata.repository
- https://github.com/Emily2040/seedance-2.0
seedance-troubleshoot
Before producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the Director's Read, classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers and keep its internal labels out of final generation prose.
Use retake-protocol to record the failed criterion, observed or user-reported evidence, useful parts of the take, one plausible repair, and the remaining authorized limits. Diagnose before rewriting; repeated failures do not prove the prompt is wrong. Consider mode mismatch, conflicting references, ambiguity, unsupported controls, model variation, or missing preservation constraints. A review or rewrite request does not authorize another generation. At zero/exhausted budget, submit nothing; preserve model/tier, duration, resolution, and reference roles unless an already authorized change covers them.
When the diagnostic tree has no row for the failure, load model-mechanics and propose a testable hypothesis from the observed failure: conflicting priorities, ambiguous constraints, action timing, continuity state, reference roles, detail readability, or audio attribution. Do not present a diagnosis as proof of hidden model internals. Load field-observed-tips, reference-workflow, and api-workflow when the failure involves continuation, edit/extend, source clips, audio references, or platform-specific errors. Load shot-list-continuity for multi-shot drift and delivery-qc for final-client or delivery failures. When sequence state is present, load failure-atlas, continuation-handoff, and continuity-qc; diagnose against continuity locks, completed beats, exact reference tags, and reserved future beats.
Intent
A failed generation feels personal - the user showed the machine their idea and the machine returned something broken. The soul of this skill is rescue without blame: describe a plausible failure mechanism without blaming the user; preserve the idea as well as the prompt. They should leave with a fix and their confidence intact.
Diagnostic Tree
| Symptom | Likely cause | First repair |
|---|---|---|
| Product or face changes | I2V prompt re-described visible identity or overloaded motion. | Add preservation constraints; remove duplicate static detail. |
| Camera jumps | Several incompatible moves or no endpoint. | Choose one move with start and finish. |
| Generic output | Hollow style words and weak action. | Replace with physical action, source light, material, and sound. |
| Motion ignored | Static prompt or no visible consequence. | Add actor, verb, timing, and changed end state. |
| Lip-sync poor | Moving head/camera, long dialogue, unassigned speaker. | Lock framing, shorten line, assign speaker. |
| VFX noisy | Effect has no source, physics, or dissipation. | Add source, material, path, interaction, and endpoint. |
| Prompt blocked | Protected IP, real-person, graphic, or bypass-like wording. | Rewrite intent in safe production language without evasion. |
| Extension quality degrades | No last-frame anchor or too many new variables across continuations. | Use returned last frame as first frame and change one variable. |
| Audio reference ignored | Competing video sound, no visual beat mapping, or unsupported combo. | Mute competing video and map one visible event to the beat. |
| Text/logos break | Small text asked to move or be redrawn. | Keep text static, centered, and protected; animate light around it. |
| Client QC fails | Prompt output treated as final delivery without post/QC. | Route to delivery preflight, post fix, or regenerate only the failing shot. |
| Continuation assumed planned ending | Previous clip was not reviewed or observed_end_state was ignored. | Replace opening with actual observed end state. |
| Previous action restarted | Completed beat was not marked already_happened. | Add completed beat exclusion. |
| Future beat leaked | Reserved beat entered the current prompt. | Remove future beat and stop earlier. |
| Identity reference conflicts with continuity source | Source clip controlled transient state and identity at once. | Re-anchor identity from canonical reference. |
| Screen direction reset | Axis relation was not locked or intentionally reset. | Preserve screen direction or declare new-shot axis reset. |
| Open motion lost | Subject or camera vector was not inherited. | Carry motion vector into the opening sentence. |
| Camera phase restarted | Parent camera endpoint was not recorded. | Start from observed camera phase. |
| Prop state contradicted | Owner, position, or condition was missing. | Add prop state handoff. |
| Audio phase restarted | Completed dialogue or music phase was not logged. | Continue or intentionally change the audio phase. |
Show full SKILL.md (238 more words)Show less
Repair Process
First quote the failing phrase or missing element. Then state a plausible cause or testable hypothesis, with its uncertainty; call it a root cause only when the evidence establishes causation. Next, remove conflicts rather than adding complexity. Recommend one primary repair variable rather than adding more adjectives. Finally, produce one conservative retry prompt and one optional creative variant only if the user wants exploration.
Conservative Retry Pattern
[Reference role if any]. Preserve [identity/product/environment] exactly. One visible action: [specific verb and consequence]. Camera: [single move]. Lighting: [physical source]. Sound: [ambient/SFX/dialogue]. Constraints: [what must not change].
Escalation Rules
If the same error repeats, split the scene into shorter clips, reduce characters, simplify hand or face motion, use stronger reference role mapping, or change the mode. For unstable text/logos, keep them static, centered, and protected; do not ask the model to redraw small text during motion.
For edit/extend failures, preserve the source clip first and change only the failing layer. If a surface supports returned last frames, use that still as the next first-frame anchor before extending.
Output Contract
Return the failed criterion, observed or user-reported evidence, a plausible cause or testable hypothesis with uncertainty, and a repaired prompt when useful. Add a conservative retry proposal only when it serves the diagnosis; preserve the user's existing settings and authorization. Do not present uncertain causation as a proven root cause or submit a generation merely because a revision was requested.
© Emily2040, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/seedance-troubleshoot of Emily2040/seedance-2.0.
Open the folder on GitHubat commit 4668457
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Emily2040/seedance-2.0, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Seedance Troubleshoot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Seedance Troubleshoot this skillEmily2040/seedance-2.0 | 7.6k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Seedancesongguoxs/seedance-prompt-skill | 2.9k | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| SN Motion HTMLOpenSenseNova/SenseNova-Skills | 5.7k | — | ~2.2k | Automated safety check: Notes | MIT | |
| Seedance Prompt Endexhunter/seedance2-skill | 4.2k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Seedance 2 5 Video Directorliyue-aigc/seedance-2-5-video-director | 599 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Seedance Prompt Zhdexhunter/seedance2-skill | 4.2k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
SN Motion HTML
OpenSenseNova/SenseNova-Skills
Builds HTML stories where one continuous camera journey advances with page progress, using researched structure, AI stills, Seedance video clips and browser QA.
Seedance Prompt En
dexhunter/seedance2-skill
Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation.
Seedance 2 5 Video Director
liyue-aigc/seedance-2-5-video-director
Design, derive, optimize, diagnose, and rewrite scripts or copy-ready prompts specifically for Dreamina/即梦 Seedance 2.5.
Seedance Prompt Zh
dexhunter/seedance2-skill
为即梦 Seedance 2.0 多模态AI视频生成模型撰写高质量提示词。当用户需要使用文本、图片、视频、音频等多模态输入创作视频提示词时触发。涵盖@引用语法、运镜复刻、特效模仿、视频延长、视频编辑、音乐卡点、电商广告、短剧创作、科普教育等场景。
Seedance
MapleShaw/seedance2.0-prompt-skill
Generate production-ready Chinese video prompts and image prompts for ByteDance Seedance 2.0 (即梦), and optionally execute them via the official dreamina CLI.
More from Emily2040/seedance-2.0
All 29 skills in this repoSeedance 2.0 Video Prompting
Emily2040/seedance-2.0
Routes Seedance 2.0 video work across Dreamina, API and router surfaces, covering prompts, reference handling, audio and lip-sync, pricing and model-ID questions.
Seedance IP-Safe Prompt Rewriter
Emily2040/seedance-2.0
Rewrites Seedance 2.0 video prompts that name characters, brands, celebrities, songs or real people into original, rights-safe versions that keep the creative intent.
Seedance Japanese Prompt Examples
Emily2040/seedance-2.0
Provides Japanese prompt patterns and safe example rewrites for Seedance 2.0 video generation, with reference tags kept intact and each example labeled by risk.
Seedance Korean Prompt Examples
Emily2040/seedance-2.0
Korean-language prompt patterns for Seedance 2.0 video generation, each labeled as safe, needing an owned reference, or requiring a rewrite.
Seedance Chinese Prompt Examples
Emily2040/seedance-2.0
Supplies Chinese example prompts for Seedance 2.0 video generation, labeled by safety, with notes on rewriting prompts that name protected people or brands.
Seedance Anti-Slop Prompt Editor
Emily2040/seedance-2.0
Rewrites Seedance 2.0 video prompts to replace filler, hollow superlatives and vague cinematic wording with production-specific detail while keeping the user's style.
Related
Works with
Categories
Questions about Seedance Troubleshoot
What does Seedance Troubleshoot do?
This skill should be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause…. 0.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent, or otherwise fails and needs root-cause diagnosis.
When should I use Seedance Troubleshoot?
Seedance Troubleshoot fits situations like: tasks that involve AI video generation.
How do I install Seedance Troubleshoot in Claude Code?
Run `npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a claude-code`. Or copy the skill folder (skills/seedance-troubleshoot in Emily2040/seedance-2.0) into .claude/skills/seedance-troubleshoot in your project. Claude Code loads it when a task matches its description.
How do I install Seedance Troubleshoot in Codex?
Run `npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a codex`. Or copy the skill folder (skills/seedance-troubleshoot in Emily2040/seedance-2.0) into .agents/skills/seedance-troubleshoot in your project. Codex loads it when a task matches its description.
Can I use Seedance Troubleshoot in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Emily2040/seedance-2.0 --skill seedance-troubleshoot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seedance-troubleshoot, .gemini/skills/seedance-troubleshoot, .github/skills/seedance-troubleshoot and .opencode/skills/seedance-troubleshoot in your project.
What does Seedance Troubleshoot need to run?
SKILL.md names no scripts, command-line tools or credentials: Seedance Troubleshoot is instructions for the agent only.
Does Seedance Troubleshoot access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Seedance Troubleshoot safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Seedance Troubleshoot use?
Seedance Troubleshoot is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Seedance Troubleshoot use?
About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Seedance Troubleshoot?
Skills that share tags, products or a category with Seedance Troubleshoot: Seedance (songguoxs/seedance-prompt-skill, 2.9k stars), SN Motion HTML (OpenSenseNova/SenseNova-Skills, 5.7k stars), Seedance Prompt En (dexhunter/seedance2-skill, 4.2k stars) and Seedance 2 5 Video Director (liyue-aigc/seedance-2-5-video-director, 599 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Seedance Troubleshoot?
Emily2040 (a GitHub user) maintains it in Emily2040/seedance-2.0, which has 7,573 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 3, 2026.
Source: Emily2040/seedance-2.0 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.