CtrlK
BlogDocsLog inGet started
Tessl Logo

seedance-lighting

This skill should be used when the user asks for lighting design, atmosphere, time of day, color temperature, shadow, reflections, weather light, practical lights, or mood transitions in Seedance 2.0.

69

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-structured instruction spec: it gives a concrete contract, ready-to-use prompt fragments organized by mood/task, source-selection heuristics, failure-recovery guidance, and a clear output contract, with no wasted tokens.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence — 'Lighting should describe physical sources and transitions, not abstract beauty' — with no padding explaining what light or color temperature is, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It supplies a concrete Lighting Contract, a table of copy-paste-ready prompt fragments ('warm practical lamp from frame left, blue moonlight rim on shoulders'), explicit source-selection rules, and an Output Contract; as an instruction-only skill the guidance is fully actionable, so absence of code is not penalized.

3 / 3

Workflow Clarity

This is a simple single-purpose skill whose single action (produce a lighting block + transition note + integrated sentence) is unambiguous via the Output Contract, and the Failure Fixes section provides explicit error-recovery guidance, satisfying the simple-skill allowance for a 3.

3 / 3

Progressive Disclosure

Content is organized into clearly headed sections (Intent, Lighting Contract, Source Selection, Color and Atmosphere, Failure Fixes, Sequence State, Output Contract); as a sub-50-line simple skill with well-organized sections it meets the 3 anchor per the simple-skills scoring note, and the [ref:...] load triggers are clearly signaled one-level-deep pointers.

3 / 3

Total

12

/

12

Passed

Description

72%

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

The description has excellent trigger coverage and a clear, conflict-resistant niche via the Seedance 2.0 scoping, but it omits any statement of what the skill actually does, leaving the 'what' half of completeness and the action specificity underserved.

Suggestions

Lead with one concrete capability clause before the trigger list, e.g. 'Describes physical light sources, direction, color temperature, and transitions for Seedance 2.0 prompts.' to satisfy both the 'what' and specificity dimensions.

Keep the existing 'Use when the user asks for...' trigger list intact — it is the description's strongest asset — and simply prepend the capability statement.

Optionally name the deliverable form ('returns a compact lighting block plus one prompt-ready sentence') so users know the output shape up front.

DimensionReasoningScore

Specificity

The description names a rich, specific domain ('lighting design, atmosphere, time of day, color temperature, shadow, reflections, weather light, practical lights, or mood transitions') but states no concrete actions or capabilities — 'should be used when' is a trigger, not a description of what the skill does.

2 / 3

Completeness

It answers 'when' explicitly ('should be used when the user asks for...') but never answers 'what does this do', so it cannot reach the 3 anchor that requires both; the strong explicit trigger keeps it above the 'both very weak' 1 anchor.

2 / 3

Trigger Term Quality

Natural terms a user would actually say are well covered ('lighting design', 'atmosphere', 'shadow', 'reflections', 'mood transitions'), matching the 'good coverage of natural terms' anchor rather than the 'some relevant keywords' anchor at 2.

3 / 3

Distinctiveness Conflict Risk

Scoping to 'in Seedance 2.0' with domain-specific triggers (practical lights, weather light, color temperature) gives it a clear niche unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
Emily2040/seedance-2.0
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.