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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seedance-examples-ja/SKILL.md

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, highly actionable set of concrete Japanese Seedance prompt examples with clear labeling and rewrite guidance, well-organized for a self-contained single-purpose skill; the only gap is that the conditional workflow is implicit rather than explicitly sequenced.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, providing concrete Japanese prompt examples and a brief intent note without explaining basic video-generation or prompt concepts Claude already knows.	3 / 3
Actionability	It supplies six concrete, copy-paste-ready Japanese prompt patterns (Product I2V, Portrait micro-performance, Sequence clip 01, Continuation, Dialogue, Textless localization) plus concrete before/after rewrite examples, giving fully actionable guidance.	3 / 3
Workflow Clarity	Decision rules exist via the Example Labels table, Rewrite Pattern, and Output Contract, but the procedure is implicit rather than explicitly sequenced, and there is no validation checkpoint (acceptable here since the task is non-destructive).	2 / 3
Progressive Disclosure	The skill is under 50 lines, self-contained with no external references, and well-organized into clear sections (Intent, Example Labels, Safe Example Patterns, Rewrite Pattern, Output Contract), which satisfies the rubric's simple-skill allowance for a top score.	3 / 3
	Total	11 / 12 Passed

Description

72%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at explicit trigger guidance and distinctiveness, but it reads as a pure "when" clause with the skill's concrete capabilities left implied rather than stated, capping completeness and specificity at the middle level.

Suggestions

Add an explicit "what" clause naming the concrete actions the skill performs (e.g., "Generates and rewrites Japanese Seedance 2.0 video-generation prompt examples") before the "Use when..." trigger, so capabilities are stated rather than implied.

Reduce the repeated "Japanese ..." phrasings and add varied natural trigger terms a user might say (e.g., "rewrite this Seedance prompt in Japanese", "safe Japanese prompt for video generation") to broaden coverage without redundancy.

Dimension	Reasoning	Score
Specificity	The description names a specific domain and output types ("Japanese Seedance 2.0 examples", "example rewrites", "safe versions of working Japanese video-generation prompts"), but presents them as trigger objects rather than concrete capability verbs, so it is not comprehensive.	2 / 3
Completeness	It has a strong explicit "when" clause ("This skill should be used when the user asks for..."), but the "what" is only implied through the listed output types rather than stated as explicit capabilities.	2 / 3
Trigger Term Quality	It covers a good spread of natural phrasings a user would actually say for this niche: "Japanese Seedance 2.0 examples", "Japanese prompt patterns", "example rewrites", and "safe versions of working Japanese video-generation prompts".	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and highly specific (Japanese + Seedance 2.0 + example/rewrite/safe-version prompts), making it clearly distinguishable and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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

	Total	14 / 16 Passed

Repository: Emily2040/seedance-2.0
Path: skills/seedance-examples-ja/SKILL.md
Commit: 6c51262

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.