Qwen Video Generation

Generate videos using Wan models. All tasks are asynchronous — submit, then poll until completion. This skill is part of qwencloud/qwencloud-ai.

⚠️ Critical Parameter Differences:

• kf2v (First+Last Frame): Duration is fixed at 5 seconds — other values will fail. Output is silent only.
• Resolution parameters vary by model family, not mode alone: Fetch the current model catalog before choosing size, resolution, or ratio.

Skill directory

Use this skill's internal files to execute and learn. Load reference files on demand when the default path fails or you need details.

Security

NEVER output any API key or credential in plaintext. Always use variable references ($QWENCLOUD_API_KEY in shell, os.environ["QWENCLOUD_API_KEY"] in Python). The scripts accept QWENCLOUD_API_KEY, then QWEN_API_KEY, then DASHSCOPE_API_KEY. Any check or detection of credentials must be non-plaintext: report only status (e.g. "set" / "not set", "valid" / "invalid"), never the value. Never display contents of .env or config files that may contain secrets.

When the API key is not configured, NEVER ask the user to provide it directly. Instead, help create a .env file with a placeholder (QWENCLOUD_API_KEY=sk-your-key-here) and instruct the user to replace it with their actual key from the QwenCloud Console. Only write the actual key value if the user explicitly requests it.

Key Compatibility

Scripts support both standard QwenCloud API keys (sk-...) and Token Plan keys (sk-sp-...). Token Plan keys are automatically routed to the Token Plan endpoint for supported video models — see Token Plan Support below.

Token Plan: do not use curl; always use the bundled Python script.

Coding Plan keys (also sk-sp- prefix but purchased via Coding Plan subscription) cannot be used — video generation models are not available on Coding Plan. Video generation incurs per-second charges on standard keys. The script detects key type at startup and routes accordingly. If qwencloud-ops-auth is installed, see its references/codingplan.md for full details.

Detect the API key type without exposing the key:

python3 -c "
import sys; sys.path.insert(0, 'scripts')
from qwencloud_lib import detect_api_key_type
print(detect_api_key_type('scripts/qwencloud_lib.py'))
"

For Token Plan, fetch and read the current Token Plan model catalog, then use an exact listed model. If CDN access fails, use the local fallback.

Mode Selection Guide

Model Selection

🚫 CRITICAL — Never override user-specified parameters. If the user explicitly specifies a model (in prompt or request JSON), you MUST use exactly that model. Do NOT:

