Produce with Google Veo

Treat a Veo request as a shot-production job, not as a generic text completion. Lock the access route, model, input mode, shot contract, and delivery constraints before generating.

Read evidence labels correctly

• Documented means a current first-party Google API document, model card, policy, or technical report says it.
• First-party evaluation means Google measured or reported it; do not restate it as independent superiority.
• Production heuristic means a practical operating recommendation derived from the documented interface and common shot-production constraints. It is not a provider guarantee.
• Documentation gap means Google's current pages conflict or a generic schema exposes a field that the selected model card does not support. Run a low-cost preflight instead of guessing.

All volatile facts in this skill were verified 2026-07-09. Recheck model lifecycle, quotas, pricing, regional availability, and terms before a paid production run.

Confirm that Veo is the right Google video model

Use Veo for a shot-generation workflow that specifically benefits from Veo's first/last-frame control, asset references, extension, established publisher-model integration, or Veo-native audio contract. Do not use this skill for video understanding or transcription.

Documented current product guidance: Google's Gemini API video overview now recommends Gemini Omni Flash as the default for multimodal coherence, character consistency, factual accuracy, and conversational multi-turn video editing; it positions Veo 3.1 for capabilities such as scene extension, last-frame control, and legacy pipeline integration. Treat that as provider routing guidance, not independent quality proof. If the request is simply “make a video” and does not need a Veo-specific control, compare the current Google video models before committing. See Video generation in the Gemini API.