BF seedance-short-drama
Requires OFOX_API_KEY — create one at https://app.ofox.ai. Generate a realistic-human, dialogue-driven short-drama clip — one shot, or a few hard-cut shots inside one job — from a script or scene description using the Ofox video API (Seedance 2.5). Runs a short creative brief when the input leaves beat, aspect ratio, emotional arc or camera register open (one held take, a travelling take, or a multi-shot cut list) ("Let the AI decide" is offered on the taste questions, never on a must-ask one, and never as the default), writes a structured prompt (header manifest, timestamped shots, quoted dialogue with delivery notes, consistency lock), shows a cost estimate, then calls ofox-video-core to submit, poll, download, and report the real cost. Use when a user asks to turn a script beat into video, e.g. "generate scene 3 of this script, two characters talking, 15 seconds", "make a vertical short-drama clip of these two arguing in a kitchen", "turn this dialogue into a 12-second video", or "give me a realistic short-drama shot of a couple breaking up at a train station". Do not use for silent product/brand shots (see seedance-ad-creative), for anime- or manga-styled scenes (see seedance-anime-drama), or for anything not involving people/dialogue.
Requires OFOXAPIKEY — create one at https://app.ofox.ai. Generate a realistic-human, dialogue-driven short-drama clip — one shot, or a few hard-cut shots…
As a process F 41/100 · Will not run — References files that are not bundled: ../ofox-video-core/SKILL.md, ../ofox-video-core/references/creative-brief.md, ../ofox-video-core/references/prompt-structure.md
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.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1259 chars, limit 1024 - warning
body-longSKILL.md body ≈ 16914 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../ofox-video-core/SKILL.md - warning
missing-refreference to a missing file: ../ofox-video-core/references/creative-brief.md - warning
missing-refreference to a missing file: ../ofox-video-core/references/prompt-structure.md - warning
missing-refreference to a missing file: ../ofox-video-core/references/approval-gate.md - warning
missing-refreference to a missing file: ../ofox-video-core/references/api-params.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 41/100
- 0Tools and files. 5 referenced file(s) missing: ../ofox-video-core/SKILL.md, ../ofox-video-core/references/creative-brief.md, ../ofox-video-core/references/prompt-structure.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 16914 tokens: crowds the task out of the window
- 30Running it twice. 24 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 85Steps. 17 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 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
- +3Description length 1259: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Description says when NOT to use the skill
- +4Structure: 35 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (13 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 43.