FD seedance-product-video
Requires OFOX_API_KEY — create one at https://app.ofox.ai. Generate a clean, catalog-style e-commerce product video from a real product photo (or, for a generic or fictional product, a text description) using the Ofox video API (Seedance 2.5) — runs a short creative brief (product photo, target platform and aspect ratio, background, camera orbit or turntable) when the request leaves them open, writes a plain-background, literal-accuracy prompt (precise product description, a simple camera orbit or turntable motion, no dramatic cinematography), 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 product photo into catalog/listing footage, e.g. "make this product photo a 360-degree white-background showcase", "turn this photo into a white-background product video", "make a clean turntable video of this item", or "give me a 5-second white-background rotation video of this product for my listing". Do not use for cinematic brand/mood advertising (see seedance-ad-creative) or for anything involving people/dialogue (see seedance-short-drama).
Requires OFOXAPIKEY — create one at https://app.ofox.ai. Generate a clean, catalog-style e-commerce product video from a real product photo (or, for a generic…
As a process D 46/100 · Unfinished process — References files that are not bundled: ../ofox-video-core/SKILL.md, ../ofox-video-core/references/prompt-structure.md, ../ofox-video-core/references/creative-brief.md
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 2
-
high Concealment
en-hide-from-userCHANGELOG.md:444Instruction to hide actions from the userit can silently delete a waypoint's content — clip B, plus the new clip's
-
high Concealment
en-hide-from-userSKILL.md:1181Instruction to hide actions from the usermerely crop the picture; it can silently delete part of what a waypoint asks
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1133 chars, limit 1024 - warning
body-longSKILL.md body ≈ 35680 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/prompt-structure.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/api-params.md - warning
missing-refreference to a missing file: ../ofox-video-core/references/approval-gate.md - warning
missing-refreference to a missing file: ../product-image/SKILL.md - warning
missing-refreference to a missing file: ../image-edit/SKILL.md - warning
missing-refreference to a missing file: references/*.md - note
frontmatter-keyunknown frontmatter key "homepage" - note
edit-residuethe text marks something as outdated (lines 113, 131): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 46/100
- 0Tools and files. 8 referenced file(s) missing: ../ofox-video-core/SKILL.md, ../ofox-video-core/references/prompt-structure.md, ../ofox-video-core/references/creative-brief.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 35680 tokens: crowds the task out of the window
- 30Running it twice. 51 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 85Steps. 57 steps, 1 vague phrases
- 100Failures and branches. 9 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 23 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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 1133: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -226 emoji in the instructions: noise for the model
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +4Structure: 44 headings
- +3Step-by-step instructions: 57 items
- +4Has examples (18 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 37.