CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-vocab-en

This skill should be used when an English Seedance 2.0 prompt needs clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints. Route blocked prompts through seedance-filter for context and boundary review.

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-vocab-en/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 compact, boundary-conscious instruction skill with genuinely useful inline vocabulary and a clear output contract. Its weaknesses are implicit workflow sequencing with no validation checkpoints, hedging prose that could be tightened, and heavy dependence on reference files that are absent from the bundle.

Suggestions

Number the core workflow explicitly (load Director's Read → classify → translate to carriers → de-slop → filter check if blocked → output) so the sequence survives being spread across sections.

Add a validation checkpoint before output, e.g. 'confirm every reference token matches the input exactly, including case and spacing'.

Trim the repeated negative-evidence hedges into one short 'What wording cannot do' line, and ship the referenced files (directors-read.md, vocab/en.md, anti-slop-lexicon.md, filter-vocab.md) so the links resolve.

Include one fully worked before/after example pair to complement the placeholder Compact Pattern.

DimensionReasoningScore

Conciseness

The body is mostly efficient — the vocabulary table and Compact Pattern are dense and useful — but each section carries a convoluted hedging sentence ('it is not a demonstrated cure for moderation errors', 'This repository has no matched evidence that English receives heavier moderation than other languages', 'A written example token does not attach a file') that reads as over-explanation and could be tightened to a few words. It fits the 'mostly efficient but includes some unnecessary explanation' anchor better than the lean 4, and nowhere near the padded 2.

3 / 5

Actionability

Guidance is largely concrete: a per-function vocabulary table ('slow push-in', 'warm practical light from the left', 'no music until after the line'), a fill-in Compact Pattern template, and explicit do/don't rules (preserve tokens 'including its script, case, spacing and punctuation'). It falls short of 5 because the pattern is a bracketed placeholder template and there is no single fully worked example of an input prompt and its rewritten output.

4 / 5

Workflow Clarity

A sequence exists — 'Before producing prompt text... load the Director's Read, classify the brief, and complete its canonical narrative or non-narrative record. Translate that record into visible or audible carriers' — followed by de-slop, filter routing for blocked prompts, and an Output Contract. But the steps are dispersed across topical sections rather than listed in order, and checkpoints are implicit; the only verification is the Output Contract's 'unchanged reference tags'. This matches the 3 anchor (sequence present, checkpoints implicit) rather than 4.

3 / 5

Progressive Disclosure

The split is conceptually right — a small inline example table with the full vocabulary delegated to references, each signaled with 'Load X for Y' phrasing — but the bundle contains no references/, scripts/, or assets/ directories, so all five-plus links (../../references/directors-read.md, ../../references/vocab/en.md, ../../references/anti-slop-lexicon.md referenced twice, ../../references/filter-vocab.md, ../seedance-filter/SKILL.md) are dangling and unverifiable. Structure is present and signaling is clear, which places it at the 3 anchor, but the skill is not navigable as bundled.

3 / 5

Total

13

/

20

Passed

Description

87%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, niche-scoped description that explicitly answers both what and when with concrete trigger terms and clean delegation to a sibling skill. The passive 'This skill should be used when...' phrasing and a few missing natural synonyms ('rewrite', 'video prompt') keep it just below the top tier.

Suggestions

Rewrite the opening in active third person (e.g., 'Refines English Seedance 2.0 prompts with concrete production wording...') to sharpen the what-clause.

Add one or two natural trigger synonyms users would actually say — 'rewrite', 'video prompt', 'shot description' — to broaden trigger matching.

State the concrete deliverable (a reworded prompt plus an explanation of material edits) so the what-clause covers the output, not just the inputs.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints' plus 'Route blocked prompts through seedance-filter' — matching the anchor for several specific actions with minor coverage gaps. It falls short of 5 because it never states that it rewrites or refines existing prompts as a deliverable, and the voice is the passive 'This skill should be used' rather than the crisper third-person declarative of the top anchor.

4 / 5

Completeness

Both questions are answered explicitly: what it does ('clearer production wording, less generic prose, or precise vocabulary for camera, lighting, motion, VFX, audio, and constraints') and when to use it ('should be used when an English Seedance 2.0 prompt needs...') with concrete trigger phrases. It clearly exceeds the 4 anchor, whose 'when' is only serviceably explicit.

5 / 5

Trigger Term Quality

It includes natural terms a Seedance user would say — 'camera', 'lighting', 'motion', 'VFX', 'audio', 'English', 'prompt', 'wording', 'blocked' — giving good keyword coverage. It stays at 4 rather than 5 because common synonyms like 'video prompt', 'clip', 'shot description', or 'rewrite' are missing, and it doesn't reach the comprehensive-with-synonyms level of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow (English wording for Seedance 2.0 prompts) and the explicit routing of blocked prompts to seedance-filter shows boundary awareness. It is not a 5 because it sits in a family of sibling seedance-* skills (other language variants, the filter skill), leaving minor overlap risk with closely related skills — exactly the 4 anchor.

4 / 5

Total

17

/

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

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

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