blender-core

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 Blender code). No account, no API key, no paid service, and nothing is sent anywhere. Optional, for live sessions only: a blender-mcp server connected to your open Blender; without one, the skill runs Blender in the background (headless). The host-side launcher script needs system Python 3.9 or newer. This listing installs only the blender-core skill: the 21 other blender-* skills in the same repository are NOT installed, even though SKILL.md routes tasks to them. Install "blender-core" for me. It is the foundation skill for any Blender 5.2+ task an agent drives: running bpy code live through MCP or headless through the CLI, context overrides, locale-safe node lookup, enum discovery, the 5.x API changes that break old tutorials, and verification rules, with routing to the specialized blender-* skills. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-core/ folder at the pinned commit: SKILL.md, references/api-changes-5x.md, references/bpy-patterns.md, scripts/_bpyx.py, scripts/env_report.py, scripts/run_in_blender.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-core/ 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 92ab591e713d8b4cdd3ed591c813ad29df9f7ce3f90f6e84971719a6b1bdc51d - references/api-changes-5x.md: SHA-256 ccf0b52a1d9fd836eb689abcec6a878b0ac57fb32ac600476b5070b9c8d22307 - references/bpy-patterns.md: SHA-256 ba7bbc708bf198bdcdfa59d9d41d830a4ae119c24ae9457830b73d9e818e2af8 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/env_report.py: SHA-256 e628feed806dd265e0c1ce803d92591aac208a9f463d8c47cbb939476d3b347a - scripts/run_in_blender.py: SHA-256 e97e078c1b52475d386af2b8f9d27c7578a55c250ccd43ff50bed9c33d380355 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 six files: SKILL.md (7,166 bytes), two reference documents (references/api-changes-5x.md, 6,666 bytes, a 4.x to 5.2 migration table; references/bpy-patterns.md, 7,793 bytes, verified bpy snippets), and three Python scripts under scripts/. - 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 none of the three scripts contains any network code (no HTTP, no sockets, no uploads). - scripts/run_in_blender.py is the host-side launcher: it finds the local Blender executable (the BLENDER_EXE environment variable first, then PATH, then the standard install folders - that variable is the only environment value any script reads), then runs Blender headless with subprocess on a script or expression I provide, and prints only the script's JSON result. scripts/env_report.py runs inside Blender and reports version, engines, GPU devices, enabled add-ons, units, color management and scene counts as JSON. scripts/_bpyx.py is the shared helper the other scripts import (argument parsing after "--", JSON output, object and node helpers); it is a synced copy of the repository's shared/_bpyx.py. - At use time, everything runs locally in my own Blender, on files I point you at: either live in my open Blender through the optional blender-mcp execute_blender_code tool (my own local session), or headless through run_in_blender.py. SKILL.md's own safety rules apply: live sessions are my work - never read_factory_settings, never delete data the skill did not create, and save a backup copy before destructive batch edits (save_as_mainfile with copy=True). The launcher runs headless Blender with --factory-startup unless --user-prefs is passed. No use is launched by this install. - The scope is the foundation layer only: executing bpy, the 5.x API rules, and routing. SKILL.md routes specialized work (modeling, rigging, materials, export, rendering and the rest) to the other blender-* skills, which this listing does not install; 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-core folder into the agent's skills directory, in a folder named "blender-core", keeping all six files with their references/ and scripts/ subfolders. 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, set BLENDER_EXE or put Blender on my PATH if the launcher cannot find it, connect a blender-mcp server myself if I want live sessions, and install any 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.