seedance-recipes

This skill should be used when the user asks for a Seedance 2.0 template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene, or reusable production pattern.

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-recipes/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.

The body is a tight, well-structured instruction skill with actionable prompt skeletons and a clear workflow, slightly held back by references to files not present in the local bundle and by the lack of explicit validation checkpoints.

Suggestions

Add a brief verification step in the workflow (e.g. confirm the selected recipe preserves the brief's most fragile requirement before emitting the final prompt) to strengthen workflow_clarity.

Confirm the ../../references/*.md files resolve from the skill's installed location, or co-locate them under the skill's own references/ directory so the signaled links are navigable.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense: it assumes Claude knows video production, never pads with definitions of Seedance or clip structure, and every section (families table, skeletons, selection rule, output contract) earns its tokens.	5 / 5
Actionability	Concrete, copy-paste-ready prompt skeletons with bracketed placeholders (e.g. "Camera: [single move]. Lighting: [physical source].") plus a per-family core-pattern table give specific executable guidance, though the placeholders still require judgment to fill.	4 / 5
Workflow Clarity	A clear sequence is stated up front ("load the Director's Read, classify the brief, and complete its canonical record") and an Output Contract defines what to return, with the Selection Rule and Sequence State guiding decisions; explicit validation checkpoints are absent but the task is generative rather than destructive/batch.	4 / 5
Progressive Disclosure	Content is well split into an overview plus one-level-deep, purpose-labeled references ("Load [genre-guides] for genre patterns, [examples-by-mode] when the user needs copy-ready examples..."), but the referenced files live at ../../references/ and are not present in the skill bundle, so navigation cannot be fully verified.	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.

The description has strong, natural trigger terms and a clear niche, but it states when to use the skill far more explicitly than what the skill actually does, leaving the action implicit.

Suggestions

Lead with an explicit action verb for the "what", e.g. "Generate Seedance 2.0 prompt recipes and templates for..." before the "Use when" clause.

Keep the strong trigger list but pair it with a one-phrase statement of the deliverable (e.g. "...returns a customized prompt skeleton and final prompt").

Dimension	Reasoning	Score
Specificity	Lists many concrete deliverable types ("Seedance 2.0 template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene"), giving specific output categories rather than vague abstractions, though it stops short of naming the action (e.g. generate/produce) explicitly.	4 / 5
Completeness	An explicit, concrete "when" clause is present ("should be used when the user asks for..."), but the "what" is only implied by the noun list — no explicit action verb states what the skill does, so it falls between the only-when and clear-what anchors.	3 / 5
Trigger Term Quality	Comprehensive coverage of natural trigger terms a user would actually say, spanning template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, and animation scene with the Seedance 2.0 qualifier.	5 / 5
Distinctiveness Conflict Risk	The Seedance 2.0 qualifier plus a highly specific set of video-production output types carves a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 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: 5 suspicious	Warning

	Total	13 / 16 Passed

Repository: Emily2040/seedance-2.0
Path: skills/seedance-recipes/SKILL.md
Commit: 44b5149

Reviewed: 28 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.