CtrlK
BlogDocsLog inGet started
Tessl Logo

seedance-20

This skill should be used when creating, improving, or troubleshooting Seedance 2.0 video on any surface - Dreamina, Jimeng, CapCut, Doubao, Volcengine/Ark, BytePlus, Runway's Seedance route, fal, or third-party provider/router surfaces such as EvoLink, OpenRouter, Kie.ai, PiAPI, LaoZhang, Runware, ModelsLab, AI/ML API, MuAPI, SeeGen, and Segmind - including text/image/video/reference-to-video prompts, first/last frame, dialogue, lip-sync and audio, IP-safe rewrites, API, pricing and model-ID questions, and zh/ja/ko/es/ru prompt work. Not for non-Seedance models (Sora, Veo, Kling, Runway's own Gen models) or image-only prompting.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-architected routing skill: a sequenced gate loop with explicit checkpoints, a fast lane for the common case, and a clean Load Map that pushes detail into verified reference files. It earns top marks on actionability, workflow clarity, and progressive disclosure; conciseness is the only soft spot due to some repetition between the gate list and the Authority Order/Sequence Gate prose.

Suggestions

Consolidate the Sequence Gate invariants, which restate constraints already implied by the Sequence Gate step and continuation references, into a brief pointer.

Tighten the Authority Order explanatory paragraphs; the tier classification examples could be shortened once the tier list itself is stated.

DimensionReasoningScore

Conciseness

The body is information-dense and largely free of concepts Claude already knows, but it is long and several passages (Authority Order prose, Sequence Gate invariants) repeat ideas already implied by the gate list, so it could be tightened.

2 / 3

Actionability

Gives concrete, executable routing: a numbered Operating Loop with explicit '[skill:...]' and '[ref:...]' load triggers, exact word-count budgets (40-110 words), and one-variable-per-retake rules that read as direct instructions.

3 / 3

Workflow Clarity

The 13-step Operating Loop is a clear sequence with validation checkpoints (Safety/Source/Professional/Sequence/Mode gates), a fast-lane shortcut, a repair loop with triage and attempt budget, and an explicit Authority Order for resolving contradictions.

3 / 3

Progressive Disclosure

SKILL.md stays a lean overview with a Load Map table of well-signaled one-level-deep '[ref:...]' and '[skill:...]' pointers, and spot-checking the references directory confirms the cited files (e.g. directing-engine.md, capability-map.md, vocab/zh.md) all exist.

3 / 3

Total

11

/

12

Passed

Description

100%

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 dense, third-person description with explicit trigger guidance, concrete action list, and a sharp exclusion clause that bounds the niche. Its only weakness is verbosity - it crams surfaces and tasks into one long sentence rather than the leaner style the rubric rewards.

Suggestions

Trim the provider/router enumeration into a representative few plus 'and other Seedance-compatible routers' to cut length without losing trigger coverage.

Split the single long sentence into a short 'Use when...' clause followed by a compact scope list for faster scanning.

DimensionReasoningScore

Specificity

Lists many concrete actions (text/image/video/reference-to-video prompts, first/last frame, dialogue, lip-sync and audio, IP-safe rewrites, API/pricing/model-ID questions, zh/ja/ko/es/ru prompt work) across a long enumeration of surfaces.

3 / 3

Completeness

Opens with an explicit 'should be used when...' trigger and enumerates what is covered, then closes with an explicit 'Not for...' exclusion, answering both what and when clearly.

3 / 3

Trigger Term Quality

Embeds natural user-facing terms users would actually say (Seedance, video, prompts, lip-sync, audio, API, pricing, model ID) plus surface names like Dreamina, CapCut, Runway, fal.

3 / 3

Distinctiveness Conflict Risk

The 'Not for non-Seedance models (Sora, Veo, Kling...)' exclusion carves a clear niche and actively prevents triggering on competing video skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.