blender-simulation

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, and the node-based cloth and hair dynamics are Blender 5.2 features). No account, no API key, no paid service, and nothing is sent anywhere. Optional, for live sessions only: a blender-mcp server connected to your open Blender; without one, the skill is driven in Blender in the background (headless), through the blender-core launcher. This listing installs only the blender-simulation skill: the 21 other blender-* skills in the same repository are NOT installed, even though SKILL.md points to some of them. Install "blender-simulation" for me. It sets up and bakes physics in Blender 5.2: rigid bodies with density-based mass and bake-to-keyframes, classic cloth presets with pinning and colliders, the new node-based Cloth and Hair Dynamics (XPBD), Mantaflow fluids, hair curves and geometry-nodes simulation zones, all bakeable headless. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-simulation/ folder at the pinned commit: SKILL.md, scripts/_bpyx.py, scripts/sim_setup.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-simulation/ 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 c7224f4d86921caace516dc9cc436ef0dbda4910be2eb05af3234f6a120dd875 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/sim_setup.py: SHA-256 8c9f7cf99b4539343873caf707dd1b8eff8d78c55ccd19f9aa2dae26ef7150f2 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,883 bytes), and two Python scripts under scripts/ (scripts/sim_setup.py, 10,097 bytes, and scripts/_bpyx.py, 4,503 bytes). 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 neither script contains any network code (no HTTP, no sockets, no uploads), any subprocess call, or any reading of environment variables. - scripts/sim_setup.py runs inside Blender (imported as a module, or run with Blender in the background on a .blend file I provide). It sets up rigid bodies (mass computed from volume times density), classic cloth from the built-in presets (cotton, denim, leather, rubber, silk) with an optional pin vertex group and Collision modifiers on colliders, and the experimental 5.2 node-based Cloth Dynamics: for that path it appends the Cloth Dynamics and Collider node groups from Blender's own local datafiles asset library (geometry_nodes_dynamics_assets.blend, a file installed with Blender itself, read locally, nothing downloaded). It can then bake by stepping through frames in order, optionally turn rigid-body motion into keyframes, and report final positions and min_z as JSON. scripts/_bpyx.py is the shared helper it imports (argument parsing after "--", JSON output, object helpers); it is a synced copy of the repository's shared/_bpyx.py, and its command-line wrapper saves a .blend file only when a --save path is explicitly passed. - 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 tool, or in the background through the blender-core launcher (which is a separate skill, not installed by this listing). A use modifies the scene I am working on: it adds rigid-body, cloth, collision or node modifiers, changes frame ranges and cache ranges, bakes caches, and, only when asked, converts rigid bodies to keyframes or saves the .blend file. SKILL.md's own rules apply: set the frame rate and scale before tuning, always bake before rendering or exporting, and re-bake after any change because caches are invalidated. No use is launched by this install. - The scope is simulation setup and baking only. SKILL.md states that the execution model lives in blender-core and that procedural simulation zones live in blender-geometry-nodes, and it points onward to other blender-* skills (for example blender-export-pipelines for exporting baked actions, and blender-asset-qa for checking a scene); none of those skills is installed by this listing. The node-based dynamics are labelled experimental in 5.2 (no self-collision yet, no built-in wind), and fluid baking with Mantaflow is described in SKILL.md as guidance only: sim_setup.py has no fluid mode. 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-simulation folder into the agent's skills directory, in a folder named "blender-simulation", 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 its launcher and execution rules, install blender-geometry-nodes separately if I want the procedural simulation-zone guidance, connect a blender-mcp server myself if I want live sessions, and expect long bake times for fluids and high-resolution simulations; 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.