CB seedance-prompts
Write effective prompts for Seedance 2.0 (bytedance/seedance-2.0) multimodal video generation — the official basic prompt formula (Subject+Motion required; Environment/Aesthetics/Camera/Audio optional), the @ reference system (@Image1/@Video1/@Audio1 role assignment, equivalent to the guide's plain Image 1/Video 1), camera-language vocabulary, time-segmented prompt structure, in-video text (slogans/titles, subtitles, speech bubbles), and capability-specific patterns (character consistency, camera/effects replication, video extension, editing, track completion / multi-clip stitching, music beat-matching, dialogue, one-take, e-commerce, educational). A craft overlay on the art-director step: the output prompt is fed to `ralphy generate video --model bytedance/seedance-2.0`, never to a provider API directly. USE WHEN the user is generating video with seedance and needs a prompt drafted or improved, asks "write a seedance prompt", "how do I reference my uploaded image/video in the prompt", wants beat-synced cuts / camera replication / video extension on seedance, or the art-director playbook has already picked seedance for the job (stylized motion, horror/POV/walking, non-default physics). DO NOT FIRE for model SELECTION (that is MODELS.md + the art-director playbook), for Kling/Veo prompt drafting, or for photoreal-human i2v anchors (seedance's compliance filter blocks them — route to kling-v3.0-pro instead).
Write effective prompts for Seedance 2.0 (bytedance/seedance-2.0) multimodal video generation — the official basic prompt formula (Subject+Motion required…
As a process B 70/100 · Nearly there — weak spots: running it twice, progress reporting
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1429 chars, limit 1024 - warning
body-longSKILL.md body ≈ 6669 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "namespace"
Process rating: all ten parameters 70/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 10 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Steps. 64 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6669 tokens
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
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)
- +3Description length 1429: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Structure: 57 headings
- +3Step-by-step instructions: 64 items
- +3Output format is stated explicitly
- +4Has examples (26 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.