CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-vocab-ko

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

Quality

71%

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

Quality

Content

53%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 lean, well-sectioned instruction body with genuinely useful concrete vocabulary and a usable compact pattern, but it is undermined by process meta-commentary, a scattered workflow with no validation step, and three references that point outside the skill bundle to nonexistent files.

Suggestions

Fix the reference paths to point inside the skill bundle (references/directors-read.md, references/vocab/ko.md, references/surface-prompt-profiles.md) and include those files, so the speech-level and de-slop guidance can actually be loaded.

Remove process meta-commentary ("The shipped independent review artifact is empty...", the fixed-multiplier sync-budget aside) that does not guide translation work.

Add a final validation step to the Output Contract, e.g., re-check that every user-supplied reference tag and dialogue line survived unchanged before returning.

DimensionReasoningScore

Conciseness

The vocabulary table and compact pattern earn their tokens, but the body carries unnecessary meta and defensive filler: "The shipped independent review artifact is empty, so treat these choices as working production wording pending locale-specialist review", "do not use a fixed multiplier or change politeness to fit an invented sync budget", and "The table offers authored options, not a default look or a proven model-performance rule" — none of which guide the actual translation task. Mostly efficient but several sentences could be cut; it is below the 4 anchor because the padding is scattered across multiple sections, not minor.

3 / 5

Actionability

The Usage Rule table supplies concrete Korean wording ("느린 돌리 인", "역광", "조용한 환경음") and the Compact Pattern is a fill-in template with real placeholders (`@Image1은 참조 이미지이며... 카메라: [한 가지 움직임]`), which is copy-adaptable guidance for an instruction-only skill. Not a 5 because key guidance depends on reference files that are not part of the bundle, and a few directives stay abstract ("clarify ambiguous intent through observable light, framing, blocking, or timing").

4 / 5

Workflow Clarity

An ordered flow is implied by the opening paragraph (load the Director's Read, classify the brief, complete the record, translate into carriers, keep internal labels out) and the Output Contract states the deliverable, but the sequence is never laid out as steps, is scattered across five rule sections, and has no validation checkpoint (e.g., verify reference tags survived unchanged — the contract only asserts they should). This matches anchor 3: sequence present, checkpoints missing or implicit; it is not a destructive/batch skill so no cap applies, but it also lacks the explicit validation the 4/5 anchors require.

3 / 5

Progressive Disclosure

The body is sectioned and its three references are clearly signaled ([Director's Read](../../references/directors-read.md), [Using Reference Examples](../../references/surface-prompt-profiles.md#using-reference-examples), [the vocabulary guide](../../references/vocab/ko.md)), but scored against the actual bundle structure they are all broken: there is no references/ directory in the bundle, and the ../../ paths escape the skill directory entirely to files that do not exist. Navigation cannot actually be followed, which lands at anchor 2 ("minimal structure... or references are buried/broken") rather than 3, where references would at least resolve.

2 / 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 tight, third-person, niche-scoped description with explicit trigger guidance and good natural keyword coverage. Its main weakness is that the capability statement is folded entirely into the when-clause, leaving the what implicit rather than separately and explicitly stated.

Suggestions

State the capability as an explicit action before the trigger, e.g., "Translates camera, lighting, action, VFX, audio, and production terms into Korean for Seedance 2.0 prompts. Use when...".

Add one or two natural user phrasings such as "Korean video prompt" or "bilingual prompt wording" to broaden trigger coverage.

DimensionReasoningScore

Specificity

Quotes like "Korean Seedance 2.0 prompt wording" and "translation of camera, lighting, action, VFX, audio, and production terms into Korean" enumerate several concrete deliverable categories (wording, vocabulary, translation across six term families). It falls short of a 5 because the actions are near-synonymous variants of one capability (produce/translate Korean wording) rather than multiple distinct actions like extract, fill, and merge.

4 / 5

Completeness

The when is explicit and concrete ("should be used when the user asks for Korean Seedance 2.0 prompt wording, Korean cinematic vocabulary, or translation of..."), and a what is present via "translation of camera, lighting... terms into Korean". It sits between anchors 4 and 5 rather than clearly at 5 because the capability is only stated inside the trigger clause — the description never independently states what the skill returns (e.g., "Produces Korean prompt wording with...") the way the anchor-5 example does with separate what and when statements.

4 / 5

Trigger Term Quality

Natural phrases a user would actually say are well covered: "Korean Seedance 2.0 prompt wording", "Korean cinematic vocabulary", and the category terms "camera, lighting, action, VFX, audio, and production terms". Not a 5 because common variations users might say (e.g., "Korean video prompt", "bilingual prompt", "translate my shot list to Korean") and any shorter synonym set are absent.

4 / 5

Distinctiveness Conflict Risk

"Korean Seedance 2.0 prompt wording" and "Korean cinematic vocabulary" define a clear niche with distinct triggers; only a general Korean-translation skill could plausibly overlap, and the Seedance 2.0 and cinematic-production scoping keeps conflict risk minimal.

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

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

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