How to use the Seedance Output Troubleshooter agent skill

What an agent skill is and what this one does

An agent skill is a folder containing a SKILL.md file with instructions that an AI agent loads when a request matches the skill's description. This one is named seedance-troubleshoot and is licensed MIT.

When a Seedance 2.0 clip fails, the skill makes the agent first identify the failed criterion and the evidence, such as what you saw or what you reported. It then checks a symptom-to-cause table, for example mapping a changing product or face to an image-to-video prompt that re-described visible identity or overloaded motion. The agent proposes one primary repair variable and writes one cautious retry prompt that keeps what already worked.

• Quotes the failing phrase or missing element from your prompt
• States a likely cause or testable hypothesis and how certain it is
• Removes conflicts before adding complexity
• Returns one conservative retry prompt, plus an optional creative variant only if you ask for exploration

Install the skill from the ZIP

Download the ZIP from the skill's page on the directory. Then install it in one of two ways, depending on how you use Claude.

For Claude Code, unzip the download into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want it available only in that project.

In the Claude apps, open Settings, go to Capabilities, then Skills, and upload the ZIP there.

• Personal use across projects: ~/.claude/skills/
• Single project: the .claude/skills/ folder inside that project
• Claude apps: Settings → Capabilities → Skills

Check what you need before you start

The skill itself only produces text. It diagnoses and writes prompts but does not regenerate anything. To actually retry a clip you need Seedance 2.0 access.

The skill loads several reference files, including directors-read, retake-protocol and model-mechanics. These must be present in the repository you install from. The single SKILL.md file is not enough on its own, so if the agent reports a missing reference, install the full repository folder.

• Seedance 2.0 access to regenerate clips
• The full repository, including the reference files the skill loads
• No scripts are run by this skill
• The skill does not use the network

Trigger the skill with natural requests

You do not need a special command. The skill is meant to be used when a Seedance 2.0 output is blurry, jittery, off-prompt, morphing, blocked, visually generic, unstable, desynced, inconsistent or otherwise failing. Describe the problem in plain words and include the prompt you used if you have it.

Give the agent as much evidence as you can. What you saw, when it happened, and which part of the prompt you think caused it all help the diagnosis.

• My Seedance 2.0 clip has the product changing shape halfway through. Here is my prompt: ...
• This Seedance output keeps coming back blurry in the background. Diagnose it before rewriting.
• The second clip in my sequence restarts the action from the first clip. What went wrong?
• Seedance blocked my prompt. Help me rewrite the intent in safe production language.

Read the diagnosis the agent returns

A good response names the failing element, gives a cause with honest uncertainty, and proposes one change. The skill treats repeated failures as a reason to look at the cause, not as proof that the prompt is bad.

The skill's table covers common failures, such as camera jumps (several incompatible moves or no endpoint), lip-sync problems (moving head or camera, long dialogue, unassigned speaker) and text or logos breaking (small text asked to move or be redrawn). For continuation problems it covers items like a restarted completed action or a reserved future beat leaking into the current prompt.

• Camera jumps: choose one move with a start and a finish
• Lip-sync poor: lock framing, shorten the line, assign the speaker
• Text or logos break: keep text static, centered and protected
• Extension quality degrades: use the returned last frame as the first frame and change one variable

Escalate carefully when the same error repeats

If the same error keeps happening, the skill suggests splitting the scene into shorter clips, reducing characters, simplifying hand or face motion, using stronger reference role mapping, or changing the mode. For edit or extend failures it suggests preserving the source clip first and changing only the failing layer.

The skill does not authorize extra generations. Requesting a review or rewrite does not mean another generation is submitted, and at zero or exhausted budget it submits nothing and keeps your model, duration, resolution and reference roles unchanged.

• Shorter clips or fewer characters
• Simpler hand or face motion
• Stronger reference role mapping
• Change the mode, then retest