seedance-camera

This skill should be used when the user asks for camera movement, shot scale, lens feel, framing, one-take direction, dolly, pan, tilt, push-in, handheld, aerial, macro, or camera-transfer guidance for Seedance 2.0.

Quality

91%

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

92%

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 cinematography-direction skill with concrete phrase patterns, decision rules, and a clear output contract. Its one real defect is progressive disclosure: it signals several [ref:...] bundles that are not present in the skill bundle.

Suggestions

Ship the referenced bundle files (quick-ref, cinematography-shot-language, directing-engine, vocab/zh, vocab/ru) under references/ so the inline [ref:...] links resolve, or remove the references and inline any essential content.

Confirm each [ref:...] token matches an actual file path in references/ (e.g. [ref:vocab/zh] -> references/vocab/zh.md) so Claude can load them without dead links.

Dimension	Reasoning	Score
Conciseness	The body is dense and directive, organized into short labeled sections with tables; it assumes Claude knows what a dolly or pan is and uses them as instructions rather than explaining the concepts, with only a brief purposeful "empathy mechanics" framing.	3 / 3
Actionability	It gives copy-paste-ready camera phrase patterns (e.g. "slow dolly-in from medium close-up to tight close-up as Character A lowers the envelope"), specific lens anchors, and exact reference-tag usage ("@Video1 controls camera rhythm only; do not transfer performer, room, logo, or identity").	3 / 3
Workflow Clarity	As a single-purpose advisory skill it provides an unambiguous decision flow (Move Selection -> Conflict Rule -> Continuity/Sequence State) and an Output Contract that acts as a deliverable checklist; no destructive/batch validation loop is required here.	3 / 3
Progressive Disclosure	The body is well organized and inline references are clearly signaled with stated purposes ("[ref:quick-ref] for prompt assembly", "[ref:directing-engine]"), but the referenced bundles (quick-ref, cinematography-shot-language, directing-engine, vocab/zh, vocab/ru) do not exist on disk, so navigation is broken rather than functional.	2 / 3
	Total	11 / 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 strong, trigger-rich description that explicitly tells Claude when to invoke it and is tightly scoped to Seedance 2.0 camera direction. Its main weakness is that the "what it does" side is thin ("guidance") rather than a list of concrete capabilities.

Dimension	Reasoning	Score
Specificity	The description names a clear domain (cinematography/camera) and one action ("camera-transfer guidance") but does not list multiple concrete capabilities; it is essentially a trigger-term list rather than a roster of specific actions like "extract, fill, merge".	2 / 3
Completeness	It has an explicit "This skill should be used when the user asks for..." trigger clause (clearly answering "when") and states the domain/purpose as camera-transfer guidance for Seedance 2.0 (answering "what"), so both are present.	3 / 3
Trigger Term Quality	It covers a broad set of natural cinematography terms a user would actually say ("camera movement, shot scale, lens feel, framing, one-take direction, dolly, pan, tilt, push-in, handheld, aerial, macro") plus the product name "Seedance 2.0".	3 / 3
Distinctiveness Conflict Risk	Tying triggers to the specific product "Seedance 2.0" with specialized camera vocabulary (dolly, push-in, macro, one-take) creates a clear niche unlikely to fire for 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-camera/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.