Blender Production

What it does

• Turns a brief into concrete checks, like proportions, materials, lighting, animation timing and delivery format.
• Builds scenes in order: shape and camera first, then structure, materials, lighting and detail.
• Benchmarks rendering on the real scene early, before long renders or bakes.
• Renders long films as image sequences that can resume, and checks the frames before encoding them.
• Inspects the finished images and motion, reopens the saved file, and reports what was and wasn't verified.

How it works

1. Confirm which Blender window, file and scene it is working on before changing anything.
2. Translate the brief into checks and keep a short list of defects with evidence.
3. Build in dependency order and review actual output at display size and in close crops.
4. Benchmark delivery, render, then verify and package the result.

What you need

• Blender (tested on 5.1.2)
• A Blender MCP server for live scene inspection
• An agent that supports skills, such as Codex or Claude Code

Install it

npx skills add per-simmons/blender-production

Or put the folder in your agent’s skills directory: ~/.codex/skills/blender-production for Codex, ~/.claude/skills/blender-production for Claude Code.

The full instructions, and the skill itself, are on GitHub.

Try asking

• “Build a 3D model of this building from these reference photos and render a flythrough.”
• “Check this Blender scene's materials and lighting and fix the biggest visible problem.”
• “Benchmark render times on this scene, then render the film as a resumable image sequence.”

Good to know

• The skill says it cannot guarantee a perfect reconstruction from incomplete references. It defines checks and reports what it verified.
• The sequence tool checks and encodes frames but does not render missing frames or judge visual quality.