Veo Generator

What it does

When your agent uses it

• Tasks that involve AI video generation

Example prompts

• “s shot package (shots/.md), one clip per camera cut, reusing each shot”
• “render the Veo video for <project”
• “generate the videos from the shot scripts”
• “/veo-generator”

Requirements

• A credential in GEMINI_API_KEY
• A credential in VEO_API_KEY

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Dry-run / validate the package (no key spent)
2. 2Plan the render (resolves key + model + outputs, still no API call)
3. 3Render (calls Veo, polls, downloads to video_production/renders/)
4. 4(Optional) regenerate storyboard sketches (the first-frame images) via
5. 5Assemble in post — cut the renders/*.mp4 in timecode order, lay the

What it can do on your machine

Read from SKILL.md and the folder at commit 7a2d171. 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 bash).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • aistudio.google.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • GEMINI_API_KEY
  • VEO_API_KEY
  • GOOGLE_API_KEY

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Veo Generator loads about 1.9k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 853 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~96

When it runs · the whole SKILL.md, loaded when a task matches

~1.9k

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

• NoteMentions a .env fileSKILL.md:16

  .env                      <- (optional) per-project API key lives here

• NoteMentions a .env fileSKILL.md:49

  | 3 | **`<Project>/.env`** or `…/video_production/.env` | **per-project key** |

• NoteMentions a .env fileSKILL.md:50

  | 4 | this package's `.env` | global fallback |

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 BlackBeltTechnology/pi-agent-dashboard at commit 7a2d171, republished under its MIT licence (© BlackBeltTechnology). 853 words, ~1,931 tokens.

name

veo-generator

description

Render a scripted video project into mp4 clips with the Google Veo 3.1 API. Reads a project's shot package (shots/*.md), one clip per camera cut, reusing each shot's prompt and sketch — world anchor only with `--with-reference`, seed unless `--no-seed`. Use on "render the Veo video for <project>", "generate the videos from the shot scripts", "make the clips with Veo".

<Project>/
  .env                      <- (optional) per-project API key lives here
  video_production/
    shots/shot_*.md         <- source of truth: prompt, negative, seed, aspect, refs
    storyboard/*.png        <- first-frame sketches + 00_world_anchor.png
    renders/                <- mp4 output (created here)

© BlackBeltTechnology, 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 1 other file in packages/video-production/.pi/skills/veo-generator of BlackBeltTechnology/pi-agent-dashboard.

• SKILL.md
• .env.example

Open the folder on GitHubat commit 7a2d171