01
Write reliable Blender Python
Create scripts that manage context deliberately, use data APIs where suitable, expose parameters, report failures, and avoid needless destructive edits.
3D creation and automation
CategoryGame & 3D Development
Codex Skills for Blender
Codex Skills for Blender give Codex focused instructions for writing Blender Python, building procedural scenes, creating Geometry Nodes setups, managing materials, automating repetitive work, debugging add-ons, and validating exported assets. Download the skills and connect them to the Blender version and production rules you use.
Blender PythonGeometry NodesScene automationAsset checks
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: generate modular room kit
inspect:
- scene units
- object naming
- export target
verify: geometry + materials + exportA valid script is not always a usable scene
Good Blender automation respects context, transforms, data blocks, performance, and the artist who must edit the result.
Blender work combines visual decisions with technical state. Selection, mode, active objects, modifiers, node trees, collections, units, color management, and version-specific APIs can all change what a script produces.
These skills help Codex plan and write Blender automation that is predictable, non-destructive where possible, clearly named, easy to rerun, and suited to a real asset pipeline.
What the downloadable skills can do
What Codex Skills for Blender can help you create
02
Build procedural systems
Generate repeatable models, object layouts, modifiers, Geometry Nodes groups, materials, cameras, lights, and scene variations from defined inputs.
03
Develop and debug add-ons
Structure operators, panels, properties, registration, preferences, and error handling while accounting for the target Blender API version.
04
Prepare production-ready assets
Check names, scales, transforms, topology expectations, materials, texture paths, origins, collections, and export settings before delivery.
From visual brief to editable scene
Define the scene contract before generating geometry or code
The workflow captures the target Blender version, units, coordinate conventions, editability, performance budget, and export destination before implementation begins.
workflow.statusREADY
Context → Plan → Work → Verify
01
Describe the visual and technical target
Specify references, dimensions, style, asset purpose, version, renderer, frame range, naming, poly budget, and required deliverables.
02
Inspect the scene and choose an approach
Review objects, collections, modifiers, node groups, materials, dependencies, and whether scripting, nodes, or manual setup is the best fit.
03
Build in repeatable stages
Create or modify data with stable names, grouped parameters, reusable functions, progress messages, and safe rerun behavior.
04
Validate the final asset
Check viewport and render output, transforms, missing data, performance, file paths, frame results, and export in a clean scene copy.
Useful across Blender production
Match the skill to the kind of 3D work being automated
Procedural modeling, animation tools, rendering, and game assets have different success criteria.
Geometry Nodes
Create node groups for scattering, instancing, attribute-driven modeling, reusable modifiers, and artist-friendly controls.
Python scripting
Automate scene setup, batch operations, data cleanup, rendering, imports, exports, and repeatable asset generation.
Animation and rendering
Set up cameras, lights, keyframes, drivers, render layers, frame outputs, and batch render checks.
Asset and engine export
Prepare models for game engines or other DCC tools with agreed axes, scale, origins, names, materials, and export presets.
Common Blender automation jobs
Use the skills for repetitive work, procedural tools, and pipeline checks
A task can produce a one-off script, a reusable node group, an add-on, or a validated asset batch.
01Generate a scene with Python
02Create a procedural modeling tool
03Build a Geometry Nodes modifier
04Batch rename and organize objects
05Set up materials, lights, and cameras
06Debug a Blender add-on
07Automate renders or exports
08Validate assets before delivery
Artists and developers building in Blender
Who Is This For?
These skills help people translate a visual or pipeline requirement into dependable Blender code and editable scene structure.
3D artists
Automate repetitive setup, generate variations, organize complex scenes, and keep procedural results controllable.
Technical artists
Build tools, node groups, validators, exporters, and production conventions that artists can use safely.
Game developers
Create and prepare props, modular kits, collision helpers, LOD workflows, materials, and engine-ready exports.
Add-on developers
Plan Blender extensions, use the Python API correctly, debug context issues, and support declared Blender versions.
Good to know:
The skills provide instructions and code for Blender work. They do not replace artistic direction or guarantee that a script will work across every Blender version, renderer, add-on combination, file, or production pipeline without testing.
Connect the skill to your Blender project
Installation Guide
Install the skill in the repository that holds your scripts, add-on, assets, or pipeline documentation.
Download and extract the Blender skills
Keep SKILL.md with included scripting guidance, scene checks, API notes, and production references.
Choose project or personal scope
Use project scope for one asset pipeline and Blender version, or personal scope for reusable 3D automation guidance.
Declare the Blender environment
Record the exact Blender version, operating system, renderer, enabled add-ons, units, coordinate rules, output formats, and Python restrictions.
Add scene and asset conventions
Document collections, object names, origins, transforms, materials, texture paths, poly budgets, modifier policy, and export presets.
Open Codex beside the project files
Provide the visual brief and a description of the current scene. Run generated scripts on a backup or version-controlled copy first.
Before you automate Blender
Frequently Asked Questions
Answers about Python, Geometry Nodes, add-ons, scene access, versions, and generated assets.
Can the skills control Blender directly?+
They can create scripts and instructions. Direct scene control requires a configured connection or a way to run the generated Python inside Blender.
Can they create Geometry Nodes setups?+
Yes. They can plan node graphs and generate Python that builds node groups, interfaces, links, defaults, and modifiers for a declared Blender version.
Will scripts work in every Blender version?+
No. Blender APIs and node definitions change. Always state the target version, check its documentation, and test the script in a copy of the intended file.
Can the skills help build an add-on?+
Yes. They can structure registration, operators, panels, properties, preferences, packaging, and debugging, then help verify behavior in supported versions.
Can I use the output for game development?+
Yes. The workflow can enforce engine-specific scale, axis, origin, naming, topology, material, collision, LOD, and export requirements you provide.
Automate without losing control
Give Codex a Blender workflow built for predictable scripts, editable scenes, and assets that survive the pipeline.
Clear parameters. Safe scene changes. Reusable tools. Outputs checked before delivery.