CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-vocab-ru

This skill should be used when the user asks for Russian Seedance 2.0 prompt wording, Russian cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Russian.

Quality

69%

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

Quality

Content

50%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.

The body is well-sectioned and contains a useful concrete vocabulary table and prompt pattern, but its core workflow defers to reference files that are absent from this bundle, and much of the Output Contract reads as abstract policy rather than executable guidance. Tightening the prose and either shipping or inlining the deferred vocabulary would materially improve it.

Suggestions

Ship the referenced files (references/directors-read.md, references/vocab/ru.md, references/surface-prompt-profiles.md) in the bundle or inline the essential vocabulary, since every 'load X' instruction currently points at a missing file.

Rewrite the Output Contract as a short numbered checklist of concrete actions (what to return, what to preserve, what to ask), replacing abstract statements like "distinguish their visible performance, staging or information tradeoffs".

Remove duplication and meta-commentary: the token-does-not-attach-file rule appears twice, and the Intent section's remarks about the empty review artifact do not guide execution.

DimensionReasoningScore

Conciseness

The body is dense and vocabulary tables earn their tokens, but there is avoidable padding: the Intent section is meta-commentary ("The shipped independent review artifact is empty, so treat these choices as working production wording pending locale-specialist review") and the idea "A written example token does not attach a file" / "A written token does not attach an asset" is stated twice. It matches 'mostly efficient but could be tightened', not anchor 4's 'only minor instances'.

3 / 5

Actionability

There are genuinely concrete elements — the Russian wording table ("медленный наезд камеры", "контровой свет"), the copy-paste Compact Pattern, and the named slop words ("кинематографичный", "эпичный") — but the core workflow depends on files ("load [vocab/ru](../../references/vocab/ru.md)", "load the [Director's Read](../../references/directors-read.md)") that do not exist in this bundle, and much of the Output Contract is abstract ("distinguish their visible performance, staging or information tradeoffs") rather than executable guidance. This lands between anchors 3 and 4, closer to 'incomplete; missing key details'.

3 / 5

Workflow Clarity

An opening sequence exists (load Director's Read → classify the brief → complete the record → translate into carriers) but it is prose, not a numbered workflow, and validation checkpoints are only implicit ("Time the actual performance", "name the criterion, propose one concrete change"). Anchor 3 ('sequence present but checkpoints missing or implicit') fits; anchor 4 would require explicit checkpoints tied to each step.

3 / 5

Progressive Disclosure

References are clearly signaled with purpose (Director's Read for classification, vocab/ru for dense vocabulary, surface-prompt-profiles for example adaptation), but the bundle contains no references/ directory — every referenced path (../../references/directors-read.md, ../../references/vocab/ru.md, ../../references/surface-prompt-profiles.md) resolves outside the skill or to nothing, so navigation is broken and the vocabulary payload the body defers to is unavailable. Anchor 3 ('some structure; references present but... could be better organized') applies rather than 4's 'references mostly clear and appropriately placed'.

3 / 5

Total

12

/

20

Passed

Description

78%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 well-targeted, trigger-rich description for a niche skill. The 'when' is explicit and the term categories are concrete; the main weakness is that the 'what' is implied by the when-clause rather than stated, and a few natural synonyms are absent.

Suggestions

State the capability independently in third person (e.g., "Provides Russian wording for Seedance 2.0 video prompts and translates camera, lighting, action, VFX, audio, and production terms into Russian") before the Use-when clause.

Add common synonyms users might say, such as "video prompt", "Russian dialogue/lip-sync wording", or a sample Russian trigger phrase, to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Russian Seedance 2.0 prompt wording") and several concrete deliverables: "Russian cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Russian". It stops short of listing multiple distinct actions (compose, rewrite, bind references), so it fits 'several specific actions; minor gaps' rather than the comprehensive anchor 5.

4 / 5

Completeness

The 'when' is fully explicit ("This skill should be used when the user asks for...") with concrete triggers, but the 'what' is only embedded inside the when-clause rather than stated as a capability (e.g., "Provides Russian wording for..."). This matches anchor 4 ('both what and when; one could be more explicit'), not 5, where the what is stated independently.

4 / 5

Trigger Term Quality

Natural trigger phrases are present — "Russian Seedance 2.0 prompt wording", "Russian cinematic vocabulary", "camera, lighting, action, VFX, audio" — which a user needing this skill would plausibly say. Missing common synonyms such as "video prompt", "Russian subtitles/dialogue", or a Russian-language trigger term, so it falls between anchors 3 and 5 at 4.

4 / 5

Distinctiveness Conflict Risk

The niche is narrow and clearly bounded — Russian-language Seedance 2.0 video-prompt vocabulary — a combination unlikely to collide with other skills. Trigger terms are distinct, so the clear-niche anchor 5 applies.

5 / 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: 5 suspicious

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

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