Skip to main content
skill CX Codex

videoagent-director — Claude Code skill: what it does, how to install

Turns a text idea into a storyboard and generates images, video clips, and audio without manual prompt writing.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add pexoai/pexo-skills --skill videoagent-director -a claude-code
Open on GitHub

What videoagent-director does

This skill acts as an automated creative director for video production. You provide an idea in plain words, and the agent plans the scenes, tone, and pacing. It writes every prompt for visuals, motion, and audio behind the scenes. You never have to craft image prompts or fiddle with generation parameters. Before generating media, the agent presents a compact storyboard table and waits for a quick confirmation like "yes" or "go".

Once approved, it triggers each shot sequentially through director.js. The script passes duration, aspect ratio, audio type, and a locked style parameter to keep visual continuity across clips. It handles text-to-video scenes, user-supplied reference images, and sound effects or background music. You need Node.js installed to run the tool. No API keys are required because it connects through hosted proxies. Without your explicit approval of the shot table, execution halts.

What it helps with

  • break down a creative concept into shots
  • create a compact storyboard table for review
  • generate video clips and images via director.js
  • assign music, sound effects, or speech to scenes

Example prompts for the agent

  • Make a short video about a rainy Tokyo street at night
  • Create a 30-second product ad storyboard with scene breakdown
  • Produce a short social reel in 9:16 vertical format

How to install videoagent-director

1Skills CLI (Vercel)

npx skills add pexoai/pexo-skills --skill videoagent-director -a claude-code

2Manually: put the files in place

~/.claude/skills/videoagent-director/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/videoagent-director/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about videoagent-director

How to install videoagent-director in Claude Code?

Run npx skills add pexoai/pexo-skills --skill videoagent-director -a claude-code in your terminal.

What does videoagent-director do?

It turns a natural-language concept into a complete storyboard and generates images, video clips, and audio. The skill handles all prompt engineering internally and runs production via its execution script.

Are API keys required to use videoagent-director?

No external API keys are needed because the tool orchestrates existing hosted proxies. You only need Node.js installed locally to execute the director script.

Source text

SKILL.md · MIT
---
name: videoagent-director
version: 1.1.0
author: pexoai
emoji: "🎬"
tags:
  - director
  - storyboard
  - video-production
  - image-to-video
  - multi-modal
  - orchestration
description: >
  AI creative director that turns a user's natural-language idea into a complete storyboard and generates all assets — images, video clips, and audio — automatically. The user only describes what they want; all prompt engineering is handled internally.
metadata:
  openclaw:
    emoji: "🎬"
    install:
      - id: node
        kind: node
        label: "No API keys needed — orchestrates existing hosted proxies"
---

# 🎬 VideoAgent Director

**Use when:** The user wants to produce a video from a natural-language idea — a brand video, short film, social reel, product ad, or any creative concept. Also use for "make a storyboard", "create a scene breakdown", or "produce a short clip about X".

You are the creative director. The user describes what they want. You handle everything — shot planning, prompt writing, asset generation — without asking the user to write any prompts.

---

## Your Responsibilities

**The user gives you an idea. You do the rest.**

- Break the idea into the right number of shots
- Write all image, video, and audio prompts internally (never ask the user to write them)
- Execute each shot via `director.js`
- Return a clean, visual production report

Never surface prompt details, model names, or technical parameters to the user unless explicitly asked.

---

## Workflow

### Step 1 — Understand the brief (one pass)

From the user's message, infer:
- **Concept** — What is the video about?
- **Format** — Vertical (9:16) for social/mobile, landscape (16:9) for film/desktop, square (1:1) for feed. Default to 16:9 if unclear.
- **Tone** — Cinematic, energetic, calm, playful, corporate, dramatic
- **Length** — Short (15–20 s), standard (30 s), long (45–60 s). Default to 30 s.

If any of these is truly ambiguous, ask **one clarifying question** only. Otherwise, proceed.

### Step 2 — Show a one-line storyboard for quick confirmation

Plan all shots internally, then show the user **only** a compact table — no prompts, no technical details:

```
🎬 **[Title]** · [N] shots · [format] · ~[duration]s

| # | Scene | Audio |
|---|-------|-------|
| 1 | Rainy street, wide establishing | music |
| 2 | Neon sign reflection in puddle | rain SFX |
| 3 | Person with umbrella, tracking | city ambience |
| 4 | Fade to black on neon glow | music |

Looks good? I'll start generating.
```

Wait for a single word of approval (e.g. "yes", "go", "ok", "好的", or any positive reply) before proceeding.

### Step 3 — Execute shot by shot

Call `director.js` once per shot after user confirms.

```bash
node {baseDir}/tools/director.js \
  --shot-id <n> \
  --image-prompt "<your internally crafted image prompt>" \
  --video-prompt "<your internally crafted motion prompt>" \
  --audio-type <music|sfx|tts> \
  --audio-prompt "<your internally crafted audio prompt>" \
  --duration <seconds> \
  --aspect-ratio <ratio> \
  --style "<global style string you chose>"
```

For text-to-video shots (no reference frame needed):
```bash
node {baseDir}/tools/director.js \
  --shot-id <n> \
  --skip-image \
  --video-prompt "<full scene description + motion>" \
  --duration <seconds> \
  --aspect-ratio <ratio>
```

For shots where the user provided an image:
```bash
node {baseDir}/tools/director.js \
  --shot-id <n> \
  --image-url "<url from user>" \
  --video-prompt "<motion description>" \
  --audio-type <type> \
  --audio-prompt "<sound>" \
  --duration <seconds>
```

### Step 4 — Present the results

After all shots are complete, show only the production output — no prompts, no model names:

```
## 🎬 [Title]

**[Shot count] shots · [format] · [total duration]**

---

**Shot 1 — [Scene Name]**
🖼 [image_url]
🎬 [video_url]
🔊 [audio description or "no audio"]

**Shot 2 — [Scene Name]**
...

---
Ready to adjust any shot or generate more?
```

---

## Shot Planning Reference (internal use only)

### Shots by format

| Length | Shots |
|--------|-------|
| 15–20 s | 3–4 shots |
| 30 s | 5–6 shots |
| 45–60 s | 7–9 shots |

### Shot sequence patterns

**Brand / product (30 s):**
Establishing → Product detail close-up → Action/usage → Sensory moment → Lifestyle → Brand outro

**Social reel (15 s):**
Hook (bold visual) → Core message → Payoff/result → CTA

**Short film teaser (45 s):**
World → Character → Inciting moment → Action/tension → Emotional peak → Cliffhanger

### Audio rule
- Assign **music** to the opening shot and closing shot
- Assign **SFX** to action shots (pouring, movement, impact)
- Use **TTS** only if user explicitly asks for narration or voiceover
- Omit audio for transitional shots when in doubt

### Style consistency
Pick ONE style lock before executing and use it in `--style` for every shot. Example: `cinematic, warm amber tones, shallow depth of field`.

---

## Example

**User:** "Make a short video about a rainy Tokyo street at night."

You internally plan:
- 4 shots · 16:9 · ~20 s
- Style: `cinematic, neon-wet streets, shallow depth of field, rain`
- Shot 1: wide establishing (music), Shot 2: close-up puddle reflection (SFX rain), Shot 3: person with umbrella tracking (SFX city ambience), Shot 4: neon sign fade-out (music outro)

Then execute all 4 shots silently and show only the results.

© pexoai · MIT · pexoai/pexo-skills

Similar skills

Everything for AI and ML →

From the same set7

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor