CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-vocab-ja

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

Quality

80%

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

Quality

Content

68%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 an efficient, largely actionable overview: concrete vocabulary tables, an adaptable compact pattern, and clearly signaled one-level-deep references. Its main weaknesses are an implicit, checkpoint-free workflow dispersed across prose and reference paths that point outside the bundle and cannot be verified.

Suggestions

Express the core procedure (load Director's Read → classify the brief → complete the record → translate into carriers → apply the Output Contract) as a short numbered list in one place, so the sequence and its ordering are explicit rather than implied across prose sections.

Fix the reference paths (../../references/directors-read.md, ../../references/surface-prompt-profiles.md, ../../references/vocab/ja.md) to point inside the skill bundle, or ship the referenced files, so navigation from SKILL.md actually resolves.

Trim meta-commentary such as "The shipped independent review artifact is empty, so treat these choices as working production wording pending locale-specialist review" — it does not instruct the model and costs tokens.

DimensionReasoningScore

Conciseness

The vocabulary table and compact pattern are tight and every entry earns its place, with only minor trimmable material such as the meta-sentence "The shipped independent review artifact is empty, so treat these choices as working production wording pending locale-specialist review" and some convoluted rule prose.

4 / 5

Actionability

Concrete, usable guidance: the Function/Japanese wording table, the copy-adaptable compact pattern, and specific rules like "Preserve actual reference tags exactly" and "Measure the actual spoken line; do not use a fixed multiplier". Not a 5 because the opening directives ("classify the brief, and complete its canonical narrative or non-narrative record") depend on external files and leave minor executable gaps.

4 / 5

Workflow Clarity

A rough sequence exists (load Director's Read → classify the brief → complete the record → translate into carriers → follow the Output Contract) but it is spread across prose with implicit ordering and no validation checkpoints. Score 4 would require most checkpoints present; 2 would require the sequence itself to be poorly defined.

3 / 5

Progressive Disclosure

The short body pushes detail to clearly signaled, section-anchored references (directors-read.md, surface-prompt-profiles.md#using-reference-examples, vocab/ja.md) one level deep. Not a 5: the ../../references/... paths point outside the skill directory and no bundle files exist to verify, a minor but real organization gap.

4 / 5

Total

15

/

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 description: it explicitly covers both what the skill provides and when to use it, with concrete, natural trigger terms covering the major term categories. It is specific to a clear niche and would reliably fire only on Japanese Seedance prompt/vocabulary requests.

DimensionReasoningScore

Specificity

Names the domain plus several concrete deliverables — "Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese" — with comprehensive term-category coverage. Not a 5 because it states requested scope rather than distinct capability actions, a minor gap.

4 / 5

Completeness

Explicitly answers both: "when" via "This skill should be used when the user asks for..." and "what" via Japanese prompt wording, cinematic vocabulary, and translation of enumerated term categories. A score of 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say: "Japanese... prompt wording", "cinematic vocabulary", "camera, lighting, action, VFX, audio", "production terms", "into Japanese". Missing a few natural variations (e.g., 日本語, bilingual, dialogue), so good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche — Japanese-language Seedance 2.0 cinematic/production vocabulary — with distinct, specific triggers and minimal overlap risk with generic translation or video skills.

5 / 5

Total

18

/

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-ja/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.