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

81%

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.

The body is a lean, highly actionable recipe catalog with concrete prompt skeletons and a dense family table. Its weaknesses are an implicit rather than explicit workflow sequence and references to [ref:...] files that do not exist in any bundle directory.

Suggestions

Convert the implicit pick→customize→output flow into an explicit numbered sequence (select recipe, customize skeleton, return per Output Contract) with a verification step that the chosen recipe protects the most fragile requirement.

Either ship the referenced bundle files under references/ (genre-guides, examples-by-mode, shot-list-continuity, multilingual-community-examples) or remove the [ref:...] pointers; if kept, use standard markdown links like [genre-guides](references/genre-guides.md) so navigation resolves.

Add a brief validation checkpoint in the Sequence State section (e.g., confirm continuity locks and reference tags are honored before finalizing the current prompt) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean: a compact recipe-family table, fill-in prompt skeletons, and tight rules, with only a brief "Intent" paragraph of philosophy; it assumes Claude's competence and avoids explaining concepts Claude already knows, matching the lean-and-efficient anchor.	3 / 3
Actionability	It provides concrete, copy-paste-ready prompt skeletons with specific placeholders (e.g., "Product I2V: @Image1 is the product reference; preserve logo, label, shape, and materials exactly. [One material or light change]. Camera: [single move]..."), which are the executable units for this prompt-generation skill per the code-vs-instruction scoring note.	3 / 3
Workflow Clarity	A sequence is implied ("Pick the recipe that matches the user's outcome, then customize..." plus an Output Contract) but it is never laid out as an explicit numbered sequence with checkpoints, matching the level-2 anchor where the sequence is present but implicit.	2 / 3
Progressive Disclosure	The body signals four references with clear purpose descriptions (e.g., "Load [ref:genre-guides] for genre patterns"), but no references/, scripts/, or assets/ bundle exists so those files do not resolve, and the non-standard [ref:...] syntax is not a navigable markdown link — structure is present but references don't actually exist.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 trigger-term coverage and a clear, distinctive Seedance 2.0 niche with an explicit use-when clause. Its main weakness is that it lists deliverable nouns without stating the skill's action, leaving the "what does this do" half of completeness only implied.

Suggestions

Lead the description with an explicit action verb (e.g., "Generates Seedance 2.0 prompt recipes and production templates...") so the "what" is stated, not just implied by the noun list.

Keep the existing "Use when..." trigger list but reorder so the action precedes the when-clause, mirroring the rubric's level-3 completeness example.

Dimension	Reasoning	Score
Specificity	The description enumerates many specific concrete deliverable types — "Seedance 2.0 template, genre recipe, product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene" — matching the anchor for listing multiple specific concrete capabilities; it is not vague.	3 / 3
Completeness	It has an explicit "when" ("This skill should be used when the user asks for...") but never states the action verb of what the skill does — providing/generating these recipes is only implied from the noun list, so the "what" is not clearly answered as the level 3 anchor requires.	2 / 3
Trigger Term Quality	It includes natural terms a user would actually say ("product ad", "music video", "landscape shot", "commercial", "animation scene", "drama scene") with good coverage, matching the high-coverage anchor rather than the sparse level 2 example.	3 / 3
Distinctiveness Conflict Risk	It is tied to a clear niche ("Seedance 2.0") with a distinct set of video-production genre triggers, making it unlikely to fire for unrelated skills, matching the clear-niche anchor.	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-recipes/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.