blender-texture-baking

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. The skill's script runs inside Blender and uses numpy, which ships with Blender. SKILL.md assumes the execution model of the separate blender-core skill (how an agent runs Blender code, live through MCP or headless through the CLI); blender-core is NOT installed by this listing. Optional, for live sessions only: a blender-mcp server connected to your open Blender; without one, the script can be run through Blender's own command line in the background (headless). Install "blender-texture-baking" for me. It bakes texture maps in Blender 5.2 Cycles: high-to-low-poly normal maps with cage or extrusion, AO, curvature, ID and thickness maps, base color / roughness / metallic converted from procedural materials, ORM packing, OpenGL vs DirectX normal conventions, margins, GPU baking, and fixes for skewing, waviness and seams. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-texture-baking/ folder at the pinned commit: SKILL.md, scripts/_bpyx.py, scripts/bake_maps.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-texture-baking/ 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 b02a766f81399e3a596d450033413df94bc00ce880e96d8d5f5342bf512a3233 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/bake_maps.py: SHA-256 16b27115c8bb19f9d4b2162a67467df9b3f9f720dcc365497a7443be9cab5e0a 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,713 bytes) and two 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 neither script contains any network code (no HTTP, no sockets, no uploads). Neither script reads any environment variable. - scripts/bake_maps.py runs INSIDE Blender (it imports bpy and numpy, both shipped with Blender). It bakes the maps I ask for with Cycles: high-to-low (selected-to-active) when I name high-poly objects, or a self-bake that converts the low object's own procedural materials into textures when I do not. It picks a GPU compute backend (OptiX, CUDA, HIP, Metal or oneAPI) through the Cycles preferences and falls back to CPU, creates the target images with the right color spaces, and writes PNG files named T_<name>_<suffix>.png into the output folder I choose (by default //textures, relative to the open .blend file). While baking it temporarily rewires material node trees (an Emission override reads the Principled inputs for base color, metallic and opacity; an Ambient Occlusion node feeds the thickness map), switches the render engine to Cycles, and restores the previous engine and node links afterwards; its temporary target nodes are removed after each map. The only hash it computes is an MD5 of material NAMES, used to derive the flat colors of the ID map - no file contents and no personal data are hashed or read. An optional --save argument writes a copy of the .blend file to a path I give, after the bake. - scripts/_bpyx.py is the shared helper the bake script imports (argument parsing after "--", one-line JSON result output, object and node helpers); it is a byte-identical 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 Blender's command line. The bake works on my open scene and writes image files to disk; no use is launched by this install. - The scope is texture baking only. SKILL.md takes its execution model from blender-core, takes UVs from blender-retopology-uv and materials from blender-pbr-materials, and recommends running blender-asset-qa on the low and high meshes first; none of those skills 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-texture-baking folder into the agent's skills directory, in a folder named "blender-texture-baking", 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 SKILL.md assumes, install any other specialized blender-* skill separately if I want one, and connect a blender-mcp server myself if I want live sessions; 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.