• Replace it with a "better suited" or newer model (e.g., swapping the user's wan2.6-t2v for wan3.0-video because the task "looks like an all-in-one job")
• Replace or restructure their input fields (e.g. converting a user-specified img_url/media arrangement) unless required by the chosen model's documented format — and if a conversion is required, keep the user's media order and content intact
• Add parameters the user did not ask for (prompt_extend, shot_type, style hints) — note shot_type: "multi" REQUIRES prompt_extend: true, but only when the user actually requested multi-shot
• "Optimize" any explicit user choice (duration, size, resolution, prompt)

Selection guidance below applies only when the user has NOT specified a model.

1. User specified a model → MANDATORY: use that exact model — do not substitute, do not "optimize", do not add unrequested parameters.
2. Consult the qwencloud-model-selector skill when model choice depends on capability, scenario, or pricing.

Models

Before selecting, recommending, or defaulting a model, fetch and read the current QwenCloud video-generation model catalog. It contains the model list, basic model information, mode recommendations, compatibility notes, and defaults. If CDN access fails, use the local fallback.

⚠️ Important: The model catalog is a point-in-time snapshot and may be outdated. Model availability changes frequently. Always check the official model list for the authoritative, up-to-date catalog before making model decisions.

Model details: For more information about a specific model, direct the user to https://www.qwencloud.com/models/<model-name>. Replace <model-name> with the exact model ID; never modify or guess it.

Dynamic model queries: If the qwencloud-model-selector skill or QwenCloud CLI (qwencloud models info <model>) is available, use it for real-time model data. CLI requires authentication — see the qwencloud-usage skill for login flow.

Execution

⚠️ Multiple artifacts: When generating multiple files in a single session, you MUST append a numeric suffix to each filename (e.g. out_1.mp4, out_2.mp4) to prevent overwrites.

Prerequisites

• API Key: Check QWENCLOUD_API_KEY, QWEN_API_KEY, then DASHSCOPE_API_KEY using a non-plaintext check only (e.g. in shell: [ -n "$QWENCLOUD_API_KEY" ]; report only "set" or "not set", never the key value). If not set: run the * qwencloud-ops-auth* skill if available; otherwise guide the user to obtain a key from QwenCloud Console and set it via .env file ( echo 'QWENCLOUD_API_KEY=sk-your-key-here' >> .env in project root or current directory) or environment variable. The script searches for .env in the current working directory and the project root. Skills may be installed independently — do not assume qwencloud-ops-auth is present. Note: The script auto-loads .env from the current directory and the project root (in addition to any exported environment variable). A shell check showing $QWENCLOUD_API_KEY as "not set" does NOT mean the script will fail — it may still find the key in .env. Treat the shell check as informational only; the authoritative test is simply running the script (it exits with a clear error if no key is found anywhere).
• Python 3.9+ (stdlib only, no pip install needed)
• For media merging (concat, trim, audio overlay): see merge-media.md for ffmpeg/moviepy recipes suited to the user's environment

Environment Check

Before first execution, verify Python is available:

python3 --version  # must be 3.9+

If python3 is unavailable or below 3.9, PAYG may use Path 2 (curl); Token Plan must install Python 3.9+ instead.

Default: Run Script

Script path: Scripts are in the scripts/ subdirectory of this skill's directory (the directory containing this SKILL.md). You MUST first locate this skill's installation directory, then ALWAYS use the full absolute path to execute scripts. Do NOT assume scripts are in the current working directory. Do NOT use cd to switch directories before execution.

Execution note: Run all scripts in the foreground — wait for stdout; do not background.

Discovery: Run python3 <this-skill-dir>/scripts/video.py --help first to see all available arguments.

python3 <this-skill-dir>/scripts/video.py \
  --model wan2.6-t2v \
  --request '{"prompt":"A detective in a rainy city at night","size":"1280*720","duration":5}' \
  --print-response

# Image-to-animation (no prompt): transfer dance moves from reference video to a character
python3 <this-skill-dir>/scripts/video.py \
  --model wan2.2-animate-move \
  --request '{"image_url":"https://example.com/character.jpg","video_url":"https://example.com/dance.mp4","mode":"wan-std"}' \
  --print-response

Verify Result

• Exit code 0 + response has output.task_id → submission success
• Poll reaches task_status: SUCCEEDED → generation complete
• Non-zero exit, HTTP error, or FAILED status → fail
• Post-execution check: Verify the output video file exists and has non-zero size (ls -la <output_dir>)
• MANDATORY — stderr signal check: After confirming the result, scan the command's stderr output for [ACTION_REQUIRED] or [UPDATE_AVAILABLE]. If either signal is present, you MUST follow the instructions in Update Check below before responding to the user.

On Failure

If the script fails, match the error output against the diagnostic table below to determine the resolution. If no match, read execution-guide.md for alternative paths: curl commands (Path 2 — all 5 modes), code generation (Path 3), and autonomous resolution (Path 5).

If Python is not available at all → PAYG may use Path 2 (curl); Token Plan must install Python 3.9+.

Request Fields Summary

All modes require prompt except animate (no prompt) and videoedit for wan2.7 (prompt optional). See request-fields.md for full field tables per mode.

⚠️ Resolution Parameters by Model Family (Critical)

The resolution field varies by model family. Check the model catalog above before choosing between size, resolution, and ratio; using the wrong field can cause the API call to fail.

Mode-Specific Required Fields

• Required fields vary by model family. Use request-fields.md for payload shapes and the model catalog above for current model-specific compatibility.

Cost Estimation

🚨 NEVER guess or fabricate any price figure. Always direct the user to the official pricing page for exact rates.

Cost is billed per second of generated video. Price varies by model and resolution. Fetch the CDN model-pricing reference, and use the official pricing page for exact current rates. Some models may offer a limited free quota — do not assume any call is free; use the qwencloud-usage skill to check remaining free tier quota, or verify in the user's QwenCloud console. If CDN access fails, use the local fallback.

To check actual usage and bills: use the qwencloud-usage skill, or visit the console: Usage Analytics | Pay-as-you-go Billing | Coding Plan Billing

NEVER fabricate, guess, or construct usage/billing/console URLs. Only provide the exact links listed in this skill. If a URL is not listed here, do not invent one.

Local File Handling

When the user provides local file paths (images, videos, audio), pass them directly to the script. The script automatically uploads local files to DashScope temporary storage (oss:// URL, 48h TTL) and injects the X-DashScope-OssResourceResolve: enable header. No manual upload step is needed.

Production: Default temp storage has 48h TTL and 100 QPS upload limit — not suitable for production, high-concurrency, or load-testing. To use your own OSS bucket, set QWEN_TMP_OSS_BUCKET and QWEN_TMP_OSS_REGION in .env, install pip install alibabacloud-oss-v2, and provide credentials via QWEN_TMP_OSS_AK_ID / QWEN_TMP_OSS_AK_SECRET or the standard OSS_ACCESS_KEY_ID / OSS_ACCESS_KEY_SECRET. Use a RAM user with least-privilege (oss:PutObject + oss:GetObject on target bucket only). If qwencloud-ops-auth is installed, see its references/custom-oss.md for the full setup guide.

Cross-Skill Chaining

When using output from another skill as input (e.g., image-gen → i2v, audio-tts → audio overlay):

• Pass the URL directly (e.g., "img_url": "<image_url from image-gen>") — do NOT download and re-pass as local path
• The script detects URL prefixes (https://, oss://) and passes them through without re-upload
• Use local_path from the response only for user preview or non-API operations

When passing this skill's output to another skill (e.g., vace edit, vision analyze):

• Pass video_url from the response — do NOT download and re-pass as local path

Important Notes

• Async only: All video APIs require X-DashScope-Async: enable header.
• kf2v: Uses a different API endpoint. Duration fixed at 5s, silent only.
• r2v: Use character1/character2/... in prompt. Up to 5 references (max 3 videos).
• vace: Must specify function. Silent only, output ≤5s.
• Multi-shot: Set shot_type: "multi" AND prompt_extend: true.
• Video URL expires in 24h — the script auto-downloads to --output dir. When chaining to another skill (e.g., vace edit), pass video_url directly — do NOT re-download.
• For advanced workflows → see workflows.md.

Error Handling

Output Location

Prefer the current working directory. Default subdirectory: ./output/qwencloud-video-generation/.

Write prohibition: NEVER write output files into this skill's installation directory or any skills/ hierarchy. All generated content must go to output/ under the current working directory or a user-specified path.

Token Plan Support

Token Plan supports only a subset of video models. Fetch and read the current Token Plan model catalog before selecting or validating a model. If CDN access fails, use the local fallback.

Only modes with a compatible model in the current Token Plan catalog can use Token Plan. A request for another mode may return a service error; do not silently switch the requested model or mode.

For a Token Plan kf2v request when the catalog has no compatible kf2v model, stop before submitting. Explain that the selected model requires PAYG, then ask the user to choose either a PAYG key already configured for this request or a change to the requested outcome that a Token Plan-supported mode can fulfill.

⚠️ Credits warning: Video generation consumes significantly more Credits per call than text conversations. A single video may use hundreds of Credits depending on duration and resolution. Check your remaining quota before generating.

Required header

User-Agent: qwencloud-skills is automatically included.

Update Check (MANDATORY Post-Execution)

After script execution, check stderr for action signals. The script automatically detects update status and emits structured signals. You MUST act on them. This section also applies when the user explicitly asks to check for updates.

Signal: [ACTION_REQUIRED] qwencloud-update-check skill is not installed

When stderr contains this signal, you MUST present the following options to the user and wait for their response before proceeding. Do NOT silently skip this.

The update-check skill is not installed. It keeps you informed about new qwencloud/qwencloud-ai features and bug fixes.

1. Install now — I'll run the install command for you
2. Skip for now — do nothing this time
3. Never remind me — permanently suppress this prompt

After the user responds:

• User chooses 1 → run: npx skills add QwenCloud/qwencloud-ai --skill qwencloud-update-check -y, then run: python3 <this-skill-scripts-dir>/gossamer.py --dismiss
• User chooses 2 → run: python3 <this-skill-scripts-dir>/gossamer.py --dismiss, then continue normally
• User chooses 3 → run: python3 <this-skill-scripts-dir>/gossamer.py --never-install, then continue normally

Signal: [UPDATE_AVAILABLE]

When stderr contains this signal, you MUST append a brief update notice to your response, including the version info and the update command shown in the stderr output.

No signal in stderr

If stderr contains neither [ACTION_REQUIRED] nor [UPDATE_AVAILABLE], no action is needed — the skill is installed and up to date (or cached within 24h).

Explicit user request

When the user explicitly asks to check for updates (e.g. "check for updates", "check version"):

1. Look for qwencloud-update-check/SKILL.md in sibling skill directories.
2. If found — run: python3 <qwencloud-update-check-dir>/scripts/check_update.py --print-response and report the result.
3. If not found — present the install options above.

References

• execution-guide.md — Fallback paths (curl for all modes, code generation, autonomous)
• request-fields.md — Detailed field tables by mode + audio handling
• workflows.md — Duration extensions, audio workarounds, multi-shot, VACE pipelines
• polling-guide.md — Polling patterns and timing recommendations
• merge-media.md — Guide for generating merge/trim/audio-overlay code
• examples.md — Full script execution examples for all modes
• sources.md — Official documentation URLs