CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seedance-examples-ja

This skill should be used when the user asks for Japanese Seedance 2.0 examples, Japanese prompt patterns, example rewrites, or safe versions of working Japanese video-generation prompts.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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, highly actionable body whose concrete Japanese example patterns, label taxonomy, and rewrite mappings are exemplary for an examples-style skill. The structural weakness is its reliance on two reference files hosted outside the skill directory with non-standard relative paths, which undermines the skill's self-containment and makes the referenced material unverifiable.

Suggestions

Move the referenced files (directors-read.md, multilingual-native-review.md) into the skill's own references/ directory and link them with standard in-bundle relative paths (e.g., references/directors-read.md) so the skill is self-contained.

If the Director's Read record format is essential to the workflow, inline a minimal template or summary of its canonical record fields, since the current body instructs 'complete its canonical narrative or non-narrative record' with no fallback if the external file is unavailable.

Tighten the 'Intent' section to a single prescriptive line (e.g., 'Write examples as production notes: polite, compact, every emotion expressed as framing/light/motion/sound') to remove the remaining editorial padding.

DimensionReasoningScore

Conciseness

The ~40-line body is dense and example-driven with almost no explanation of concepts Claude already knows; the 'Intent' section ('should feel like production notes a Japanese creator could actually use…') is soft editorial guidance that could be trimmed to one line.

4 / 5

Actionability

Six complete, copy-paste-ready Japanese prompt patterns (product I2V, portrait micro-performance, sequence, continuation, dialogue, textless localization) plus concrete rewrite mappings ('有名キャラクターそのもの' → 'オリジナルの仮面をつけた屋上配達員'), a label table, and a defined output contract cover the common cases fully.

5 / 5

Workflow Clarity

A coherent sequence is stated up front ('load the Director's Read → classify the brief → complete its canonical record → translate into carriers → keep internal labels out of final prose') with a language-review checkpoint ('use multilingual language review for that review'); it is prose rather than numbered steps, and no explicit verify-before-proceeding loop exists, keeping it below the anchor-5 example.

4 / 5

Progressive Disclosure

Sections are well-organized, but both external references use '../../references/…' — paths that escape the skill's own directory — and no references/ bundle directory exists here, so the linked files (directors-read.md, multilingual-native-review.md) are neither self-contained nor verifiable within the skill, which the rubric treats as references that are not clearly organized for discovery.

3 / 5

Total

16

/

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 strong, trigger-explicit description for a well-defined niche: it names concrete deliverables and a clear 'use when' clause. Its main gap is that it describes what the user asks for rather than what the skill actually does, leaving the capability statement implicit.

Suggestions

Add explicit capability verbs up front, e.g., 'Generates and rewrites Japanese Seedance 2.0 video-generation prompt examples…', so the 'what' is stated rather than implied by the trigger clause.

Include one or two natural synonym triggers users might type, such as '日本語プロンプト' or 'Seedance prompt in Japanese', to widen trigger coverage without adding bulk.

DimensionReasoningScore

Specificity

The description names the domain and several concrete deliverables — 'Japanese Seedance 2.0 examples', 'Japanese prompt patterns', 'example rewrites', 'safe versions of working Japanese video-generation prompts' — but never states an explicit action (e.g., 'Generates…', 'Rewrites…'), so it stops short of the comprehensive multi-action anchor.

4 / 5

Completeness

The 'when' is explicit and well-formed ('This skill should be used when the user asks for…'), and the deliverable nouns imply the 'what', but unlike anchor-5 examples the description never explicitly states what the skill does — no capability verbs — so the 'what' remains partly implicit.

4 / 5

Trigger Term Quality

'Japanese Seedance 2.0 examples', 'prompt patterns', 'example rewrites', 'safe versions', and 'video-generation prompts' are phrases a user would naturally say, but common variations and synonyms (e.g., '日本語', 'Seedance prompts', 'JP localization') are absent.

4 / 5

Distinctiveness Conflict Risk

'Japanese Seedance 2.0' video-generation examples is a narrow, clearly-delineated niche with distinctive trigger terms; only trivial overlap with a generic Seedance or non-Japanese examples skill could occur.

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

Warning

Total

13

/

16

Passed

Repository

Emily2040/seedance-2.0

Path

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