blender-interface-cli-headless-execution
Sub-skill of blender-interface: CLI Headless Execution (+3).
Best use case
blender-interface-cli-headless-execution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of blender-interface: CLI Headless Execution (+3).
Teams using blender-interface-cli-headless-execution should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cli-headless-execution/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How blender-interface-cli-headless-execution Compares
| Feature / Agent | blender-interface-cli-headless-execution | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of blender-interface: CLI Headless Execution (+3).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# CLI Headless Execution (+3)
## CLI Headless Execution
```bash
# Run Python script headlessly (no GUI)
blender --background --python script.py
# Run with specific .blend file
blender model.blend --background --python script.py
# Render single frame
blender model.blend --background --render-output //renders/frame_ --render-frame 1
# Render animation (frames 1-250)
blender model.blend --background --render-output //renders/frame_ --render-anim
# Render specific frame range
blender model.blend --background --frame-start 1 --frame-end 100 --render-anim
# Pass custom arguments (after --)
blender --background --python script.py -- --input mesh.stl --output render.png
```
## CLI Flags Reference
| Flag | Purpose |
|------|---------|
| `--background` / `-b` | Run without GUI (headless) |
| `--python` / `-P` | Execute Python script |
| `--python-expr` | Execute Python expression inline |
| `--render-output` / `-o` | Set render output path |
| `--render-frame` / `-f` | Render single frame |
| `--render-anim` / `-a` | Render full animation |
| `--frame-start` / `-s` | Set start frame |
| `--frame-end` / `-e` | Set end frame |
| `--factory-startup` | Ignore user preferences |
| `--addons` | Enable specific addons |
| `--threads` | Set thread count |
## Accessing Custom Arguments in Script
```python
import sys
# Arguments after "--" are passed to the script
argv = sys.argv
if "--" in argv:
custom_args = argv[argv.index("--") + 1:]
else:
custom_args = []
# Parse with argparse
import argparse
parser = argparse.ArgumentParser()
parser.add_argument("--input", required=True)
parser.add_argument("--output", required=True)
args = parser.parse_args(custom_args)
```
## Complete Headless Render Pipeline
```python
#!/usr/bin/env python3
"""Headless Blender render script for engineering visualization."""
import bpy
import sys
import argparse
def parse_args():
argv = sys.argv
custom = argv[argv.index("--") + 1:] if "--" in argv else []
parser = argparse.ArgumentParser()
parser.add_argument("--input-stl", required=True)
parser.add_argument("--output-png", required=True)
parser.add_argument("--resolution", type=int, nargs=2, default=[1920, 1080])
return parser.parse_args(custom)
def main():
args = parse_args()
# Clear scene
bpy.ops.object.select_all(action='SELECT')
bpy.ops.object.delete()
# Import geometry (Blender 4.x)
try:
bpy.ops.wm.stl_import(filepath=args.input_stl)
except AttributeError:
bpy.ops.import_mesh.stl(filepath=args.input_stl) # 3.x fallback
obj = bpy.context.selected_objects[0]
# Auto-center and scale
bpy.ops.object.origin_set(type='ORIGIN_GEOMETRY', center='BOUNDS')
obj.location = (0, 0, 0)
# Setup scene
setup_engineering_camera(distance=max(obj.dimensions) * 2)
setup_lighting()
configure_render(resolution=tuple(args.resolution))
# Render
bpy.context.scene.render.filepath = args.output_png
bpy.ops.render.render(write_still=True)
print(f"Rendered: {args.output_png}")
if __name__ == "__main__":
main()
```Related Skills
solidworks-to-blender-pipeline
Use when converting SolidWorks .sldprt/.sldasm geometry to Blender for rendering, animation, or visualization, including questions about STEP export settings, FreeCAD as a bridge, or which mesh format (STL/OBJ/GLTF) to choose.
digitalmodel-worktree-test-execution-with-shared-venv
Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.
blender-worktree-test-hardening
Recover and harden digitalmodel Blender automation work in isolated worktrees when uv/editable dependency paths break and local machines lack a Blender executable.
plan-gated-issue-execution-wave
Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.
work-around-merge-conflicts-in-test-execution
Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly
wave-based-parallel-plan-execution
Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering
plan-governance-vs-execution-boundary-for-adversarial-review
Keep stale-approval/governance remediation out of execution-path pseudocode, TDD, files-to-change, and deliverable acceptance when hardening a GitHub issue plan under adversarial review.
interactive-issue-execution-worktree-guardrails
Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.
gtm-prospect-pipeline-phased-execution
Phased execution pattern for
workspace-hub-batch-issue-execution
Deprecated alias for gh-work-execution.
gh-work-execution
Canonical GitHub issue execution route after plan approval — strengthened resource intelligence, TDD-first implementation, targeted validation, adversarial review, delegation controls for Codex agent teams, GitHub progress posting, future-issue capture, and commit/push with closeout discipline.
gh-work-execution-checklist
Compact live-execution checklist companion for approved GitHub issue work. Use during active implementation as a fast operational route; gh-work-execution remains the canonical source of truth.