AC Seedance 2.0 JiMeng Skill (OpenClaw / ClawHub)
Create high-control English prompts for Seedance 2.0 and Seedance 2.0 Fast using multimodal references (image/video/audio/text).
Create high-control English prompts for Seedance 2.0 and Seedance 2.0 Fast using multimodal references (image/video/audio/text).
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
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 61/100
- 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 JiMeng Skill (OpenClaw / ClawHub)) differs from the folder (seedance-2-prompt-engineering-skill)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 66 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 2076 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)
- +1No license
- +2Single-language instructions
- +3Description length 128: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 66 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.