seedance-characters
/seedance-characters
This skill should be used when the user asks for character consistency, character tags, identity lock, multi-character blocking, wardrobe continuity, hand safety, expression control, or likeness-sensitive character guidance.
- Author
- anymouschina ↗
- Repository
- tapcanvas ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
This skill should be used when the user asks for character consistency, character tags, identity lock, multi-character blocking, wardrobe continuity, hand safety, expression control, or likeness-sensitive character guidance.
Original author description
This skill should be used when the user asks for character consistency, character tags, identity lock, multi-character blocking, wardrobe continuity, hand safety, expression control, or likeness-sensitive character guidance.
How it works
- Intent
- Character Contract
- Multi-Character Blocking
- Three-Tier Action Hierarchy
- Hand and Face Stability
- Likeness Rule
- Sequence State
- Output Contract
SKILL.md preview
---
name: seedance-characters
description: "This skill should be used when the user asks for character consistency, character tags, identity lock, multi-character blocking, wardrobe continuity, hand safety, expression control, or likeness-sensitive character guidance."
license: MIT
user-invocable: true
tags:
- characters
- identity
- consistency
- seedance-20
metadata:
version: "6.6.0"
updated: "2026-07-04"
parent: "seedance-20"
author: "Iamemily2050 (@iamemily2050)"
repository: "https://github.com/Emily2040/seedance-2.0"
openclaw:
emoji: "🎬"
homepage: "https://github.com/Emily2040/seedance-2.0"
---
# seedance-characters
Surface reference contract: literal `@Image1` examples below are Seedance 2.0 surface syntax, not a required character-tag form. Emit only exact tokens supplied by the user or active structured surface; otherwise use stable neutral character names and the active structured reference fields.
Use this for identity, consistency, multi-character blocking, wardrobe continuity, hand safety, expression control, and likeness-sensitive character guidance. Character prompting must remove ambiguity before adding style.
Load `[ref:shot-list-continuity]` when character identity, wardrobe, props, eyeline, screen direction, or emotional state must survive across multiple shots. Load `[ref:directing-engine]` to direct performance: give each character a playable objective, show subtext through contradiction between word and action, and keep one performance register consistent with the project's directorial voice.
## Intent
The user is protecting someone here - a character they invented, a product they built, or a person they love. Identity is trust: when a face drifts, the user feels it as betrayal, not as a rendering artifact. Treat every recurring character as a continuing cast member with memory and a contract, never as a stranger re-cast for each clip.
## Character Contract
Assign each character a stable tag: `Character A`, `Character B`, `@Image1 subject`, or a user-provided original name. After more than one character appears, do not use ambiguous pronouns. Keep tag, role, appearance, wardrobe, position, action, and emotional beat consistent.
| Field | Prompt use |
|---|---|
| Tag | `Character A` or `@Image1 subject` |
| Identity anchor | Age range, silhouette, hair, wardrobe, or authorized reference role |
| Position | Foreground/background, left/right, seated/standing |
| Action | One assigned verb and endpoint |
| Expression | Observable behavior such as blink, glance, smile, grip, pause |
| Constraint | What must stay unchanged |
## Multi-Character Blocking
Assign actions separately: `Character A lowers the envelope; Character B remains in the doorway`. Do not write `they argue dramatically` when the model must decide who moves. If contact occurs, describe the contact point and endpoint. For crowd scenes, identify the hero subject and keep background motion simple.
## Three-Tier Action Hierarchy
Field-observed from Chinese production practice; the strongest known stabilizer for multi-person scenes. Give every visible person an action from exactly one tier:
1. **Persistent micro-motion** - breathing, blinks, slight shoulder movement, hair drift, drifting gaze. Continuous, no gaps; this is the default tier for everyone who is not the focus.
2. **One focused response** - a single person gets one small reaction with an explicit time window: `Character B's lip corner lifts and she holds a half-second glance`.
3. **Large actions - prohibited by default.** In multi-person shots, explicitly exclude standing, walking, turning, posture changes, and object pickup unless one of them is the shot's single beat. Character-to-prop physics (lifting a glass, passing an object) is fragile with multiple people on screen - keep contact simple or move it off-screen.
## Hand and Face Stability
Hands and faces degrade under complex choreography. Keep hands visible but simple, avoid rapid finger actions, avoid face-touching during dialogue, and lock the camera for lip-sync or portrait preservation. Use props to show emotion when facial precision is fragile.
## Likeness Rule
For real-person likeness, do not infer consent from an uploaded asset. Treat portrait, face, and voice workflows as authorization-dependent and surface-specific. If authorization is unclear, rewrite to an original character archetype while preserving the scene function.
## Sequence State
When sequence state is present, inherit wardrobe, hair, screen geography, eyeline, pose, emotional state, current clip scope, continuity locks, exact reference tags, and reserved future beats. Canonical identity references control identity; accepted footage controls transient opening state. Do not let a motion or continuity source overwrite immutable character locks.
## Output Contract
Return a character card, tag map, action assignments, continuity constraints, and any safety or authorization note.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · anymouschina/tapcanvas | 100 | MIT |
| navyran/skills | 90 | MIT |
| Emily2040/seedance-2.0 | 90 | MIT |
| leoyeai/seedance-skills | 90 | MIT |
| sideshowroberto/vfx-agent-toolkit | 85 | MIT |
Database snapshot: 13.11.2026 · package version 498b2f11dc8b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100continuity-tracking
Screenplay continuity tracking systems and templates. Covers character registry, timeline registry, location registry, prop registry, and wardrobe registry for maintaining story consistency. Use when: setting up tracking systems, checking consistency, managing timelines, or… - 90video-character-continuity
Use when the task is to keep character appearance, wardrobe, props, and screen direction stable across shots. - 100character-consistency
Use when a character must stay visually identical across AI video scenes — locks identity tokens (silhouette, palette, wardrobe, prop) in JSON. Triggers 'character lock', 'same character'. - 100seedance-20
This skill should be used when directing Seedance 2.0 T2V, I2V, V2V, R2V, audio, safety, or API work. - 100higgsfield-character-design
Pre-production story-and-character development for Higgsfield projects — the upstream layer that decides WHAT to prompt before any model runs. Use when the user wants to build a character, design a world, develop a story or premise, create a character sheet / character bible /… - 100dp-character-style
Use when establishing character speech patterns, writing dialogue, verifying voice consistency, or crafting subtext through what characters avoid saying