BD Seedance 2.0 Guide - Cinematic Storyboard & Prompt Director
Professional Seedance 2.0 / Jimeng (即梦) Storyboard & Prompt Engineering Guide. Create movie-grade 9:16 vlogs, cinematic AI video prompts, and auto-audio scripts from multimodal inputs. Optimized for Claude Code, Cursor, and OpenClaw.
As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency
The same skill appears in 1 more place: ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Seedance 2.0 Guide - Cinematic Storyboard & Prompt Director) differs from the folder (seedance-guide)
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 32 steps
- 100Execution cost. Instruction body is 1707 tokens
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 233: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.