- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add scenario-labs/skills --skill scenario-blender-expert -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add scenario-labs/skills --skill scenario-blender-expert -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add scenario-labs/skills --skill scenario-blender-expert -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add scenario-labs/skills --skill scenario-blender-expert -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/scenario-labs/skills/tree/HEAD/skills/dcc/blender/scenario-blender-expertFrom the publisher
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.
bpy.ops.wm.save_as_mainfile(filepath=..., copy=True) after each stage.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).
Live channel: the Scenario Blender Plugin. When the user's Blender runs the Scenario Blender
Plugin, its local MCP server scenario-blender is the bridge. Setup, quotes, generation and placing
results are the scenario-blender skill's work; this section covers the bpy side (guide at
blender.scenario.com). Its tool names differ from other Blender MCP
servers: there is no execute_blender_code, get_scene_info, get_viewport_screenshot or
import_asset.
Read each tool's input schema from the server before its first call: it is the reference for optional arguments.
execute_python stays off until the user enables Allow connected agents to run Python in the
plugin preferences. A PermissionError means ask for it or stay on the specific tools. A refused
spelling (quit, factory reset, file deletion) changed nothing: rewrite the call.save_as_mainfile(..., copy=True) through execute_python) writes a separate file and leaves
the open file and its unsaved state alone: it is also the saved copy that headless work starts
from. Ask the user to save their own file at milestones; with no one to ask, keep working from the
copies and say in the report that the open file is still unsaved.Check bpy.app.version first; this skill set targets 5.2 LTS, while the Scenario Blender Plugin
also runs on 5.0 and 5.1 (scene_summary reports the version), so check the version timeline in the
deltas before using a recent API. Many tutorials the experts recorded use 2.8x to 4.2 UI: read
references/blender-5.2-deltas.md before trusting any
remembered operator, brush name or API.
Verified capability matrix (Blender 5.2.1):
scripts/bx_audit.py for
meshes, the domain's own checks) AND render a review sheet
(scripts/bx_review.py: silhouette, matcap, wire from
front/side/three-quarter/low) and open it with the image reader. Experts orbit constantly; the
review sheet is the agent's orbit. Every image read stays in the agent's context: for quick looks
use render_still at about 768 px wide or screenshot_viewport, and keep review sheets near
1600 px (res=400 for four views and three modes). Judge with the domain's
references/critique.md.bx_audit.deliverable, below) on the parts of
the asset before any export or handoff and fix every error. Then report final renders, gate and
audit numbers, and what was not verified.Never report a model, rig, animation or render as done without having looked at a render of it.
Related skills outside this set: scenario-3d (generate meshes to finish here), scenario-textures (AI textures).
scripts/, all tested on 5.2.1)bx_audit.py: audit(obj, high=None) returns quads %, n-gons, poles (valence 3 / 5+ / 6+),
non-manifold, loose, duplicates, flipped faces, self-intersections, boundary loops, symmetry %,
edge-length CV, and fidelity to a high poly; verdict(report) lists problems. CLI:
blender -b f.blend --python bx_audit.py -- --object Name [--high Sculpt] [--json out.json].bx_audit.deliverable(objs, profile="game"): the delivery gate. audit grades topology; this
grades what an engine, renderer or slicer receives, across the parts of ONE asset:
print;game, render, print, roblox): unapplied scale, faces pointing into a part
(an error from 0.1% of its surface, a warning below except for print), duplicate faces, no UV
map under an image texture, open borders for print and roblox, any gap between parts for
print, the Roblox 20,000-triangle mesh limit (checked 2026-10-18).{pass, errors, warnings, per_object}. Tolerances scale with the asset's diagonal.
UV-seam splits from a glTF import are welded for the checks, so seams never read as holes.blender -b --factory-startup --python-exit-code 1 -P bx_audit.py -- --deliverable [--import model.glb | --objects A B] --profile game [--json out.json].obj.data.transform(Matrix.Diagonal(obj.scale).to_4x4()), then
obj.scale = (1, 1, 1); a scale the message puts on a parent: select the parent and its
children, bpy.ops.object.transform_apply(scale=True)), bmesh.ops.recalc_face_normals for
inside-out parts, bmesh.ops.reverse_faces for faces pointing inward
(per_object[name]["inward_faces_at"]), delete or offset the hidden face of a z-fighting pair,
join or move floating parts, delete fragments.bx_review.review(parts, out, culling=True) (magenta shows through a face pointing inward) and
compare with a sheet without.bx_review.py: review(objs, out_dir, views, modes, culling=False) takes objects or names and
writes one contact sheet (rows = modes, cols = views) in a temporary scene, user settings
untouched; ; . Only
has a command line: call the others from a short wrapper script.Import pattern: import sys; sys.path.append("<this skill>/scripts"); import bx_audit, bx_review.
Replace <this skill> with the absolute path of the installed skill folder: Blender's Python does
not share the agent's working directory, and over a live bridge the code runs inside the user's
Blender. Check the path in the first call (result["ok"] = os.path.isdir(path)) and
importlib.reload a module after the skill updates.
bpy.ops.brush.asset_activate(asset_library_type='ESSENTIALS', asset_library_identifier="", relative_asset_identifier="brushes/essentials_brushes-mesh_sculpt.blend/Brush/Clay Strips");
brush size is a diameter (5.0); Flatten/Fill/Scrape merged into the Plane type.mesh.shade_smooth() / Smooth by Angle modifier; voxel remesh output
is flat-shaded until you call shade_smooth().BLENDER_EEVEE is the EEVEE Next identifier in 5.x (BLENDER_EEVEE_NEXT fails).scene.compositing_node_group, not scene.node_tree.image_settings.media_type = 'VIDEO' before file_format = 'FFMPEG' (5.0).action.fcurves removed (5.0): use
bpy_extras.anim_utils.action_get_channelbag_for_slot(action, slot).GREASEPENCIL with
bpy.ops.grease_pencil.* (4.3).with bpy.context.temp_override(...).obj.matrix_world is stale right after setting location/scale until view_layer.update().references/bpy-reliability.md: checklist and tested procedures
for reliable bpy (operators vs data API, stale references, evaluated vs original data, idempotent
headless jobs, numpy bulk access, node trees, persistence). Load before writing any non-trivial
script.references/blender-5.2-deltas.md: full, cited list of what changed from 2.8x to 5.2 per domain
(load before writing code from memory or following an old tutorial).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, an
---name: scenario-blender-expertdescription: Use when doing any 3D work in Blender through Python or an MCP bridge, headless or in a live session…---# skills/dcc/blender/scenario-blender-expert/SKILL.mdOverview
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.
FAQ
Download skills/dcc/blender/scenario-blender-expert/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/scenario-labs/skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
playblast(out_path, res_pct=50)turntable(obj, out_path, frames=72, res=720)reviewbx_gui.py: real brushes in a live session: set_view, activate_brush(mode, name),
stroke(mode, world_points, size, strength), run(op, **kw), set_paint_color, screenshot.