seedance-motion

This skill should be used when the user asks for body action, choreography, physics, object movement, movement timing, action continuity, stunt direction, or motion-reference mapping in Seedance 2.0.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%

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

A lean, highly actionable skill body with strong examples and clear patterns. Its main weaknesses are the absence of an explicit validation/verification checkpoint for sequence and reference-mapping operations, and four [ref:...] links that point to bundle files which are not present.

Suggestions

Add an explicit verification step for multi-clip sequence and reference-mapping work (e.g., 'confirm each beat carries the story forward and references are licensed before returning the output contract') to support a feedback loop.

Provide the referenced bundle files (reference-workflow, shot-list-continuity, examples-by-mode, directing-engine) under references/ or remove the [ref:...] links so signaled references actually resolve.

Standardize the reference link syntax to a resolvable path form (e.g., [reference-workflow.md](references/reference-workflow.md)) so the progressive-disclosure navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean with no padding or explanation of concepts Claude already knows; every section (Motion Contract, Physics-Forward, Timing, Stability) earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It provides concrete, copy-ready guidance: a strong/weak phrase table, a worked three-beat timing example ('0-2s: candle flame steady; 2-4s: door opens...'), and explicit cause-consequence patterns, matching the 'fully executable / specific examples' anchor.	3 / 3
Workflow Clarity	Sections are well sequenced (Motion Contract -> patterns -> Output Contract), but multi-clip sequence and reference-mapping operations have no explicit validation or feedback checkpoint, and the rubric caps workflow clarity at 2 when validation/verification is missing for such operations.	2 / 3
Progressive Disclosure	The body clearly signals one-level-deep references ([ref:reference-workflow], [ref:shot-list-continuity], [ref:examples-by-mode], [ref:directing-engine]) with good section organization, but no corresponding bundle files exist in references/, scripts/, or assets/, so the signaled references do not resolve.	2 / 3
	Total	10 / 12 Passed

Description

90%

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-constructed trigger-oriented description with explicit 'use when' guidance and a clear Seedance 2.0 niche. It is strong on trigger terms and completeness, though it leans on domain enumeration rather than stating the concrete actions the skill performs.

Suggestions

Pair the domain list with the concrete actions the skill performs (e.g., 'composes motion phrases, maps reference footage, sequences action continuity') so specificity scores at the top anchor.

Lead with a short active-voice what-statement before the trigger list to make the skill's capability unambiguous.

Dimension	Reasoning	Score
Specificity	The description names many concrete domains ('body action, choreography, physics, object movement, movement timing, action continuity, stunt direction, or motion-reference mapping') but describes domains/triggers rather than the concrete actions the skill performs, matching the 'Names domain and some actions' anchor rather than a full list of executable actions.	2 / 3
Completeness	It explicitly answers both what (motion-reference mapping in Seedance 2.0) and when via 'This skill should be used when the user asks for...', matching the anchor that requires both an explicit 'Use when' clause and a what statement.	3 / 3
Trigger Term Quality	It provides broad coverage of natural terms a user would say (choreography, stunt direction, movement timing, action continuity), matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'Seedance 2.0' with distinctive triggers (stunt direction, choreography, motion-reference mapping), giving it a clear niche unlikely to conflict with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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

	Total	14 / 16 Passed

Repository: Emily2040/seedance-2.0
Path: skills/seedance-motion/SKILL.md
Commit: 6c51262

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.