blender-workflow-recipes

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 one file, but the recipes it contains drive Blender work). No account, no API key, no paid service for this skill itself, and nothing is sent anywhere by this file. This listing installs only the blender-workflow-recipes skill, which is a single text file of playbooks and contains no script of its own: every recipe chains scripts that belong to the other blender-* skills (starting with blender-core, whose launcher or the blender-mcp route runs them), and none of those skills is installed by this listing, so the recipes cannot run end to end until the skills each recipe needs are installed separately. Two optional steps named inside the recipes, at use time only and only if I choose those recipes, involve things outside Blender: the Roblox recipe ends with an upload inside Roblox Studio (AssetService:CreateAssetAsync, in my own Studio session), and the web/AR recipe optionally calls an external gltf-transform command-line tool (optimize --texture-compress ktx2) that this skill does not install. Install "blender-workflow-recipes" for me. It is a set of nine end-to-end Blender 5.2 playbooks that chain the specialized blender-* skills in order, with a quality gate to pass before moving on and a save after every stage: a mid-poly game prop, a high-to-low baked game prop, a game character from sculpt or AI mesh to a rigged and animated export, Roblox props, accessories and avatars, cleanup of AI-generated or downloaded assets, a procedural environment, a web or AR asset, a product turntable, and a mood or weather shot. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-workflow-recipes/ folder at the pinned commit: SKILL.md only) 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-workflow-recipes/ 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 4994cf41939797e193fef00b6f5eda1a7ba6ae169e6287b5eda3f50a849b576f 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 one file only: SKILL.md (7,442 bytes). There is no scripts/ folder and no references/ folder in this skill, and the file contains no code of its own: it is nine written recipes that name scripts belonging to other blender-* skills (for example uv_pack.py, qa_check.py, bake_maps.py, rigify_build.py, export_asset.py and render_batch.py). - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. The file names no account, no API key, no telemetry and no remote service for the skill itself, and it contains no network code, no shell command of its own and no download instruction. - The execution model SKILL.md prescribes belongs to blender-core, which this listing does not install: every script a recipe calls runs headless through blender-core's run_in_blender.py launcher (python S/blender-core/scripts/run_in_blender.py --blend F.blend S/<skill>/scripts/<x>.py -- ...), or live through MCP import and run() in my own Blender session. SKILL.md defines a gate as stop and fix before continuing, and says to save after every stage (--save). - The nine recipes, in order, are: (1) a mid-poly game prop with UVs before beveling, a QA gate, LODs and an engine export; (2) a high-to-low baked hero prop (retopology, UVs, QA on both meshes, normal/AO/curvature/ID bakes, PBR material); (3) a game character from a sculpt, an AI-generated mesh (generate_3d) or a scan, retopologized, baked, rigged with Rigify, weight-checked with stress poses, converted to a game skeleton, animated and exported with its clips; (4) Roblox work (MeshPart props, rigid accessories, layered clothing from the official cage templates, and 15-part avatar bodies), ending, for batches, with an upload inside Roblox Studio through AssetService:CreateAssetAsync in my own session; (5) cleaning AI-generated or downloaded assets (import, real scale, scene audit fixes, QA, LOD cleanup, fresh UVs and rebake, never shipping a generated mesh unreviewed); (6) a procedural environment (terrain plus a geometry-nodes scatter of optimized props, kept as instances where the engine supports it); (7) a web or AR asset under a web budget, exported with meshopt and WebP, with an optional external gltf-transform optimize --texture-compress ktx2 step and a USDZ variant for iOS AR; (8) a product shot and turntable (measured PBR values, a studio turntable rig, a preview render, then the full frame range); (9) a mood or weather shot (a scene mood such as night or fog, precipitation and surface wetness or snow, lightning, and a preview gate at the final aspect ratio). - At use time, everything the recipes themselves do runs locally in my own Blender, on files I point you at, through scripts from the other blender-* skills; the only outward steps SKILL.md names are the two optional ones already stated above (a Roblox Studio upload in my own session for that recipe, and the optional local gltf-transform tool for the web recipe), plus starting an asset from a mesh I generated or downloaded elsewhere in the AI-asset recipes. No use is launched by this install. - The scope is the playbooks only: the order of stages, the gates and the budgets. All of the doing (modeling, UVs, baking, rigging, materials, export, rendering, weather and the rest) belongs 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-workflow-recipes folder into the agent's skills directory, in a folder named "blender-workflow-recipes", keeping its single SKILL.md file. 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, and install blender-core plus each specialized blender-* skill a recipe needs separately if I want that recipe to actually run; 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.