CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-prompt

This skill should be used when the user asks to write, improve, translate, compress, or debug a Seedance 2.0 video prompt; mentions T2V, I2V, V2V, R2V, camera direction, prompt quality, or provides reference assets for a production-ready prompt.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 dense, expert-level instruction skill with concrete slot patterns, per-mode mistake/repair pairs, an explicit compression order, and multiple validation gates before delivery. The main costs are repetition of the Director's Read gate, checklist rules compressed into hard-to-scan run-on prose, and a workflow spread across many sections instead of one canonical ordered view.

Suggestions

State the Director's Read load-and-classify gate once (in Director Formula) and reference it from the opening and Prompt Build Process instead of repeating the full instruction three times.

Reformat the eight-point check in the Pre-Delivery Screen as a short bulleted checklist (or move it entirely into direct-for-the-model.md and link to it) rather than one multi-clause sentence, so each rule is scannable at delivery time.

Consolidate the process into a single numbered end-to-end sequence (classify → lane record → reference roles → shot table → draft → checks → screen → output contract), with Mode Gate, Time Structure, and Compression Rules as clearly-labeled substems, so the reader does not have to infer the order across sections.

DimensionReasoningScore

Conciseness

The body carries almost no filler and assumes Claude's competence — no section explains what video generation or prompting is — with all content being skill-specific rules. It loses a point to redundancy (the Director's Read load-and-classify instruction is stated three times: lines 23, 35, and 79; multishot-grammar is loaded in both the line-27 sweep and Time Structure) and to overlong chained sentences ('Before the screen, run the eight-point check...' packs an entire checklist into one paragraph) that could be split without adding tokens.

4 / 5

Actionability

Concrete guidance dominates: the director-formula table gives prompt-ready example phrases per slot ('slow dolly-in from medium product shot to macro label detail'), the mode table names each mode's common mistake and its literal repair ('Say `preserve @Image1 exactly`'), compression is an explicit priority-ordered cut list, and the Output Contract is a numbered deliverable list. It falls short of fully executable because the eight-point check and Stakes and Peak rules are compressed into prose rather than a runnable checklist, and no complete worked example prompt appears inline (examples are delegated to examples-by-mode.md).

4 / 5

Workflow Clarity

The Prompt Build Process section gives a real ordered sequence ('First, load the Director's Read... Next, assign reference roles... then write the draft... Finally, run a self-check') backed by explicit validation checkpoints (self-check, directing coherence test, paper render on the shot table, moderation pre-screen, anti-slop pass). It is not a 5 because the full workflow is distributed across six sections the reader must assemble, some ordering is stated inversely ('Before the screen, run the eight-point check'), and intermediate checkpoints like the paper render are invoked without a link to where they are defined.

4 / 5

Progressive Disclosure

The body is a genuine overview that delegates depth to ~12 one-hop reference files, each with a clear purpose signal ('for the checklist', 'for image-to-video', 'for shot order'), plus routing to sibling skills for continuation and filtering — navigation is easy. It stays at 4 because the load-sweep in the opening references paragraph bundles eleven files into one sentence, and substantial reference content (the eight-point check from direct-for-the-model, the Stakes and Peak summary from directing-engine) is duplicated inline rather than split out, and no bundle files were present alongside this SKILL.md to verify the referenced paths exist.

4 / 5

Total

16

/

20

Passed

Description

92%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 description: third-person voice, explicit 'use when' triggers, five concrete actions, and a tightly-scoped Seedance 2.0 niche that minimizes conflict risk. The only gap is reliance on mode acronyms (T2V/I2V/V2V/R2V) without their spelled-out natural-language synonyms, which costs it the top trigger-term score.

DimensionReasoningScore

Specificity

The description names five concrete actions scoped to one artifact — 'write, improve, translate, compress, or debug a Seedance 2.0 video prompt' — which is comprehensive coverage for this domain. It is written in third person ('This skill should be used when the user asks...'), so no voice penalty applies, and it goes beyond the level-4 anchor by covering the full action set rather than leaving minor gaps.

5 / 5

Completeness

Both halves are explicit: what ('write, improve, translate, compress, or debug a Seedance 2.0 video prompt') and when ('This skill should be used when the user asks to...; mentions T2V, I2V, V2V, R2V, camera direction, prompt quality, or provides reference assets'), matching the level-5 anchor's what-plus-concrete-trigger-phrases pattern. Not 4, because the when-clause enumerates specific trigger phrases rather than a vague 'use when working with prompts'.

5 / 5

Trigger Term Quality

Good keyword coverage: 'Seedance 2.0 video prompt', 'camera direction', 'prompt quality', 'reference assets', and the mode acronyms T2V, I2V, V2V, R2V that platform users naturally say. It stops short of the level-5 anchor because spelled-out natural variants are missing — 'text-to-video', 'image-to-video', 'video generation', or generic phrases like 'make/edit a Seedance video' that a user might say before learning the mode acronyms.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — Seedance 2.0 video prompts specifically, with mode acronyms and 'camera direction'/'reference assets' as triggers — that no generic video or prompt-engineering skill would claim. Conflict risk is minimal; even a competing video-prompt skill would be distinguishable by the Seedance 2.0 and mode-term triggers.

5 / 5

Total

19

/

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: 24 suspicious

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

skills/seedance-prompt/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.