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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/seedance-lighting/SKILL.md

Quality

Content

82%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 well-crafted, instruction-only skill body that is lean, concrete, and well-structured with prompt-ready examples and a clear output contract. The main gap is implicit rather than explicit validation checkpoints in its workflow.

Suggestions

Add an explicit validation/verification step in the opening workflow (e.g., 'before returning the lighting block, confirm source, direction, color temperature, and transition are all stated') to raise workflow clarity.

Consider a short fill-in template for the Output Contract so the prompt-ready integrated sentence is copy-paste ready rather than described.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — every section (Lighting Contract, Source Selection, Color and Atmosphere, Failure Fixes) delivers rules and examples without explaining what lighting or color temperature is, matching the lean-and-efficient anchor.	5 / 5
Actionability	It gives concrete, prompt-ready examples in the contract table (e.g., 'narrow warm strip light sweeps across brushed metal') plus explicit source-selection and failure-fix rules, but stops short of a fully copy-paste ready template per case, leaving minor gaps.	4 / 5
Workflow Clarity	The opening sequences the work (load Director's Read → classify the brief → complete the record → translate to carriers → Output Contract) and the Failure Fixes section provides a feedback loop, but explicit validation checkpoints between steps are only implicit.	4 / 5
Progressive Disclosure	Structure is good with clearly signaled one-level-deep inline references (Director's Read, color-pipeline-aces, directing-engine) and well-organized sections; it falls just short of the 5 anchor because the referenced files live outside this bundle and their contents cannot be verified here.	4 / 5
	Total	17 / 20 Passed

Description

77%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 strong, trigger-rich description that clearly signals when to activate, anchored to the Seedance 2.0 niche. Its main weakness is that it lists topics rather than concrete capabilities, leaving the 'what does this do' side implicit.

Suggestions

Lead with a concrete capability clause (e.g., 'Translates mood and scene briefs into physical lighting prompts specifying source, direction, color temperature, and transitions') before the 'Use when...' trigger list.

Add 1-2 active verbs describing what the skill produces (e.g., 'designs and compiles lighting blocks') so the 'what' is explicit, not just the 'when'.

Dimension	Reasoning	Score
Specificity	The description names the lighting domain and trigger topics ("lighting design, atmosphere, time of day, color temperature, shadow, reflections") but states almost no concrete actions — "asks for lighting design" is the only verb, with the rest being topics rather than capabilities. It sits at the anchor naming a domain with 1-2 actions, not the 4-anchor list of several specific actions.	3 / 5
Completeness	It has an explicit "Use when the user asks for..." trigger clause, but the "what" is only implied by "lighting design" rather than stated as concrete actions, so it falls just short of the explicit both-what-and-when anchor.	4 / 5
Trigger Term Quality	It packs in the natural terms a user would actually say — "lighting design, atmosphere, time of day, color temperature, shadow, reflections, weather light, practical lights, mood transitions" — with broad synonym coverage matching the comprehensive anchor.	5 / 5
Distinctiveness Conflict Risk	The Seedance 2.0 scoping plus the specific lighting vocabulary carves a clear niche with minimal overlap risk, though the broad lighting/atmosphere terms could lightly overlap a generic mood or color skill.	4 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 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
relative_links	Relative link issues: 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: Emily2040/seedance-2.0
Path: skills/seedance-lighting/SKILL.md
Commit: 9ea203f

Reviewed: 5 days 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.