blender-scene-setup

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites: Blender 5.2 LTS or newer is required to USE this skill (installing it is only copying files, but every use runs code inside Blender, through Blender's own Python). No account, no API key, no paid service, and nothing is sent anywhere. This skill has no host-side launcher of its own: its audit script runs inside Blender, either in the background from Blender's command line or imported in a live session. SKILL.md states that the execution model and verification steps live in the separate blender-core skill, which this listing does NOT install. This listing installs only the blender-scene-setup skill: the 21 other blender-* skills in the same repository are NOT installed, even though SKILL.md points to some of them. Install "blender-scene-setup" for me. It sets up and audits Blender scenes the way studios do: metric units at real-world scale, a per-asset collection layout, Unreal-style naming conventions, origins, linking versus appending and library overrides, asset libraries and catalogs, and an audit script that flags hygiene problems before handoff or export. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-scene-setup/ folder at the pinned commit: SKILL.md, scripts/_bpyx.py, scripts/scene_audit.py) Pinned version: install the code at commit 71d031dab8bc6729504d11a78cbe91945401045f exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/EL4CTEO/blender-skills into a temporary folder, check out commit 71d031dab8bc6729504d11a78cbe91945401045f, and copy the skills/blender-scene-setup/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-19: [FINGERPRINTS] - SKILL.md: SHA-256 0860bc29f8d7af633bdf475b36884cef8f9acb4a5988a47be6deeecdb56bb0b2 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/scene_audit.py: SHA-256 a7baf10fb5a25acaf87d1024e5ec5fb89aee43b7ebff0f8598c4667cef64ae5b If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full and tell me in plain words: what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds three files: SKILL.md (5,340 bytes) and two Python scripts under scripts/. This skill has no references/ folder. - SKILL.md (version 1.1.0) is a procedure, not code: run the audit first, set metric units at scale 1.0, build the collection layout so no object stays in the scene root, name everything with its conventions (SM_ for static meshes, SK_ for skeletal meshes, T_ for textures with suffixes like _BC, _N and _ORM, M_ and MI_ for materials, UCX_ or -col for collision), set origins (props at bottom-center on the ground, characters at the world origin between the feet, hinges at the pivot), apply rotation and scale, then re-run the audit until its issues list is empty or every remaining issue is explained. It also covers real-world scale references, linking versus appending, library overrides, asset libraries and catalogs, collection exporters, and hygiene rules (purge orphans before shipping, relative or packed image paths, never ship multi-user mesh data with unapplied scale, one active scene per delivered file). - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. The files name no account, no API key, no telemetry and no remote service, and neither script contains any network code (no HTTP, no sockets, no uploads, no subprocess, no environment-variable reads). SKILL.md mentions that Blender 5.2 itself can register remote asset libraries; that is a Blender feature it describes, and no file in this skill contacts any network address. - scripts/scene_audit.py runs inside Blender only (it imports bpy and mathutils). By default it only reports, as local JSON: the unit settings, with a warning when they are not metric at scale 1.0; unapplied or negative scale; rotated meshes; default names (Cube, Plane, Material and the like) and .001 duplicate suffixes; objects left in the scene root; meshes with no material or with empty material slots; multi-user meshes; origins far from the object; missing or packed images and images with absolute paths; the orphan data-block count; and the linked library paths. It changes nothing unless fix flags are passed: --fix purge deletes orphan data-blocks, --fix scale applies rotation and scale on single-user meshes, --fix paths makes image paths relative, and --save writes the resulting .blend to the path given. SKILL.md's own instruction is to add --fix flags only on files I own. - scripts/_bpyx.py is the shared helper scene_audit.py imports (argument parsing after "--", compact JSON output on a line starting with @@JSON@@, object selection and mode helpers, node and enum helpers); it is a synced copy of the repository's shared/_bpyx.py, byte-identical to the copy shipped in blender-core. Through it, the audit's command-line entry point can also save the .blend when --save is passed. - At use time, everything runs locally in my own Blender, on .blend files I point you at: the audit reads the scene I open and reports locally, and any fix or save happens only when I ask for those flags on my own files. No use is launched by this install. - The scope is scene setup and hygiene only. SKILL.md states that the execution model and verification steps are in blender-core, and it points exporter conversion questions to blender-export-pipelines; neither skill is installed by this listing. The repository's own installer and Claude Code plugin install all 22 skills at once and are not the route used here. 3. When I say "yes, install", install it as a skill: copy the whole blender-scene-setup folder into the agent's skills directory, in a folder named "blender-scene-setup", keeping all three files with their scripts/ subfolder. 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (for example: install Blender 5.2 LTS or newer myself if I do not have it, install blender-core separately if I want the execution model and the host-side launcher this skill refers to, and install any other specialized blender-* skill separately if I want one; using the skill is a separate step that only starts when I ask for it). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.