Individual skill
vidu-video
Plan and integrate ShengShu Vidu Open Platform video generation with current model/mode selection, reference consistency, pricing, exact approval, async task handling, and safe artifact custody. Use for Vidu API text-to-video, image-to-video, start/end-frame, multi-subject reference, media-reference, or Q2 multi-frame work; do not conflate the API with vidu.com consumer plans or Vidu-S1 streaming digital humans.
skills/providers/video-generation/vidu-video/SKILL.md
Source commit 8c85352d5d75d4dcbe58480bd138e37b9742bab1
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 238
- Repository last updated
- Jul 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- agentic-ai Repository topic
- ai Repository topic
- ai-audio Repository topic
- ai-video Repository topic
- claude Repository topic
- codex Repository topic
- copilot Repository topic
- cursor Repository topic
- generative-media Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Vidu video
Use this skill to design a production request or integration for the **Vidu Open Platform API**. Default to dry-run planning. Never submit a paid generation, upload private media, cancel a task, or download a result until the operator has approved the exact provider, endpoint, model, inputs, request digest, maximum charge, storage destination, and disclosure plan.
This document was verified against first-party public documentation on **2026-07-10**. Models, prices, accepted fields, policies, and availability are volatile; re-open the linked endpoint and pricing pages immediately before execution.
## Keep the surfaces separate
- **Open Platform API:** `https://api.vidu.com`, API keys, organization-level limits, asynchronous tasks, and API credits. This is the surface covered here.
- **Vidu consumer product:** `https://www.vidu.com` and its subscription/plan credits. Do not assume its credits, features, watermark behavior, or terms apply to the API.
- **Vidu-S1 (Beta):** a separate interactive digital-human product using HTTP session setup, AliRTC media, and WebSocket control. It is not a Q3/Q2 clip model. Its public page currently mixes “1 minute to 2 hours” marketing language with a 600-second session maximum. Its pricing section separately says 3 S1 credits per 2 seconds, lists a `0.03125` credit unit price, deducts every 6 seconds, rounds to 2-second intervals, and requires at least 45 credits to create a session. Do not revalue those statements using the clip API's `$0.005` credit price without written confirmation.
- **S1 documentation conflict:** Step 3 says browser WebSocket authentication belongs in the URL query because browsers cannot set custom headers, while the page's Important Notes says it must be in an authorization header. Treat this as unresolved. Confirm the current transport with Vidu before implementation, never place a bearer URL in logs/analytics/referrers, and do not infer a secure browser design from the sample alone.
- **China host:** the S1 page documents `api.vidu.cn` for China and `api.vidu.com` internationally. The ordinary clip endpoints documented here use `api.vidu.com`; do not infer compute residency from the hostname.