EL4CTEO/blender-skills / skills/blender-pipeline-automation
blender-pipeline-automation
VerifiedAutomate Blender 5.3 at scale - headless CLI flags, batch convert/inventory/run-any-skill-script over folders of .blend/.fbx/.glb/.obj/.usd, sharding, bpy pip module, library linking, path management, render-farm and CI patterns. Use for batch jobs, format conversion, library maintenance and pipeline tooling.
Pipeline Automation
The execution model is in blender-core (run_in_blender.py finds Blender and prints only the JSON results).
Batch one-liners
blender -b -P scripts/batch_process.py -- --in "assets/**/*.fbx" --op convert --to glb --out export/
blender -b -P scripts/batch_process.py -- --in library/ --op report # inventory JSON lines
blender -b -P scripts/batch_process.py -- --in "src/*.blend" --op script \
--script ../blender-asset-qa/scripts/qa_check.py --kwargs '{"profile":"game"}' # QA a whole library
blender -b -P scripts/batch_process.py -- --in src/ --op script --script ../blender-game-optimization/scripts/make_lods.py \
--kwargs '{"rename":true}' --save-to processed/ # LODs for every file
Each file is streamed as one JSON line with ok, timing and results. Failures don't stop the batch, and the summary lists them. Parallel: start N processes with --shard 0/N … --shard N-1/N (Blender uses one core for Python, so processes scale with CPU/GPU count).
Headless CLI essentials
| Flag | Meaning |
|---|---|
-b | background, no UI. Put it first |
file.blend | open before running scripts. Order matters: args run left to right |
-P script.py / --python-expr "..." | run Python |
--python-exit-code 1 | non-zero exit if the script raises (CI) |
--factory-startup | ignore user prefs/add-ons (reproducible). Bundled add-ons still load |
--addons rigify,io_scene_fbx | enable specific add-ons |
-E CYCLES -o //out/#### -F PNG -s 1 -e 10 -a / -f 5 | render (blender-rendering) |
--command extension build/validate/install-file | extension tooling (blender-addon-development) |
-- --my args | everything after -- goes to the script (sys.argv[sys.argv.index("--")+1:]) |
--log "*", --debug-python | debugging. 5.0 changed the log format, so don't regex progress lines |
Environment variables: BLENDER_USER_SCRIPTS, BLENDER_USER_EXTENSIONS, BLENDER_SYSTEM_PYTHON. Use OCIO for custom color configs. |
bpy as a Python module
pip install bpy==5.3.* (or 5.2.* for the LTS) (Python 3.13, matching the Blender release) gives import bpy in plain Python, which is handy for pytest/CI/web services. It has no UI and no GPU module by default, and it's large (~300 MB). Version-lock it with the Blender you target. The bpy wheel and the CLI behave the same for data API work.
Library patterns
- Append/link:
bpy.data.libraries.load(path, link=...)(seeblender-core/references/bpy-patterns.md). 5.2:data_from.librariesexposes nested library paths when loading. - Write a subset:
bpy.data.libraries.write(path, {datablocks}, fake_user=True, path_remap="RELATIVE_ALL")builds asset/library files from a session. - Find files:
bpy.data.file_path_foreach(...)(5.2 flags:EXPAND_TOKENSfor UDIMs,EXPAND_SEQUENCES,EXPAND_CACHES), andbpy.utils.blend_paths(absolute=True)lists every external path. - Remap/relocate:
bpy.ops.file.find_missing_files(directory=...),make_paths_relative,pack_all. Libraries:lib.filepath = new; lib.reload(). - Iterate every ID:
bpy.data.all_ids(5.2; order isn't stable in 5.3, so sort by name if output must be deterministic), andbpy.data.orphans_purge(do_recursive=True)for cleanup.
Robustness rules
- One task per process where possible. Long Blender sessions leak (images, undo).
batch_process.pyreuses the process but resets withread_factory_settings(use_empty=True)/open_mainfile. - Never write into the source folder by default. Use separate
--out/--save-to, and write withcopy=True. - Make scripts idempotent: re-running replaces their own outputs (named prefixes,
exist_ok). - Log JSON, not prose: one object per file/job, so agents and CI can parse it cheaply.
- Pin the Blender version (5.2 LTS, or 5.3) for a project. Record
bpy.app.version_string+ hash (bpy.app.build_hash) in the outputs. - Paths:
bpy.path.abspath("//x")is relative to the opened .blend. In headless batches use absolute paths, or set them afteropen_mainfile. - GPU in containers: Cycles CUDA/OptiX needs the NVIDIA container runtime. Otherwise use CPU. EEVEE needs a GPU/EGL even headless.
CI recipe (GitHub Actions)
Download the Linux tarball (https://download.blender.org/release/Blender5.3/blender-5.3.0-linux-x64.tar.xz), cache it, then blender -b --factory-startup --python-exit-code 1 -P tests/run_all.py. This repo's .github/workflows/ci.yml is a working example.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |