Blender Asset QA

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: none for the install itself: no account, no API key, no paid service, and nothing else to install first. For using the skill afterwards you need Blender 5.2 LTS or newer, installed by me: the skill's two scripts run inside Blender (they import bpy, bmesh and mathutils, and review_shots.py also uses numpy, which ships with Blender). Do not install Blender, or anything else, during this install. An optional Blender MCP server lets an agent look at an open Blender session live; it is not required (the headless script path covers the same visual check) and this install does not install or configure any MCP server. Install "blender-asset-qa" for me. It is a mandatory review gate for any mesh or asset created or edited in Blender: it checks numbers first (z-fighting, floating or detached parts, inverted or inconsistent normals, non-manifold or open geometry, degenerate faces, duplicate vertices, n-gons, unapplied scale, UV problems, bad skin weights), then renders multi-angle review sheets so the result is also looked at, and it reports triangle counts, the issues fixed and any warnings I accept. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-asset-qa/ folder at the pinned commit: SKILL.md plus scripts/ with three Python files) 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-asset-qa/ 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 345c5f16c7ae9cfd31b3b58ee0642e31ce9fd406265305c03c0fdffd0fb551eb - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/qa_check.py: SHA-256 11b4fa11244bfa6719689a06eec58c050a3ad5b6d17ac0f75113f332f97b274b - scripts/review_shots.py: SHA-256 ffd4361f313592b67c124cdf0ec54b8d9866c9b29eefdac5c47731ce133d3f01 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 and all three scripts 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 four files: SKILL.md (4,667 bytes) and scripts/qa_check.py (16,590 bytes), scripts/review_shots.py (6,292 bytes) and scripts/_bpyx.py (4,503 bytes), the shared Blender helper (byte-identical to shared/_bpyx.py at the same commit). There is no dependency list and nothing else to install: the scripts import only Blender's own modules (bpy, bmesh, mathutils) plus the Python standard library, and review_shots.py also imports numpy, bundled with Blender. - 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 no script opens a network connection, reads environment variables or credential files, or launches a subprocess. - At use time, everything runs locally inside Blender, on a .blend file or open scene I point you at: qa_check.py analyses the named mesh objects together and returns one JSON result (pass or not, errors, warnings and per-object metrics); it does not save or modify the file (its CLI parser is created with save=False). review_shots.py renders Workbench views of the named objects and writes PNG view files plus one contact sheet to the output path given (by default review_sheet.png next to the .blend, or in the temp folder); to do that it temporarily changes render and shading settings, hides the other objects from the render, and adds a temporary camera (and, in wire mode, temporary wireframe copies), then restores every setting and removes the temporary objects before returning. - The skill is a fix-and-recheck loop, run only when I ask you to use it: fix every error the checker reports, re-run until it passes, and either fix each warning or accept it explicitly and report the reason to me. Any edit to my meshes happens at that use time, inside Blender, on the asset I named — never during this install. SKILL.md points to two sibling skills for specific fixes (blender-retopology-uv for UV problems, blender-character-rigging for skin weights); those skills are not part of this listing, are not installed by this install, and following those pointers is a separate decision for me. - The live visual check in SKILL.md uses an MCP "look" tool only if I already have a Blender MCP server connected to my open Blender session; the headless alternative is review_shots.py. This install installs and configures neither. - The repository also ships an installer (install/install.sh, install/install.ps1) and a Claude Code plugin route, but both install all 22 skills of the repository. Do not run them for this listing: install only the blender-asset-qa folder. 3. When I say "yes, install", install it as a skill: copy the whole blender-asset-qa folder (SKILL.md plus scripts/) into the agent's skills directory, in a folder named "blender-asset-qa", keeping every file. A manual clone followed by copying that one folder into ~/.claude/skills/ is the upstream route for a single skill; it is fine as long as every file matches its fingerprint. 4. Verify with no network calls: frontmatter valid, all four files in place and matching their fingerprints. Do not run qa_check.py or review_shots.py, and do not open Blender, as part of the verification. 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 yet, and provide any .blend file or asset myself; using the skill is a separate step that only starts when I ask for it, and it then works locally in Blender on the asset I name, writing only the review PNGs at the output path I choose). 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.