CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seedance-characters/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, example-driven policy skill whose blocking and action-hierarchy sections are genuinely actionable, weakened mainly by a dangling output format and by references that resolve outside the bundle to files that are not present. The rhetorical Intent section is the only noticeable token waste.

Suggestions

Include one worked example of the mandated output — a filled-in character card with tag map, tier assignments, and continuity constraints — so the Output Contract is unambiguous.

Fix or inline the `../../references/shot-list-continuity.md` and `directing-engine.md` links: they escape the skill bundle and the target files are absent, so either bundle them under `references/` with relative paths or move their essential content inline.

Compress the Intent section to a single operational sentence (e.g., "Treat every recurring character as a continuing cast member with a contract, never a re-cast stranger") and add a one-line final self-check that every visible character has exactly one action tier and no ambiguous pronouns remain.

DimensionReasoningScore

Conciseness

The body is lean and prescriptive — a field table, tiered rules, and concrete example prompts ("Character A lowers the envelope; Character B remains in the doorway") with no explanation of concepts Claude already knows. Not 5: the Intent section ("The user is protecting someone here... the user feels it as betrayal, not as a rendering artifact") is rhetorical framing rather than operational guidance and could be trimmed to one line.

4 / 5

Actionability

For an instruction-only skill the guidance is unusually concrete: stable tag formats (`Character A`, `@Image1 subject`), a field-by-field prompt table, an explicit three-tier action hierarchy with example phrasing ("lip corner lifts and she holds a half-second glance"), and explicit prohibitions ("explicitly exclude standing, walking, turning"). Not 5: the Output Contract mandates "a character card, tag map, action assignments" but no example of that output's shape is ever shown, leaving the deliverable underspecified.

4 / 5

Workflow Clarity

The sections read as a coherent implicit sequence — assign tags → block multi-character actions → apply the tier hierarchy → hands/face and likeness constraints → inherit sequence state → emit the output contract — and the Output Contract gives a verifiable end product. Not 5: nothing tells Claude to self-check (e.g., that every visible person received exactly one tier, or that no ambiguous pronouns remain after more than one character appears), so checkpoints are implicit rather than explicit; not 3 because the flow is coherent and no destructive/batch operation is involved.

4 / 5

Progressive Disclosure

Sections are well organized for a short skill, and the two outbound references are clearly signaled with load conditions ("Load shot-list-continuity when... identity, wardrobe, props, eyeline... must survive across multiple shots"). However, both links point to `../../references/` — outside the skill bundle — and those files do not exist in the provided structure, so navigation cannot be verified and the links may be broken; this is more than the "minor organization gaps" of anchor 4.

3 / 5

Total

15

/

20

Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed trigger clause with a strong, specific keyword list, but it is one-sided: it says exhaustively when to use the skill and almost nothing about what the skill does. Adding one sentence of concrete function would lift both completeness and specificity.

Suggestions

Open with a what-clause stating the skill's function in third person, e.g., "Provides prompting rules, character-contract templates, and blocking patterns that keep recurring characters visually and behaviorally consistent across shots".

Add trigger synonyms users actually type — "same character in every shot", "character reference", "face/identity drift" — to broaden natural-term coverage.

State the medium (AI video/clip generation) so the skill triggers only for character-consistency work in that context, sharpening distinctiveness.

DimensionReasoningScore

Specificity

The description enumerates specific domain facets — "multi-character blocking, wardrobe continuity, hand safety, expression control" — but never states a single concrete action or capability; it is a topic list, not a list of things the skill does. It sits between anchor 2 ("names the domain but actions are minimal or generic") and anchor 3 ("names domain and 1-2 concrete actions"), closer to 3 because the facets are individually concrete rather than generic.

3 / 5

Completeness

The "when" is explicit and well-formed ("This skill should be used when the user asks for..."), so the use-when cap does not apply, but the "what" is only implied by the enumerated topics — the description never says what the skill does (e.g., provides prompting rules and character-contract templates for consistent characters). It is stronger than anchor 2 ("only 'when' is present without 'what'") because the topic list gestures at scope, but weaker than anchor 4, which requires an actual statement of function.

3 / 5

Trigger Term Quality

"character consistency, character tags, identity lock, multi-character blocking, wardrobe continuity, hand safety, expression control, likeness-sensitive character guidance" are natural phrases a user prompting video characters would say. Not 5: no synonyms or phrasing variants (e.g., "same character across shots", "face drift", "character reference") and no mention of the video/image-generation context that would catch adjacent phrasings.

4 / 5

Distinctiveness Conflict Risk

Niche trigger terms like "identity lock", "likeness-sensitive", and "multi-character blocking" give it a clear niche unlikely to fire for unrelated skills. Not 5: terms like "character consistency" and "wardrobe continuity" overlap with sibling continuity/costume skills in the same seedance-20 family, a minor conflict risk.

4 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

skills/seedance-characters/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.