即梦 / Seedance 商业视频生成
Use this skill to turn references and a business goal into a stable short-video generation workflow. Creative judgment stays in the agent; provider calls, API keys, parameter validation, task status, downloads, storage, credits, and logs stay in MCP/server tools.
Required MCP Tools
| Tool |
Use |
get_project_video_profile |
Read project video defaults, model policy, model catalog, and credit multiplier before planning. |
register_video_reference |
Upload or normalize a text/image/audio/video reference into an OSS-backed, Ark-accessible URL. |
validate_video_generation_params |
Preflight model/ratio/resolution/duration/references and return estimated dynamic credits. |
build_video_generation_plan |
Validate parameters and produce generation-plan.json plus SDK payload preview and estimated credits. |
create_video_generation_task |
Submit the server-side Ark SDK async task. |
query_video_generation_task |
Poll task status and retrieve generated URLs/metadata. |
download_video_generation_result |
Download the completed provider result, upload it to OSS, and register it as a task file. |
Never call Volcengine/Dreamina HTTP APIs directly, never handle API keys, never use fixed global model/credit defaults, and never use the 即梦 CLI as the main execution path. Agents must use MCP tools. Do not treat external @-style labels as the server execution protocol; translate them into reference_role plus MCP references.
Workflow
- Work inside the existing project/plan/task flow. A video generation job is a
video task, not a separate product line.
- Call
get_project_video_profile(project_id) first. Use the returned project defaults, model policy, model catalog, and credit_multiplier; do not hardcode model IDs, default resolution, duration, or fixed credits.
- Prepare the workspace with
prepare_workspace(content_type="video", task_id=...) when available. Local files are temporary Claude workspace artifacts only; anything persistent must become an OSS-backed task file through MCP/server tools.
- Read the relevant references:
- Business structure:
references/methodology.md
- Consistency/retry rules:
references/stability.md
- Artifact and prompt templates:
references/prompt-templates.md
- MCP contract details:
references/mcp-contract.md
- Collect inputs: references for people/objects/scenes, business purpose (
planting, ecommerce, lead_gen, promotion), duration, ratio, resolution, model key, seed/camera preferences. Missing values come from project video profile, not from this skill.
- Register every non-text reference with
register_video_reference. Prefer task_file_id or upload through the platform; for video input, use the returned reference with server-measured input_duration_seconds and never hand-write a raw video_url into plan/create. Raw provider URLs are intermediate only and must not be the main delivery link.
- Write
reference-anchors.md: first declare reference_role for every reference, then separate each reference into must-keep, can-change, and must-not-change anchors.
- Write
script.md: use the 0-3s / 3-10s / 10-13s / 13-15s commercial structure. Do not submit raw marketing copy as a video prompt.
- Write
shot-plan.md: 4-5 shots for 15s by default. Each shot needs subject, action, scene, camera movement, visual focus, and negative constraints.
- Build the final prompt using global anchors + shot instructions + negative constraints. Keep one intent per shot.
- Call
validate_video_generation_params or build_video_generation_plan; save the result to generation-plan.json, including estimated dynamic credits and pricing breakdown. Show/record the estimate before submission.
- Call
create_video_generation_task; save video-task-submit.json.
- Poll with
query_video_generation_task; save every terminal response to video-task-result.json.
- On success, call
download_video_generation_result with task_id so the result is uploaded to OSS and registered as a task file. Save returned task file IDs/URLs to delivery-manifest.json.
- Write
quality-review.md before deciding whether to retry. Score subject consistency, product/scene fidelity, business goal fit, motion clarity, and CTA fit.
Retry Rules
- Subject drift: strengthen
reference-anchors.md; reduce shot count.
- Product shape/color drift: move product descriptors into every product shot; avoid metaphorical phrasing.
- Action chaos: simplify action verbs; one action per shot.
- Scene jumping: repeat scene anchors and set
camera_fixed when appropriate.
- Too ad-like for planting: soften CTA and rewrite script as first-person experience.
- Weak conversion for ecommerce/lead gen: make benefit and CTA more explicit, but keep claims compliant.
- Unsupported model/parameter combo: only use server-returned validation errors or
suggested_params; do not invent a downgrade outside the project policy.
Record every retry in iteration-log.md with changed fields, reason, and result.
1---2name: dreamina-video3description: Use when generating commercial short videos with 即梦, Dreamina, Seedance, Seedance 视频生成, 种草视频, 带货视频, 获客视频, 推广视频, 图生视频, 多模态视频, or when a user provides image/audio/video references and asks for a stable marketing video.4---56# 即梦 / Seedance 商业视频生成78Use this skill to turn references and a business goal into a stable short-video generation workflow. Creative judgment stays in the agent; provider calls, API keys, parameter validation, task status, downloads, storage, credits, and logs stay in MCP/server tools.910## Required MCP Tools1112| Tool | Use |13| --- | --- |14| `get_project_video_profile` | Read project video defaults, model policy, model catalog, and credit multiplier before planning. |15| `register_video_reference` | Upload or normalize a text/image/audio/video reference into an OSS-backed, Ark-accessible URL. |16| `validate_video_generation_params` | Preflight model/ratio/resolution/duration/references and return estimated dynamic credits. |17| `build_video_generation_plan` | Validate parameters and produce `generation-plan.json` plus SDK payload preview and estimated credits. |18| `create_video_generation_task` | Submit the server-side Ark SDK async task. |19| `query_video_generation_task` | Poll task status and retrieve generated URLs/metadata. |20| `download_video_generation_result` | Download the completed provider result, upload it to OSS, and register it as a task file. |2122Never call Volcengine/Dreamina HTTP APIs directly, never handle API keys, never use fixed global model/credit defaults, and never use the 即梦 CLI as the main execution path. Agents must use MCP tools. Do not treat external @-style labels as the server execution protocol; translate them into `reference_role` plus MCP `references`.2324## Workflow25261. Work inside the existing project/plan/task flow. A video generation job is a `video` task, not a separate product line.272. Call `get_project_video_profile(project_id)` first. Use the returned project defaults, model policy, model catalog, and `credit_multiplier`; do not hardcode model IDs, default resolution, duration, or fixed credits.283. Prepare the workspace with `prepare_workspace(content_type="video", task_id=...)` when available. Local files are temporary Claude workspace artifacts only; anything persistent must become an OSS-backed task file through MCP/server tools.294. Read the relevant references:30 - Business structure: `references/methodology.md`31 - Consistency/retry rules: `references/stability.md`32 - Artifact and prompt templates: `references/prompt-templates.md`33 - MCP contract details: `references/mcp-contract.md`345. Collect inputs: references for people/objects/scenes, business purpose (`planting`, `ecommerce`, `lead_gen`, `promotion`), duration, ratio, resolution, model key, seed/camera preferences. Missing values come from project video profile, not from this skill.356. Register every non-text reference with `register_video_reference`. Prefer `task_file_id` or upload through the platform; for video input, use the returned reference with server-measured `input_duration_seconds` and never hand-write a raw `video_url` into plan/create. Raw provider URLs are intermediate only and must not be the main delivery link.367. Write `reference-anchors.md`: first declare `reference_role` for every reference, then separate each reference into must-keep, can-change, and must-not-change anchors.378. Write `script.md`: use the 0-3s / 3-10s / 10-13s / 13-15s commercial structure. Do not submit raw marketing copy as a video prompt.389. Write `shot-plan.md`: 4-5 shots for 15s by default. Each shot needs subject, action, scene, camera movement, visual focus, and negative constraints.3910. Build the final prompt using global anchors + shot instructions + negative constraints. Keep one intent per shot.4011. Call `validate_video_generation_params` or `build_video_generation_plan`; save the result to `generation-plan.json`, including estimated dynamic credits and pricing breakdown. Show/record the estimate before submission.4112. Call `create_video_generation_task`; save `video-task-submit.json`.4213. Poll with `query_video_generation_task`; save every terminal response to `video-task-result.json`.4314. On success, call `download_video_generation_result` with `task_id` so the result is uploaded to OSS and registered as a task file. Save returned task file IDs/URLs to `delivery-manifest.json`.4415. Write `quality-review.md` before deciding whether to retry. Score subject consistency, product/scene fidelity, business goal fit, motion clarity, and CTA fit.4546## Retry Rules4748- Subject drift: strengthen `reference-anchors.md`; reduce shot count.49- Product shape/color drift: move product descriptors into every product shot; avoid metaphorical phrasing.50- Action chaos: simplify action verbs; one action per shot.51- Scene jumping: repeat scene anchors and set `camera_fixed` when appropriate.52- Too ad-like for planting: soften CTA and rewrite script as first-person experience.53- Weak conversion for ecommerce/lead gen: make benefit and CTA more explicit, but keep claims compliant.54- Unsupported model/parameter combo: only use server-returned validation errors or `suggested_params`; do not invent a downgrade outside the project policy.5556Record every retry in `iteration-log.md` with changed fields, reason, and result.
anbanai