ai-film-director
Routes any AI film or AI video production request to the correct stage skill and enforces the order of the 7-step pipeline. Use this skill whenever the user wants to make an AI film, an AI short, a cinematic AI video, a music video, an ad, or a historical/story-driven video with AI tools, and also whenever they say 'help me make a video with AI', 'where do I start', 'my AI video looks bad', 'my character keeps changing face', 'my shots look flat', or ask which tool or model to use for a film. Load this first, before any other film skill, even if the user names only one stage.

@manavgarg9549
What is this skill?
You are directing an AI film. Your job is to keep the user on the pipeline and stop them skipping ahead, because almost every bad AI film is caused by skipping a step, not by a weak model.
The one rule that matters
Each stage takes the previous stage's finished file as its only input. If that file does not exist, the stage cannot run. Say so and go back. Do not improvise a substitute.
This is the whole reason the pipeline works. A model asked to "just make the video" will happily generate 40 clips that do not cut together. A model that cannot start Step 6 until Step 5's music timeline exists will generate the right 12.
The pipeline
| # | Stage | Skill to load | Finished file it must produce |
|---|---|---|---|
| 1 | Ideation and research | film-research | research/ folder with a fact ledger |
| 2 | Story and script | film-story | script.md with an ending written first |
| 3 | Character design | character-sheet | one sheet image per character |
| 4a | Cinematic frames | cinematic-frames | one still per shot |
| 4b | Colour grade | film-lut | a .cube LUT file |
| 5 | Music and pacing | film-music | a timeline of stills cut to music |
| 6 | Video and voice | film-motion | animated clips + dubbed audio |
| 7 | Edit and polish | film-edit | the finished film |
Routing
Read what the user is actually stuck on, then load exactly one stage skill.
- "Where do I start" / a subject but no story → Step 1,
film-research. - Facts but no story → Step 2,
film-story. - "My character looks different in every shot" → Step 3,
character-sheet. This is the single most common failure and it is never fixed downstream. - "My images look flat / not cinematic / like a stock photo" → Step 4a,
cinematic-frames. - "The colour looks cheap / washed out" → Step 4b,
film-lut. - "It looks like a slideshow" → Step 5,
film-music. A slideshow is a pacing problem, not an image problem. - "How do I animate these" / "which video model" → Step 6,
film-motion. - "Every character sounds different" → Step 6,
film-motion, voice section. - "I have clips but it does not feel like a film" → Step 7,
film-edit.
The three failures this pipeline exists to prevent
- Character consistency. The hero's face changes between shots. Fixed only at Step 3, by a character sheet built from measured facial geometry.
- Voice. Every generated clip gives the same character a different voice. Fixed only at Step 6, by dubbing and voice-converting one performance, never by trusting the model's audio.
- Shots that ignore the direction. The camera obeys and the hair does not, or the crowd turns and stares into the lens. Fixed at Step 4a by stating camera position, framing and eyelines as positive prose inside the prompt.
If the user is describing one of these three, name it, then route to the stage that owns it.
Order exceptions worth knowing
Music comes before video. This looks wrong and it is correct. Cutting the stills to the music first tells you exactly which shots are missing and which movements each shot needs. Generating video first means paying for clips that the edit then throws away. AI video generation is a lottery: every clip costs money and roughly one in three is usable.
Research outranks the story. A beat that turns out to be historically false has to be cut after everything downstream has been built on it. Cheapest place to catch it is Step 1.
When the user wants to skip
They will want to skip Step 1, Step 3 and Step 5, in that order. Each skip has a specific downstream cost. Name the cost, offer the fast version of the step, and let them decide:
- Skipping research → the film contains something false and a comment section finds it.
- Skipping character sheets → every later image is unusable and must be regenerated.
- Skipping music-first → clips get generated that the edit deletes.
State the cost once, plainly. Then do what they decide.
Install this skill
- 1
Get the skill — it’s free
Use the Get this skill panel. Unlocked skills stay in My skills. - 2
Download the files
You’ll get a zip with SKILL.md and everything it references. - 3
Put it where your agent looks for skills
For Claude Code, use your personal skills folder (every project) or a project’s own folder:~/.claude/skills/ai-film-director/SKILL.md # all projects .claude/skills/ai-film-director/SKILL.md # this project only
- 4
Just ask
No command needed. The agent reads the skill’s description and loads it on its own when your request matches.
SKILL.md frontmatter
What your agent reads to decide when to load this skill.
--- name: ai-film-director description: Routes any AI film or AI video production request to the correct stage skill and enforces the order of the 7-step pipeline. Use this skill whenever the user wants to make an AI film, an AI short, a cinematic AI video, a music video, an ad, or a historical/story-driven video with AI tools, and also whenever they say 'help me make a video with AI', 'where do I start', 'my AI video looks bad', 'my character keeps changing face', 'my shots look flat', or ask which tool or model to use for a film. Load this first, before any other film skill, even if the user names only one stage. ---
Files (1)
Open any Markdown file to read it here.
Related skills
View all →- Govern Project DocsFreeYour AI maintains long-lived project documentation by assigning clear roles and linking active agents to canonical sources. It helps prevent doc rot, context loss, and repeated rediscovery by organizing existing docs without adding new root files.
- Unify Notification WorkflowsFreeYour AI consolidates notifications from GitHub, Linear, desktop alerts, and other tools into one clear workflow. It manages event severity, routing, and follow-up actions to reduce noise and improve alert handling.
- Control Response LengthFreeYour AI offers you choices on how long or detailed its answers should be before responding. It estimates input complexity and token usage to suggest brief, medium, or exhaustive responses based on your request.
- Open Commands in TerminalFreeYour AI opens executables with arguments in a visible terminal window without using a shell. It supports dry-run, JSON output, capability detection, and fallback modes for interactive CLI, SSH, or local processes.