Video Production with AI Agents: lanes, prompts, skills and render checks
by PaperChaseWebb
A Markdown playbook for making finished videos with Claude Code or Codex: pick a lane (draw in code, edit footage, script 3D or generate), plan with a shot list, render test frames, and make the agent check every render before you see it.
- Price
- $29
- Difficulty
- Intermediate
- Setup
- 20 min
- Format
- .md file
video-production-with-ai-agents.md · 28 KB · instant download after checkout
Want this built for you instead? We can build it for you.
What you end up with
Your agent plans the video as files, renders test frames first, checks its own output, and never touches your source footage or uploads anything.
What you get
- 9 sections in one .md file, about 16 pages
- A lane guide: draw in code, edit footage, script 3D or generate, with what each gives up
- The seven-step loop from shot list to final check
- SHOTLIST, STYLE, ASSETS and RENDER-LOG templates plus an AGENTS.md rules block
- 16 prompts across planning, code-drawn scenes, footage edits, Blender and assembly
- Four SKILL.md files: shot planner, source keeper, render checker, license ledger
- Checklists: before render, before publish, footage with people, small machines and CI
- Reported render times and costs, and a method to measure yours
- Concept library of 20 video projects
- Linked credits for all 16 sources we studied
Who it is for
People who want a coding agent to plan, render and edit real videos, from launch edits and app previews to 3D product spots, and to check its own work before anything is published.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free. Uses the agent plan you already pay for. Optional paid services (transcription, voice, music, video models) are listed so you can decide.
Time to result: Shot list and first test frames in one evening
Sample prompts, free to use
Footage for this video is in sources/. Do not modify it. Transcribe each take with word timings and propose an edit plan for a [60] second [launch video]: what to keep, in what order, and what to cut. Wait for my OK before cutting anything.
Approving a plan is cheaper than re-rendering.
Look at the test frames in out/test/. List what is physically wrong, the likely cause in the renderer, and the smallest fix for each. Re-render only the frames that were wrong.
Test frames cost seconds. A full render costs minutes.
Free preview of the file
# Video Production with AI Agents A PaperChaseWebb pack, version 1.0. Written for Claude Code and Codex, the two agents every source in this pack used to write scenes, run ffmpeg, drive Blender and check renders. Plain Markdown, so other agents with shell access can read it, but those are the two the prompts and skills were worded for. This pack does not make your video. It is the working method we pulled out of 16 public build reports and open-source tools from October 2026: people who got finished videos out of a coding agent, from launch edits of raw footage to App Store previews drawn in code, a music video timed to the beat and a 3D product spot rendered on a 2016 graphics card. Every source is linked and credited in `08-sources.md`, and everything here is in our own words. ## Files | File | What it is for | |---|---| | 01-method.md | Pick the lane (draw, edit, script 3D or generate), then the seven-step loop from shot list to final check | | 02-project-files.md | Fill-in SHOTLIST.md, STYLE.md, ASSETS.md, RENDER-LOG.md and an AGENTS.md rules block | | 03-prompts.md | 16 prompts from first shot list to final export | | 04-agent-skills.md | Four drop-in SKILL.md files: shot planner, source keeper, render checker, license ledger | | 05-checklists.md | Before you render, before you publish, footage with people in it, small machines and CI | | 06-render-time-and-cost.md | Reported render times and costs, and how to measure your own | | 07-concept-library.md | 20 video projects with the lane, the main risk and a first prompt | | 08-sources.md | Every source we used, linked and credited |
Worth knowing
- The pack is a method and prompt library. It does not include footage, models, music or hosting.
- Render times and costs are as reported by the builders. Measure your own.
- Check the license of every model, voice, track, font and asset before you publish, and never let an agent upload or post for you.
Questions
Which agents is it written for?
Claude Code and Codex. The skills use their file layouts. Other agents with shell access can read the Markdown, but we have not written for them.
Do I need a video model or a GPU?
No. Two of the four lanes (draw in code and edit footage) run on almost any machine. The 3D lane in our sources ran on a 2016 graphics card.
Does it work with my video editor?
The agent can stop at a rough cut and hand over clips, an edit list and an SRT caption file, which most editors import. One source exports a timeline to Premiere or Resolve.
Is there a free sample?
Yes. The render-checker skill and the commands it uses are free on their own listing.
Is any of it copied?
No. We read 16 public build reports and open-source tools and wrote everything in our own words. Sources are linked and credited inside.
Details
Version 1.0 · Updated Oct 26, 2026 · Markdown version of this page
License: Personal and commercial use. Your videos are yours. Do not resell or republish this pack. Download terms
Related
Check every render before you trust it (free sample)
One rule, one skill and four ffmpeg commands that make Claude Code or Codex look at its own video output (frames, cuts, loudness, captions) before it tells you it is done.
Turn a folder of raw footage into a finished edit with an agent skill
video-use is an open-source skill from the Browser Use team. You drop raw takes in a folder and ask Claude Code or Codex for an edit. It cuts filler words, grades color, adds subtitles and animated overlays, then checks its own render before showing you.
Make a 3D product ad with Claude Code and headless Blender on an old GPU
A 15-second, four-shot product spot rendered on a 2016 graphics card. Claude Code wrote the whole Blender scene in Python, Blender rendered it with no window open, and ffmpeg put the shots, music and overlay together. The builder posted the render times and what broke.