# Scenario Blender Expert

Use when doing any 3D work in Blender through Python or an MCP bridge, headless or in a...

- Repository: https://github.com/scenario-labs/skills (1448 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add scenario-labs/skills --skill scenario-blender-expert -g -a claude-code -y`
Codex: `npx skills add scenario-labs/skills --skill scenario-blender-expert -g -a codex -y`
Cursor: `npx skills add scenario-labs/skills --skill scenario-blender-expert -g -a cursor -y`
Gemini CLI: `npx skills add scenario-labs/skills --skill scenario-blender-expert -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add scenario-labs/skills`

## Description

Use when doing any 3D work in Blender through Python or an MCP bridge, headless or in a live session: modeling, sculpting a character or head, retopology, UV unwrapping, baking, texturing, rigging, animating, previs, geometry nodes, lighting and rendering, grease pencil, or finishing an AI-generated mesh into a production asset. Also before exporting or handing off an asset, to check it is ready for a game engine, a render or a 3D print (floating parts, z-fighting, inside-out normals, unapplied scale, missing UVs). Also when a bpy script fails on Blender 5.x API changes, a brush or sculpt operator fails or crashes headless, or a result has to be judged like a professional 3D artist would.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Blender expert (router and agent protocol)

Expert-level Blender work is a loop, not a script: build big to small, and at every stage turn the
model, measure it and fix it before adding detail. This skill is the protocol every Blender task
follows and the map to the domain skills distilled from Blender Studio artists, Blender Conference
talks and top instructors (sources in each skill). If a sibling skill named here is missing from
your available skills, load it with `skill_get` (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.

## 1. Execution channel

- **Live GUI Blender** (user's session over the MCP bridge), for anything interactive: real
  sculpt/paint brushes, weight painting, viewport screenshots. One short, idempotent script per call
  returning a compact result dict. Get-or-create by name. Never touch objects you did not create.
  Save a stage backup `bpy.ops.wm.save_as_mainfile(filepath=..., copy=True)` after each stage.
- **Headless helper** `blender -b [file] --factory-startup --python-exit-code 1 -P x.py -- args`,
  for renders, audits, batch ops, anything when no bridge is up. Use `--factory-startup` so the
  user's add-ons and preferences stay out of the run (an add-on can call the network or change
  defaults); the Scenario Blender Plugin's headless server,
  `blender --background scene.blend --command scenario_blender`, is the exception because it needs
  the extension loaded. Without `--python-exit-code` a failing script still exits 0. Print a final
  machine-readable result line.

Never open your own GUI Blender window to test things on the user's machine: windows steal focus and
pile up. Live work goes through the user's already-running Blender; everything else runs headless,
one Blender process at a time per agent (other sessions may be rendering on the same machine).

The rest: https://github.com/scenario-labs/skills/blob/HEAD/skills/dcc/blender/scenario-blender-expert/SKILL.md