AF seedance-2-prompt-engineer
Use this skill whenever a user wants to generate, improve, or convert a video prompt for Seedance 2.0. Triggers on: "make a Seedance prompt", "create a video prompt for Seedance", "I want to generate a video", "convert my idea to a Seedance prompt", "help me prompt Seedance", "optimize my video prompt", or any request involving Seedance 2.0 video generation. Also triggers when a user describes a scene, character, or action they want animated and has not yet written a structured prompt. Always use this skill before writing any Seedance 2.0 prompt — do NOT attempt to write one from memory.
As a process F 52/100 · Will not run — References files that are not bundled: references/best-practices.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/best-practices.md
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: references/best-practices.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (seedance-2-prompt-engineer) differs from the folder (seedance-2-prompt-optimizer)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 85Steps. 16 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1358 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 594: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.