blender-hardsurface-modeling

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 (its workflows, modifier names and Python API notes are written and tested for Blender 5.2 LTS+; the README and SKILL.md both state this). Install Blender yourself first if you do not have it: do not install Blender, any add-on, any package or any other skill during this install. No account, no API key, no paid service and no telemetry are required for the install itself. Copying the skill folder itself does not run Blender or any of its scripts. Install "blender-hardsurface-modeling" for me. It is a hard-surface and prop modeling skill for Blender: a SKILL.md playbook (blockout-to-detail flow, mid-poly vs high-to-low vs subdivision workflows, non-destructive modifier stacks, topology and shading rules) plus two Python helper scripts that run only inside Blender at use time. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-hardsurface-modeling/ folder at the pinned commit: SKILL.md and scripts/) 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-hardsurface-modeling/ 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 2bf819ed1e213909955fd70214085c0e07bb65e17f6d479573fabf18cd295c09 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/apply_stack.py: SHA-256 95127944b90646b75c73c55cb47d2a4a8e9616b4edd1c0489b94132bcd7f24e9 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 both 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 three files only: SKILL.md (5,641 bytes), scripts/_bpyx.py (4,503 bytes) and scripts/apply_stack.py (4,877 bytes). SKILL.md is the playbook: pick a workflow first (mid-poly bevel + weighted normals, high-to-low bake, or subdivision), block out at real scale, apply scale before bevels/booleans, build the stack in order Mirror, Booleans, Bevel, Weighted Normal (Triangulate only at export), check shading, and follow the stack, topology and cylinder-segment rules it lists. It also shows the Blender 4.0+ edge-attribute names (bevel_weight_edge, crease_edge, sharp_edge) from Python. - 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, HTTP, socket, subprocess or package-install code: both scripts import only Blender's bpy module and the Python standard library (argparse, json, sys, os, math), plus apply_stack.py importing its sibling _bpyx.py. - At use time, everything runs locally inside Blender on files and objects I point you at, and only when I ask you to use the skill, which is a separate step from this install. scripts/apply_stack.py builds (and, only with its --apply flag, applies) a modifier stack prefixed HS_ on named mesh objects, with presets midpoly, subd and render, boolean cutters I name, and it prints one compact JSON result line. scripts/_bpyx.py is its shared helper (arguments after --, JSON output, object selection, triangle counts). The only file write at use time is a .blend save, and only when a --save path is explicitly passed at use time; nothing is uploaded and no external host is contacted at use time. - SKILL.md says the execution model lives in a separate skill, blender-core, and says to run another separate skill, blender-asset-qa, after every modeling pass. Neither of those skills is part of this listing and neither is installed here; this install is the blender-hardsurface-modeling folder only. The repository contains 22 skills in total and its upstream installer (install/install.sh, install/install.ps1, or the Claude Code plugin route in the README) would install all of them: do not use that installer for this listing. - Blender 5.2 LTS+ is a use-time prerequisite, not something to fetch now: do not download or install Blender, a Blender MCP server, or any other skill or package during this install. 3. When I say "yes, install", install it as a skill: copy the whole blender-hardsurface-modeling folder into the agent's skills directory, in a folder named "blender-hardsurface-modeling", keeping all three files and their scripts/ subfolder exactly as fingerprinted. 4. Verify with no network calls: frontmatter valid, files in place, fingerprints still matching after the copy. 5. Report what was installed, where, and what I still need to do myself (for example: have Blender 5.2 LTS or newer installed myself before any use, provide any .blend file and object names myself, and decide myself on any --apply or --save use; using the skill is a separate step that only starts when I ask for it, and no use-time run happens during this install). 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.