Menu

Individual skill

seedance-troubleshoot

0upvotes

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.

skills/seedance-troubleshoot/SKILL.md

Read pinned source

Source commit 4668457e560eee06e95d7fcfdf441c8c0bba802e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
8,097
Repository last updated
Oct 3, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# seedance-troubleshoot

Before producing prompt text, a prompt-ready block, a rewrite, an example, or a compiled clip, load the [Director's Read](../../references/directors-read.md), 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](../../references/retake-protocol.md) 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](../../references/model-mechanics.md) 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](../../references/field-observed-tips.md), [reference-workflow](../../references/reference-workflow.md), and [api-workflow](../../references/api-workflow.md) when the failure involves continuation, edit/extend, source clips, audio references, or platform-specific errors. Load [shot-list-continuity](../../references/shot-list-continuity.md) for multi-shot drift and [delivery-qc](../../references/delivery-qc.md) for final-client or delivery failures. When sequence state is present, load [failure-atlas](../../references/failure-atlas.md), [continuation-handoff](../../references/continuation-handoff.md), and [continuity-qc](../../references/continuity-qc.md); 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