CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/seedance-recipes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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-structured, lean overview for a multi-genre video-prompt recipe skill: the recipe family table and prompt skeletons give immediately usable guidance, and references are purpose-labeled and one level deep. The main gaps are implicit rather than explicit validation checkpoints, no inline worked final prompt, and reference paths that could not be verified against the bundle.

Suggestions

Include one fully worked example (brief → chosen recipe → customized skeleton → final compact prompt) directly in the body so the output contract is unambiguous without loading a reference.

Add an explicit validation/feedback checkpoint after prompt generation (e.g. re-check the brief's most fragile requirement against the final prompt) to complement the current implicit 'review accepted footage' rule.

Fix the reference paths to point inside the skill bundle (e.g. references/directors-read.md rather than ../../references/) and ensure the referenced files ship with the skill, so the progressive-disclosure structure resolves for the model using it.

DimensionReasoningScore

Conciseness

The body is dense and efficient — a compact recipe-family table, five fill-in prompt skeletons, and short rule sections with no explanation of concepts Claude already knows. The only trimmable material is the editorial flavor in 'Intent' ('a user who feels templated has been failed even if the output is competent'), keeping it just below anchor 5.

4 / 5

Actionability

Concrete, executable guidance throughout: copy-ready skeletons like '@Image1 is the product reference; preserve logo, label, shape, and materials exactly. [One material or light change]' plus a family-to-pattern table and a defined output contract. It stops short of anchor 5 because no fully worked final prompt example appears inline — worked examples are delegated to the references.

4 / 5

Workflow Clarity

A clear sequence opens the body (load the Director's Read, classify the brief, complete the record, translate to carriers), followed by recipe selection, sequence-state inheritance, and a defined output contract. Checkpoints are mostly implicit ('leave later prompts provisional until accepted footage is reviewed') rather than explicit validation steps, so it fits anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Six references are each one level deep and clearly signaled with purpose ('Load genre-guides for genre patterns, examples-by-mode when the user needs copy-ready examples'), and the main body stays a true overview. However, the referenced paths ('../../references/directors-read.md', etc.) point outside the skill directory and no bundle reference files are present to verify, leaving minor organization gaps that keep it below anchor 5.

4 / 5

Total

16

/

20

Passed

Description

70%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 trigger-rich, well-scoped description for the Seedance 2.0 recipe domain that reads naturally and covers many genres, but it is one-sided: it fully answers 'when' while leaving 'what the skill does' implied by the object list rather than stated. Adding one explicit capability verb would lift specificity and completeness.

Suggestions

State the concrete action the skill performs, e.g. 'Generates and customizes Seedance 2.0 video prompts from proven genre recipes' — the current description lists outputs but no capability.

Add natural trigger synonyms users would actually say, such as 'video prompt', 'clip', or 'Seedance prompt', to broaden keyword coverage.

Clarify the what/when split: keep the 'Use when...' clause but precede it with a one-phrase 'what' statement so the operation is explicit rather than implied.

DimensionReasoningScore

Specificity

The description names the Seedance 2.0 domain and lists many concrete artifact types ('product ad, lifestyle video, drama scene, music video, landscape shot, commercial, animation scene'), but it states no action or capability — there is no verb describing what the skill actually does with these inputs.

3 / 5

Completeness

The 'when' is fully explicit ('This skill should be used when the user asks for...'), and the object list conveys a 'what', but the actual operation the skill performs is never stated — both present, with the 'what' implicit rather than explicit.

4 / 5

Trigger Term Quality

Good natural keyword coverage across genres ('template', 'genre recipe', 'product ad', 'music video', 'commercial'), but common variations a user might say — 'video prompt', 'clip', 'Seedance prompt' — are missing, so it falls between anchors 3 and 5.

4 / 5

Distinctiveness Conflict Risk

'Seedance 2.0' scopes a clear niche with model-specific triggers, but generic terms like 'commercial', 'animation scene', and 'landscape shot' create minor overlap risk with general video-related skills.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

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

relative_links

Relative link issues: 6 suspicious

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

skills/seedance-recipes/SKILL.md

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.