MCPInstall

blender-scene-setup

Set up and audit Blender scenes the way studios do - units and real-world scale, collection layout, naming conventions (SM/SK/T/M), origins, linking vs appending, library overrides, asset libraries and catalogs, collection exporters, orphan/path cleanup. Use when starting a project, organizing a .blend, or before handoff/export.

Installs
87
Last 24h
+8
Trending rank
#9555
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/el4cteo/blender-skills --skill blender-scene-setup
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads blender-scene-setup automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Scene Setup & Hygiene

The execution model and verification steps are in blender-core.

Procedure

  1. Run scripts/scene_audit.py (add --fix purge scale paths only on files you own). It reports units, unapplied/negative scale, default names, objects in the scene root, missing images, orphans and far-off origins.
  2. Set units: Metric, Unit Scale 1.0, Length meters. Keep 1.0 even for Unreal/Roblox, because exporters handle the conversion (see blender-export-pipelines).
  3. Build the collection layout (below). Every object must be in a named collection, never the scene root.
  4. Name everything with the conventions below. Rename after every duplicate or join so no .001 suffixes remain.
  5. Set origins: props at the bottom-center (they sit on the ground at Z=0), characters at world origin between the feet, doors/hinges at the pivot.
  6. Apply rotation and scale on meshes (Ctrl+A). Keep location unless the asset should export at the origin.
  7. Re-run the audit. It's done when issues is empty or every remaining issue is intentional and explained.

Collection layout (one asset per .blend, or one collection per asset)

ASSET_Crate
├── Crate_high      # sculpt / subdiv source (exclude from export)
├── Crate_low       # game mesh(es) SM_Crate, SM_Crate_LOD1..
├── Crate_bake      # cages, bake helpers
├── Crate_collision # UCX_SM_Crate_00 (UE) / Crate-col (Godot)
└── Crate_ref       # reference images/blockout (hide_render)

Use Collection Exporters (4.2+) to define the export once per collection, then re-export with one call:

with bpy.context.temp_override(collection=col):
    bpy.ops.collection.exporter_add(name="IO_FH_gltf2")
ex = col.exporters[-1]; ex.export_properties.filepath = "//export/SM_Crate.glb"
with bpy.context.temp_override(collection=col):
    bpy.ops.collection.exporter_export(index=len(col.exporters) - 1)

bpy.ops.wm.collection_export_all() re-runs every collection exporter.

Naming conventions (Unreal-style, accepted by all engines)

TypePatternExample
Static meshSM_<Name>[_LOD#]SM_Crate_LOD1
Skeletal mesh / rigSK_<Name> / RIG_<Name> (armature object Armature or root)SK_Hero
MaterialM_<Name> / instance MI_<Name>M_Wood_Oak
TextureT_<Name>_<Suffix>: _BC base color, _N normal, _ORM (R=AO G=Rough B=Metal), _E emissive, _M maskT_Crate_ORM
CollisionUE UCX_<Mesh>_##, Godot suffix -col/-colonly/-convcolonlyUCX_SM_Crate_00
Bones/sides.L/.R suffix (Blender mirror tools depend on it)upper_arm.L
Actions<Rig>_<Clip>Hero_Run
Use ASCII only, no spaces, and PascalCase or snake_case consistently across the project.

Real-world scale reference (meters)

Door 2.0–2.1 × 0.9 · ceiling 2.4–2.7 · table 0.75 · chair seat 0.45 · counter 0.9 · stair rise 0.18 / tread 0.28 · adult human 1.7–1.8 (eyes 1.6) · car 4.5 × 1.8 × 1.5. Roblox: 1 stud ≈ 0.28 m; default character ≈ 5 studs tall. Wrong scale breaks physics, lighting falloff, DOF and texel density, so check ob.dimensions first.

Linking, appending, overrides

  • Append (libraries.load(link=False)) makes a local copy. Use it for one-off reuse.
  • Link (link=True) is read-only, updates from the source and is what pipelines use. To edit a linked collection, add a library override: ob.override_hierarchy_create(scene, view_layer, do_fully_editable=False). Only overridable properties (transforms, pose, and anything marked overridable) can change.
  • Keep library paths relative (//). Check bpy.data.libraries for broken paths.

Asset libraries

  • Mark: ob.asset_mark(); ob.asset_generate_preview(). Metadata goes in ob.asset_data (author, description, license, tags.new("wood"), catalog_id).
  • Catalogs live in blender_assets.cats.txt at the library root, one line per catalog: UUID:Path/Sub:Simple Name.
  • Register a library with prefs.filepaths.asset_libraries.new(name=..., directory=...). 5.2+: remote libraries via use_remote_url + remote_url. In 5.2 active_asset_library indices are offset by 2 ("All", "Essentials").
  • Import method per library: LINK, APPEND, APPEND_REUSE (default; reuses already-appended data).

Hygiene rules

  • Purge orphans before shipping (bpy.data.orphans_purge(do_recursive=True)). Use fake users only on purpose.
  • Image paths: relative (file.make_paths_relative), or pack for single-file delivery (file.pack_all).
  • Never ship multi-user mesh data that has an unapplied per-object scale. Instances are fine, but bake scale before export.
  • Hide helpers with hide_render=True and exclude them from export collections; viewport hiding alone isn't enough.
  • One active scene per file for delivery. Extra scenes confuse exporters (use_active_scene).

FAQ

What does the blender-scene-setup skill do?

Set up and audit Blender scenes the way studios do - units and real-world scale, collection layout, naming conventions (SM/SK/T/M), origins, linking vs appending, library overrides, asset libraries and catalogs, collection exporters, orphan/path cleanup. Use when starting a project, organizing a .blend, or before handoff/export.

How do I install blender-scene-setup?

Run npx skills add https://github.com/el4cteo/blender-skills --skill blender-scene-setup in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/blender-scene-setup/ (personal) or .claude/skills/blender-scene-setup/ (project).

Which AI agents can use blender-scene-setup?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is blender-scene-setup safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains blender-scene-setup?

It is published by el4cteo in el4cteo/blender-skills. It has 87 recorded installs.

More from el4cteo/blender-skills

View all →

blender-core

el4cteo/blender-skills

Open the skill to read its SKILL.md instructions.

120 installs

blender-asset-qa

el4cteo/blender-skills

Open the skill to read its SKILL.md instructions.

Testing & QA110 installs

blender-animation

el4cteo/blender-skills

Open the skill to read its SKILL.md instructions.

blender-export-pipelines

el4cteo/blender-skills

Open the skill to read its SKILL.md instructions.

96 installs

blender-character-rigging

el4cteo/blender-skills

Open the skill to read its SKILL.md instructions.

93 installs

blender-pbr-materials

el4cteo/blender-skills

Open the skill to read its SKILL.md instructions.

91 installs

Popular frontend & design skills

View category →

setup-matt-pocock-skills

mattpocock/skills

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Frontend & Design1.1M installs

frontend-design

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

OfficialFrontend & Design1M installs

hyperframes-animation

heygen-com/hyperframes

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

prototype

mattpocock/skills

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Frontend & Design999.2K installs

hyperframes-core

heygen-com/hyperframes

The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

Frontend & Design930.5K installs

vercel-react-best-practices

vercel-labs/agent-skills

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

OfficialFrontend & Design843.1K installs