produce-ai-video
Skill4 starsChanged 3 months agoApache-2.0View on GitHub
Turn an approved script, scene, or story passage into a qualified, watchable AI-generated final video through autonomous script interpretation, directing, multi-shot storyboard design, prompt production, generation, editing, sound, full-playback review, and repair. Use when the user asks Codex to autonomously make, automatically produce, test its ability with, or directly deliver an actual video or finished film rather than only a storyboard or prompt. Preserve user-locked storyboards and structures when the user is directly directing or requests a scoped revision.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- 62656456/ai-film-skillsedited, first seen Sep 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- 62656456/ai-film-skills★ 11553% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- llms.txtllms.txt
- ai-short-drama-productionSkill
- ai-storyboard-directorSkill
- character-assetSkill
- cyberpunk-designSkill
- d-data-analysis-semantic-layerSkill
- director-agentSkill
- d-official-market-analysisSkill
- epic-designSkill
- fantasy-designSkill
- horror-designSkill
- noir-designSkill
- prop-assetSkill
- romance-designSkill
- scene-assetSkill
- war-designSkill
- web-design-directorSkill
- wuxia-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 17 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈17
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use ai-storyboard-director only after the director judgment is complete.
- Distinctive: line 18
Use this mode when the user asks Codex to create autonomously, automatically make the video, test its ability, or deliver a finished film …
- Distinctive: line 20
Read the project knowledge, current script, approved assets, visual rules, decisions, and checkpoints.
- Distinctive: line 23
Do not push ordinary directing decisions back to the user.
- Distinctive: line 24
Ask only when a missing choice materially changes story meaning, spend, permissions, publication, or an already locked structure.
- Distinctive: line 28
Use this mode when the user supplies or has repeatedly adjusted a storyboard, timing, shot order, staging, dialogue, or prompt structure.
- Distinctive: line 30
Treat the user-locked structure as authoritative.
- Distinctive: line 32
Do not add shots, remove shots, reorder beats, rewrite dialogue, or replace staging in the name of optimization.
- Distinctive: line 33
If a requested result conflicts with the locked structure, identify the exact conflict and its visible consequence before proposing a …
- Distinctive: line 51
Do not start from prompt formatting.
- Distinctive: line 52
Do not equate a script paragraph, generation segment, and shot.
- Distinctive: line 53
Do not equate continuity with a fixed camera.
- Distinctive: line 54
Do not count repeated crops, cosmetic zooms, or unchanged viewpoints as new effective shots.
- Distinctive: line 55
Do not declare success because files exist, durations match, prompts are complete, or individual clips pass technical checks.
- Distinctive: line 56
Do not deliver autonomous work that resembles independent single-shot demonstrations joined together.
- Distinctive: line 57
Do not claim a qualified final video without actually viewing the complete rendered file.
- Distinctive: line 61
Keep internal work concise and production-facing.
- Distinctive: line 67
Never substitute a storyboard, prompt document, still gallery, test clip, or QC checklist for the final video.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Produce AI Video
Outcome
Deliver an actual qualified video. Treat storyboards, prompts, generated clips, edit projects, and QC reports as intermediate artifacts, never as the final result.
Use ai-storyboard-director only after the director judgment is complete. Its six-module prompt structure and Digital-10 information core are the downstream encoding contract; do not modify or replace that Skill.
Choose the execution mode
Autonomous production mode
Use this mode when the user asks Codex to create autonomously, automatically make the video, test its ability, or deliver a finished film from a script.
- Read the project knowledge, current script, approved assets, visual rules, decisions, and checkpoints.
- Make the director decisions independently.
- Design the shot groups, prompts, production route, generation, selection, edit, sound, review, and repairs.
- Do not push ordinary directing decisions back to the user.
- Ask only when a missing choice materially changes story meaning, spend, permissions, publication, or an already locked structure.
User-directed execution mode
Use this mode when the user supplies or has repeatedly adjusted a storyboard, timing, shot order, staging, dialogue, or prompt structure.
- Treat the user-locked structure as authoritative.
- Change only the requested scope.
- Do not add shots, remove shots, reorder beats, rewrite dialogue, or replace staging in the name of optimization.
- If a requested result conflicts with the locked structure, identify the exact conflict and its visible consequence before proposing a change.
Run the autonomous workflow
- Lock sources and acceptance. Identify the unique project, current script version, approved assets, fixed decisions, delivery format, permissions, cost boundary, and definition of a qualified video. Separate verified facts, unknowns, assumptions, and conventions.
- Interpret the script. Determine the dramatic event, character objective, power relation, information reveal, physical action, emotional turn, sound cue, entry state, and exit state. Read autonomous-production-workflow.md for the auditable decision framework.
- Direct before prompting. Decide what the audience must see and in what order. Build a world-state model for space, subjects, props, light sources, movement axes, and continuity.
- Design segments and shots. Treat a segment as a short dramatic sequence and a shot as one uninterrupted viewpoint. In autonomous mode, design at least 7–8 effective, non-equally timed shots per segment unless the user explicitly requests a long take. Every cut must add information, change power, clarify action, reveal a reaction, or hand off the next beat.
- Create the director handoff. Produce a
DIRECTOR_SHOT_PACKAGEcontaining the segment objective, entry and exit states, world-state lock, shot order, timing, framing, camera, visible action, sound, cut motivation, and continuity handoff. Only after this package is coherent mayai-storyboard-directorconvert it into the approved human-readable storyboard and six-module video prompt. - Choose the production route. Preserve the director timing and shot design. If one model call cannot reliably render the required internal shots, generate individual shots or smaller clusters and edit them into the designed segment. Never let a model's maximum duration redefine the dramatic timing.
- Generate real motion. Produce actual video material. Reject static-frame motion, keyframe slideshows, or technical previews when the requested deliverable is a finished video.
- Select and assemble. Judge takes by performance, identity, action, continuity, composition, and editability. Cut on motivated action, gaze, occlusion, object, sound, or information change. Add handles where the tool permits; do not concatenate fixed clip durations blindly.
- Build sound. Integrate dialogue, performance breaths, environment, effects, transitions, silence, and music only when authorized. Make sound carry space, action, rhythm, and continuity rather than feeling pasted on.
- Watch, repair, and rewatch. Review the entire film at normal speed for story and rhythm, then again for continuity, artifacts, and sound. Fix the first audience-rejecting defect and repeat until all hard gates in qualified-video-acceptance.md pass.
- Deliver honestly. Return the playable final video, its duration and format, the validation state, and any visible residual risk. If full-playback review or a hard gate is unavailable, report
未完成/待验证; never call the result qualified.
Enforce hard rules
- Do not start from prompt formatting. Start from what the audience must see.
- Do not equate a script paragraph, generation segment, and shot.
- Do not equate continuity with a fixed camera. Keep the world state fixed while recalculating screen projection after every camera change.
- Do not count repeated crops, cosmetic zooms, or unchanged viewpoints as new effective shots.
- Do not declare success because files exist, durations match, prompts are complete, or individual clips pass technical checks.
- Do not deliver autonomous work that resembles independent single-shot demonstrations joined together.
- Do not claim a qualified final video without actually viewing the complete rendered file.
Output Contract
Keep internal work concise and production-facing. The user-facing completion must lead with the playable video and one of these states:
合格成片: every hard gate passed after full playback.候选成片: playable, but one or more visible quality judgments still await user review.未完成/待验证: generation, assembly, full playback, or a hard gate is incomplete.
Never substitute a storyboard, prompt document, still gallery, test clip, or QC checklist for the final video.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

