Video Gen Usage
OtoDock/oto-dock
Generate AI videos, transitions between clips, and AI video edits.
Create and edit videos using Google's Veo 2 and Veo 3 models.
Install Veo Build
$ npx skills add cnemri/google-genai-skills --skill veo-build -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cnemri/google-genai-skills veo-build --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cnemri/google-genai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/veo-build .claude/skills/veo-build && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "veo-build" agent skill from https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-build into .claude/skills/veo-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "veo-build", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-buildType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cnemri/google-genai-skills --skill veo-build -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cnemri/google-genai-skills veo-build --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cnemri/google-genai-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/veo-build .agents/skills/veo-build && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "veo-build" agent skill from https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-build into .agents/skills/veo-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "veo-build", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cnemri/google-genai-skills --skill veo-build -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cnemri/google-genai-skills veo-build --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cnemri/google-genai-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/veo-build .cursor/skills/veo-build && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "veo-build" agent skill from https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-build into .cursor/skills/veo-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "veo-build", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cnemri/google-genai-skills.git --path skills/veo-build--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cnemri/google-genai-skills --skill veo-build -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cnemri/google-genai-skills veo-build --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cnemri/google-genai-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/veo-build .gemini/skills/veo-build && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "veo-build" agent skill from https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-build into .gemini/skills/veo-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "veo-build", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cnemri/google-genai-skills veo-buildInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cnemri/google-genai-skills --skill veo-build -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cnemri/google-genai-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/veo-build .github/skills/veo-build && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "veo-build" agent skill from https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-build into .github/skills/veo-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "veo-build", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cnemri/google-genai-skills --skill veo-build -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cnemri/google-genai-skills veo-build --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cnemri/google-genai-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/veo-build .opencode/skills/veo-build && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "veo-build" agent skill from https://github.com/cnemri/google-genai-skills/tree/main/skills/veo-build into .opencode/skills/veo-build/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "veo-build", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
veo-build- GitHub stars
- 127
- Token cost
- ~513 tokens
- SKILL.md length
- 183 words
- Files
- 6 (incl. references)
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and edit videos using Google's Veo 2 and Veo 3 models.
- Works in 3 steps: Video Generation (Veo 3) → Video Editing (Veo 2) → Advanced Controls (Veo 3)
- Tasks that involve AI video generation
- SKILL.md covers Quick Start Setup, Reference Materials and Available Workflows
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Veo Build is an agent skill from cnemri/google-genai-skills. Create and edit videos using Google's Veo 2 and Veo 3 models. Supports Text-to-Video, Image-to-Video, Inpainting, and Advanced Controls.
Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/advanced.md`, `references/editing.md` and `references/generation.md`).
It sits in Media & Creative, covering AI video generation. It works with Google Veo. The licence is MIT.
When your agent uses it
- Tasks that involve AI video generation
Example prompts
- “/veo-build”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7277476. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Veo Build loads about 513 tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 37 tokens; SKILL.md has 183 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cnemri/google-genai-skills at commit 7277476, republished under its MIT licence (© cnemri). 183 words, ~513 tokens.
Download SKILL.mdSave it as
.claude/skills/veo-build/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- veo-build
- description
- Create and edit videos using Google's Veo 2 and Veo 3 models. Supports Text-to-Video, Image-to-Video, Inpainting, and Advanced Controls.
Veo Video Generation and Editing
This skill provides comprehensive workflows for using Google's Veo models (Veo 2 and Veo 3) via the google-genai Python SDK.
Quick Start Setup
All Veo operations require the google-genai library and an authenticated client with Vertex AI enabled.
from google import genai
from google.genai import types
import os
PROJECT_ID = os.environ.get("GOOGLE_CLOUD_PROJECT")
LOCATION = os.environ.get("GOOGLE_CLOUD_REGION", "us-central1")
client = genai.Client(vertexai=True, project=PROJECT_ID, location=LOCATION)Reference Materials
- Generation (Veo 3): Text-to-Video, Image-to-Video.
- Editing (Veo 2): Inpainting, Masking.
- Advanced Controls: Frame Interpolation, Video Extension, Reference Images.
- Prompting Guide: Camera angles, visual styles, and best practices.
- Source Code: Deep inspection of SDK internals (
models.py,types.py).
Available Workflows
1. Video Generation (Veo 3)
Create new videos from text or image prompts.
- Text-to-Video: Create videos from detailed text descriptions.
- Image-to-Video: Animate static images.
- Prompt Engineering: Optimization keywords for camera, lighting, and style.
2. Video Editing (Veo 2)
Modify existing videos using masks (Inpainting).
- Remove Objects: Erase dynamic or static objects.
- Insert Objects: Add new elements into a scene.
3. Advanced Controls (Veo 3)
Specialized generation tasks for precise control.
- Frame Interpolation: Generate video bridging two images (first & last frame).
- Video Extension: Extend the duration of an existing video clip.
- Reference-to-Video: Use specific asset images (subjects, products) to guide generation.
© cnemri, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (references) in skills/veo-build of cnemri/google-genai-skills.
- SKILL.md
- references/advanced.md
- references/editing.md
- references/generation.md
- references/prompting.md
- references/source_code.md
Open the folder on GitHubat commit 7277476
Compare with similar skills
Veo Build next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Veo Build this skillcnemri/google-genai-skills | 127 | — | ~513 | Automated safety check: Pass | MIT | |
| Video Gen UsageOtoDock/oto-dock | 190 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Capcutsocial-media-skills/skills | 134 | — | ~2k | Automated safety check: Pass | MIT | |
| Klingsocial-media-skills/skills | 134 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Runwaysocial-media-skills/skills | 134 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Veo Showreel Production KitBlackBeltTechnology/pi-agent-dashboard | 315 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Capcut
social-media-skills/skills
The CapCut craft skill — edit short-form social video (TikTok, Reels, Shorts) fast and safely: retention-paced cuts, auto-captions, beat-synced sound, exports.
Kling
social-media-skills/skills
The generative-video producer for native 4K, multi-shot storyboarding, and motion-transfer (Kling-led).
Runway
social-media-skills/skills
Prompt and direct Runway (Gen-4.5, Aleph) — the control-grade generative video tool for camera moves, character consistency, and edit-grade shots.
Veo Showreel Production Kit
BlackBeltTechnology/pi-agent-dashboard
Turn a video timeline + voiceover into a reproducible, sliceable Veo 3.1 prompt package with a consistency anchor and AI storyboard sketches.
Multimodal LLM
yonatangross/orchestkit
Vision, audio, video generation, and multimodal LLM integration patterns.
More from cnemri/google-genai-skills
All 10 skills in this repoDeep Research
cnemri/google-genai-skills
Perform autonomous, multi-step research using the Gemini Deep Research Agent (Interactions API).
Speech Use
cnemri/google-genai-skills
Generate (TTS), Transcribe (STT), and Clone voices using Google's GenAI and Cloud Speech SDKs.
Veo Use
cnemri/google-genai-skills
Create and edit videos using Google's Veo 2 and Veo 3 models.
Google Developer Knowledge
cnemri/google-genai-skills
Search and retrieve Google's developer documentation using the Developer Knowledge API.
Nano Banana Use
cnemri/google-genai-skills
Generate, edit, and compose images using Gemini Nano Banana models via portable Python scripts.
Google Adk Python
cnemri/google-genai-skills
Expert guidance on the Google Agent Development Kit (ADK) for Python.
Related
Works with
Categories
Questions about Veo Build
What does Veo Build do?
Create and edit videos using Google's Veo 2 and Veo 3 models. Veo Build is an agent skill from cnemri/google-genai-skills. Create and edit videos using Google's Veo 2 and Veo 3 models.
When should I use Veo Build?
Veo Build fits situations like: tasks that involve AI video generation.
How do I install Veo Build in Claude Code?
Run `npx skills add cnemri/google-genai-skills --skill veo-build -a claude-code`. Or copy the skill folder (skills/veo-build in cnemri/google-genai-skills) into .claude/skills/veo-build in your project. Claude Code loads it when a task matches its description.
How do I install Veo Build in Codex?
Run `npx skills add cnemri/google-genai-skills --skill veo-build -a codex`. Or copy the skill folder (skills/veo-build in cnemri/google-genai-skills) into .agents/skills/veo-build in your project. Codex loads it when a task matches its description.
Can I use Veo Build in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cnemri/google-genai-skills --skill veo-build -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/veo-build, .gemini/skills/veo-build, .github/skills/veo-build and .opencode/skills/veo-build in your project.
What does Veo Build need to run?
SKILL.md names no scripts, command-line tools or credentials: Veo Build is instructions for the agent only. Our summary lists: Python 3.
Does Veo Build access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Veo Build safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Veo Build use?
Veo Build is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Veo Build use?
About 513 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.
What are the alternatives to Veo Build?
Skills that share tags, products or a category with Veo Build: Video Gen Usage (OtoDock/oto-dock, 190 stars), Capcut (social-media-skills/skills, 134 stars), Kling (social-media-skills/skills, 134 stars) and Runway (social-media-skills/skills, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Veo Build?
cnemri (a GitHub user) maintains it in cnemri/google-genai-skills, which has 127 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on February 6, 2026.
Source: cnemri/google-genai-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.