seedance-vfx

This skill should be used when the user asks for VFX, particles, energy, destruction, transformation, weather effects, magical effects, explosions, smoke, fire, water, or physically plausible effects in Seedance 2.0.

Quality

78%

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-vfx/SKILL.md

Quality

Content

85%

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 lean, well-structured instruction-only skill with concrete copy-paste prompt examples and a clear output contract; its only weakness is mild redundancy in restating the physical-plausibility thesis across the opening, Intent, and Effects Contract sections.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids explaining basics Claude already knows, but the source->journey->ending thesis is restated roughly three times (opening paragraph, the Intent section's "source, a journey, and an ending", and the Effects Contract) with mildly florid prose such as "wonder dies the moment it stops obeying physics," so it could be tightened.	2 / 3
Actionability	It supplies copy-paste-ready "Prompt-ready phrase" examples per effect type, concrete integration directives, a `forms -> travels -> dissipates` timing template, and an explicit Output Contract, which is highly actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	As a single-purpose skill, its action is unambiguous: produce the VFX contract, stability constraints, and a prompt-ready phrase, sequenced via the source->journey->endpoint contract with a defined deliverable in the Output Contract; no validation loop is required for non-destructive prompt generation.	3 / 3
Progressive Disclosure	At under 50 lines with no need for external references and no bundle files present, the well-organized sections (Intent, Effects Contract table, Integration Rules, Timing and Dissipation, Output Contract) meet the bar for full marks on progressive disclosure.	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 has strong, natural trigger terms and a distinct Seedance-2.0-bound niche, but it tells the reader when to invoke the skill without ever stating what the skill does, leaving the core capability implied rather than explicit.

Suggestions

Add an explicit action clause stating what the skill does, e.g. "Generates physically grounded VFX prompts for Seedance 2.0 by translating requested effects into source, motion, and dissipation behavior."

Lead with the capability (the "what") before the trigger list so the description answers both halves of completeness.

Consider trimming the long comma-separated effect list into a shorter representative set plus "and similar physical effects" to reduce repetition while keeping triggers natural.

Dimension	Reasoning	Score
Specificity	The description names a concrete, specific domain ("VFX, particles, energy, destruction, transformation, weather effects, magical effects, explosions, smoke, fire, water") rather than vague language, but it lists effect types rather than explicit actions the skill performs, so it does not reach the "multiple specific concrete actions" bar of 3.	2 / 3
Completeness	It provides an explicit and comprehensive "when" clause ("This skill should be used when the user asks for...") but never states what the skill actually does — the action (generate/compose/translate effects) is only implied, so it does not clearly answer both what AND when.	2 / 3
Trigger Term Quality	Terms like "VFX", "particles", "explosions", "smoke", "fire", "magical effects", and "weather effects" are exactly the natural words a user would say when requesting these effects, giving good coverage of likely trigger phrasings.	3 / 3
Distinctiveness Conflict Risk	Binding the triggers to "Seedance 2.0" with effect-specific keywords carves out a clear niche that is unlikely to conflict with non-Seedance or non-VFX skills.	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-vfx/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.