blender-retopology-uv

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 execution model lives in the separate blender-core skill from the same repository: SKILL.md states "The execution model is in blender-core", so you need blender-core installed as well for the documented way of running these scripts (live through blender-mcp or headless through blender-core's launcher); the four scripts themselves run inside Blender and import only Blender's own bpy and bmesh modules plus their shared helper. This listing installs only the blender-retopology-uv skill: the 21 other blender-* skills in the same repository are NOT installed, even though SKILL.md points to some of them for follow-up work. Install "blender-retopology-uv" for me. It turns sculpts, scans and AI-generated meshes into clean game-ready meshes and prepares their UVs for texturing and baking: automatic retopology (Quadriflow, Decimate collapse, or planar dissolve) at a triangle budget, deformation edge-flow rules for manual retopology, seam placement, unwrapping (Angle Based, Minimum Stretch, or Smart), pixel-margin packing, texel density measuring and setting, plus lightmap UV2, UDIM and mirrored-UV handling. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-retopology-uv/ folder at the pinned commit: SKILL.md, scripts/_bpyx.py, scripts/auto_retopo.py, scripts/texel_density.py, scripts/uv_pack.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-retopology-uv/ 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 fc3cbc91a3d2de13b3dbf8ed261b348a9cd05a2576849d83029d93388c34deed - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/auto_retopo.py: SHA-256 d4e53e2a754f6d6675bc03b04410b7e41e147521cf4e9ba0c87e419deea01662 - scripts/texel_density.py: SHA-256 9fd15366aa20aa3005163745b12aae216c0b23a5fdafa0bbec98c1786f0c3cd6 - scripts/uv_pack.py: SHA-256 38746beb008b1f5324a9851b522308933d77bbf4ad660134d2cd7e360a95489f 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 five files: SKILL.md (5,127 bytes) and four Python scripts under scripts/. There is no references/ folder in this skill. - 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 four scripts contains any network code (no HTTP, no sockets, no uploads) and none reads any environment variable. - scripts/auto_retopo.py makes a low-poly copy of a dense mesh named <source>_low at a triangle budget (quadriflow remeshes after a voxel remesh, decimate collapses, planar dissolves flat areas), shrinkwraps the copy back onto the source for the quadriflow and decimate methods, then hides the source object in the viewport and for rendering. scripts/uv_pack.py marks seams from sharp edges when asked, unwraps (smart project, Angle Based, or Minimum Stretch/SLIM), averages island scale and packs islands with a pixel-based margin, and can build a non-overlapping lightmap UV2 layer. scripts/texel_density.py measures texel density in px/m per UV island and, with --set, rescales islands to a target density and repacks them. scripts/_bpyx.py is the shared helper the other scripts import (argument parsing after "--", one-line JSON output, object and node helpers); it is a synced copy of the repository's shared/_bpyx.py. The shared helper's optional --save flag saves the .blend file to a path I provide, only when that flag is passed. - At use time, everything runs locally inside my own Blender, on meshes in files I point you at, following the execution model defined by the separate blender-core skill (live in my open Blender through blender-mcp, or headless through its launcher). The scripts edit the meshes I name: they create the <name>_low copies, hide the source objects, rewrite UV maps, and save the .blend only if a save path is passed. No use is launched by this install. - The scope is retopology and UVs only. SKILL.md points follow-up work to other blender-* skills that this listing does not install (triangle budgets and game optimization to blender-game-optimization, UV quality checks to blender-asset-qa, baking to blender-texture-baking); 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-retopology-uv folder into the agent's skills directory, in a folder named "blender-retopology-uv", keeping all five 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 the blender-core skill separately since this skill's execution model lives there, connect a blender-mcp server myself if I want live sessions, 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.