scenario-blender-expert
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…
Install / Use
npx skills add scenario-labs/skills --skill scenario-blender-expertInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Our assessment of scenario-blender-expert
scenario-blender-expert scores 84/100 on our quality scale, 266th of 354 Other skills we index.
Its SKILL.md is 18 KB long, split into 7 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 35 days ago, so scenario-blender-expert is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-blender-expert compared with similar skills
All 4 of these similar skills score higher than scenario-blender-expert; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-blender-expert (this skill)by scenario-labs | 84 | 1.0k | 35d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| hyperframesby heygen-com | 100 | 88.2k | today | CLAUDE.md |
| rufloby ruvnet | 100 | 82.3k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
Frequently asked questions
- How do I install scenario-blender-expert?
- Run
npx skills add scenario-labs/skills --skill scenario-blender-expert. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-blender-expert work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-blender-expert safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-blender-expert still maintained?
- The repository was last updated 35 days ago, so scenario-blender-expert is actively maintained.
Skill content
View source on GitHubname: scenario-blender-expert 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." license: MIT
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-startupso 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-codea 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.
| Step | Plugin tool and main arguments |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Read the scene before acting | scene_summary, then object_detail with name for one object and datablocks_summary for counts |
| Check an API before scripting | blender_api_help with path, such as bpy.types.BevelModifier |
| Run bpy | execute_python with code; bpy and result = {} are preloaded, so fill result |
| Look | screenshot_viewport (viewport with overlays), render_still with source (CAMERA or VIEWPORT), width and height; both need the GUI |
| Select, move the timeline | select_objects with names (a list), set_frame with frame |
Read each tool's input schema from the server before its first call: it is the reference for optional arguments.
execute_pythonstays off until the user enables Allow connected agents to run Python in the plugin preferences. APermissionErrormeans ask for it or stay on the specific tools. A refused spelling (quit, factory reset, file deletion) changed nothing: rewrite the call.- Budget every call: the plugin stops a call after 120 s and some agent clients stop waiting after 60 s. Make one logical change per call, so one Undo reverts it, and send bakes, QuadriFlow on dense meshes, turntables, playblasts and final renders to a headless Blender working on a saved copy.
- A timed-out call has an unknown outcome: read the scene again before retrying, never resend it blindly.
- The plugin's tools never save the user's own file. The live channel's stage backup
(
save_as_mainfile(..., copy=True)throughexecute_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):
| Action | Headless | GUI session |
| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------- |
| Voxel remesh, QuadriFlow, multires subdivide, modifiers, bmesh, UV ops with edit-mode context, Cycles/EEVEE/Workbench renders, baking | yes | yes |
| bpy.ops.brush.asset_activate, dyntopo toggle | yes | yes |
| Brush strokes (sculpt.brush_stroke, paint.image_paint, paint.weight_paint) | no (poll fails) | yes, via scripts/bx_gui.py |
| paint.mask_flood_fill, sculpt.mesh_filter | CRASHES Blender | yes, via bx_gui.run() |
| Programmatic sculpting on mesh data | yes, scenario-blender-sculpting/scripts/bx_sculpt.py | yes |
2. The expert loop (every domain)
- Establish the brief in numbers: purpose (film, game engine, still, animation), budgets (tris, texture size, frame range), style (stylized or realistic), references. When the brief is silent, choose a documented default from the domain skill and write it down.
- Plan the stages the domain skill defines. Never start with detail.
- Build one stage with the smallest scripts that do it.
- Gate the stage: run the measurable checks (
scripts/bx_audit.pyfor 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 userender_stillat about 768 px wide orscreenshot_viewport, and keep review sheets near 1600 px (res=400for four views and three modes). Judge with the domain'sreferences/critique.md. - Fix before advancing. A problem found at blockout costs one script; found after texturing it costs the stage.
- Deliver with evidence: run the delivery gate (
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.
3. Persona pipelines
| Persona / brief | Skill chain | Deliverable | | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | Character artist, stylized or realistic | scenario-blender-sculpting, scenario-blender-retopology, scenario-blender-uv-baking, scenario-blender-texturing-shading, scenario-blender-hair | sculpt, animation-ready low poly, UVs, baked maps, materials | | AI-mesh finisher (Scenario 3D output to production) | gate the generated asset, scenario-blender-retopology (or cleanup + remesh), scenario-blender-uv-baking (bake FROM the generated high), scenario-blender-texturing-shading; generation itself: scenario-3d | clean, UV'd, baked asset at a stated budget | | Game asset artist | scenario-blender-hard-surface or scenario-blender-sculpting, scenario-blender-retopology (game budget), scenario-blender-uv-baking, scenario-blender-texturing-shading, scenario-blender-export | low poly + PBR set, exported glTF/FBX | | Rigger / character TD | scenario-blender-rigging | rig with controls, weights, deformation tests | | Animator | scenario-blender-previs-storyboard (shot planning), scenario-blender-animation | blocked, splined, polished shot + playblast | | Story / previs artist | scenario-blender-previs-storyboard, scenario-blender-grease-pencil
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
hyperframes
88.2kAI video you can actually edit. HyperFrames is a free, open-source AI video editor. Describe any video and get a real project you can change down to the frame.
ruflo
82.3k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
