director — Claude Code skill: lock the story before you render
director takes a video from idea to shot plan, keeping you in words until the story holds, and only then moves on to shots, camera and light.
no license ★ 301 updated 2026-10-23
npx skills add hoodini/ai-agents-skills --skill director -a claude-codeWhat director does
The skill kicks in for any video job: teaser, ad, promo, short, reel, documentary. It starts by pulling the idea and the script out of you in plain words, and it argues. Three competing concepts means you pick one, not keep all three. No images, no footage, no storyboard art until the concept is approved in words.
Shots come after that: camera, light, sound, cuts. Under references/ sits a 28-chapter director's handbook, and the skill opens the chapter the current stage needs instead of loading the whole thing. It works alongside cinematic-ai-video and yuv-fomo-teaser for style, hyperframes for rendering, nano-banana-2 and ElevenLabs for assets.
The trade-off shows up early. Ask for a finished clip with no discussion and you get turned down, then one sentence on why, then more development. Rewriting a line costs nothing. A render costs time and money.
What it helps with
- lock the idea and script before a single frame is rendered
- break a scene into shots, camera, light and sound
- diagnose why a cut feels flat: want, stakes, turn
- build a teaser or promo for a product launch
- rewrite the script step by step without touching renders
Example prompts for the agent
- Make a short teaser: idea and script first, no frames until I approve.
- The promo script keeps failing. Walk it through your gates and tell me what's missing.
- Plan the shots, camera and light for the final scene.
How to install director
1Skills CLI (Vercel)
npx skills add hoodini/ai-agents-skills --skill director -a claude-code2Manually: put the files in place
~/.claude/skills/director/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/director/
1Skills CLI (Vercel)
npx skills add hoodini/ai-agents-skills --skill director -a codex2Manually: put the files in place
.agents/skills/director/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hoodini/ai-agents-skills --skill director -a cursor2Manually: put the files in place
.cursor/skills/director/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hoodini/ai-agents-skills skills/director2Manually: put the files in place
.github/skills/director/SKILL.md1Skills CLI (Vercel)
npx skills add hoodini/ai-agents-skills --skill director -a gemini-cli2Platform CLI
gemini skills install https://github.com/hoodini/ai-agents-skills --path skills/directorManually: put the files in place
.devin/skills/director/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about director
How do I install director in Claude Code?
Run npx skills add hoodini/ai-agents-skills --skill director -a claude-code. The skill lands at ~/.claude/skills/director/SKILL.md.
What does the director skill do?
It moves a video through stages: idea and script in words first, then shots, camera, light, sound and the edit. Generation waits until the story is approved.
Why won't it generate frames right away?
Its core rule says language is the cheap place to iterate and rendering is the expensive one. It explains the refusal in a sentence and pulls you back to the script.