Videoagent Director logo

Videoagent Director

Community
pexoai
videoagent-director

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.

Overview

Publisherpexoai
Repositorypexo-skills
Skill namevideoagent-director
Stars
800
Forks
46
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by pexoai on GitHub. Read the source before you install it.

Installation

Install the Videoagent Director AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/pexoai/pexo-skills/tree/main/skills/videoagent-director
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/pexoai/pexo-skills.git /tmp/pexo-skills
mkdir -p .claude/skills
cp -r /tmp/pexo-skills/skills/videoagent-director .claude/skills/videoagent-director
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Videoagent Director in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Videoagent Director on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Videoagent Director is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

🎬 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

LengthShots
15–20 s3–4 shots
30 s5–6 shots
45–60 s7–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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Videoagent Director AI skill do?

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.

Why use Videoagent Director on TypingMind?

Because you install it once and use it with any model. Videoagent Director is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Videoagent Director in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/pexoai/pexo-skills/tree/main/skills/videoagent-director. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Videoagent Director?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Videoagent Director?

As many as you like. As long as a model supports skills, you can use Videoagent Director with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Videoagent Director AI skill free?

Yes. It is published on GitHub by pexoai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