blender-weather-fx

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 inside your own Blender). 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, which this listing does NOT install: its scripts run inside Blender, either imported in a live session (for example through a blender-mcp server you connect yourself) or run by Blender in the background on a .blend file. This listing installs only the blender-weather-fx skill: the 21 other blender-* skills in the same repository are NOT installed, even though SKILL.md works alongside several of them. Install "blender-weather-fx" for me. It adds weather effects to Blender 5.2+ scenes: looping Geometry Nodes rain, snow, dust, ash and embers that stop on the ground and splash, reversible wet surfaces and puddles with animated ripples, streaks on walls, snow cover with real thickness, storm lightning with multi-stroke flashes and a branching bolt, and weather masks you can export for game engines. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-weather-fx/ folder at the pinned commit: SKILL.md, references/realtime-engines.md, references/weather-values.md, scripts/_bpyx.py, scripts/lightning.py, scripts/precipitation.py, scripts/surface_weather.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-weather-fx/ 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 e3137eb02f4b2c2d7d9a5cc4d0abbf1324c835f7454baf97a963e4aebde2465e - references/realtime-engines.md: SHA-256 c7584f496ba56c115ab809034cbabee41afa008236553c9436f814c7341d78ec - references/weather-values.md: SHA-256 c8be7c985f3d28833b075e71257dd5130d8487ce0b63716a9f237f76592295c3 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/lightning.py: SHA-256 68177d83b754e8140ea8807962c8d3c984667c32332ed6a258c15d271750854e - scripts/precipitation.py: SHA-256 063fde91806f683b01172a1478c946a6bf8fd7b7f451f76111017766873f047b - scripts/surface_weather.py: SHA-256 498e69a4af740cd2cd341e4fcb33bc3a7d15621bf19cdfbe4dae2ca56619ac20 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 seven files: SKILL.md (6,649 bytes), two reference documents (references/weather-values.md, 3,142 bytes, the physical values and look library for rain, wet surfaces, snow, dust, ash, embers and lightning; references/realtime-engines.md, 2,659 bytes, how to export the weather masks and snow meshes for Unreal, Unity, Godot and Roblox), and four Python scripts under scripts/. - 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). None of them reads any environment variable, and none of them starts a subprocess: they only run inside Blender, through its bpy API. The word "socket" in the scripts means a Blender node socket, not a network socket. - scripts/precipitation.py builds a looping Geometry Nodes system named ENV_Weather_<Type> for rain, snow, dust, ash or embers: particles fall at real speeds in a world-fixed box covering what the camera sees, stop on the --ground objects you name (raycast), rain spawns splash crowns on impact, and the count is capped at 400,000 by default. scripts/surface_weather.py inserts one ENV_Weather shader group in front of each Principled BSDF of the target objects' materials to add wetness, puddles, animated ripples, wall streaks and snow, and can add real snow thickness with an ENV_SnowCover Geometry Nodes modifier and write an ENV_Weather vertex-color mask for engines; it records the original material links and values on the material itself, and its --remove mode restores them exactly. scripts/lightning.py keys a storm flash: a cool ENV_Storm_Flash sun light, a branching emissive ENV_Storm_Bolt curve and a flash on the world background, with several return strokes a few frames apart and linear interpolation; re-running it replaces the previous ENV_Storm_* objects. scripts/_bpyx.py is the shared helper the other scripts import (argument parsing after "--", compact JSON output, object and node helpers); it is a synced copy of the repository's shared/_bpyx.py, and its shared command-line wrapper can save the .blend file only when a --save path is passed. - At use time, everything runs locally in my own Blender, on files I point you at, and only changes the scene I am working on: new ENV_Weather and ENV_Storm objects, collections, node groups and materials inside that .blend, plus the material changes described above. Two cautions from SKILL.md itself: surface_weather changes shared materials, so every object using one of those materials gets the weather too (duplicate a material first to limit it), and a weather scene is normally built in an order - sky, sun or moon, fog and mood from blender-time-of-day first, then weather, with rendering settings from blender-rendering. No use is launched by this install. - The scope is weather effects only. SKILL.md states that the execution model is in blender-core, and it points to blender-time-of-day for sky and mood, blender-rendering for render settings, blender-scene-setup for real scale, blender-asset-qa for checking snow geometry before export, and blender-texture-baking and blender-game-optimization for engine exports - none of those skills is installed by this listing; 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-weather-fx folder into the agent's skills directory, in a folder named "blender-weather-fx", keeping all seven files with their references/ and scripts/ subfolders. 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 and the other blender-* skills I want separately, connect a blender-mcp server myself if I want live sessions, and check a scene with a real render before judging rain or snow; 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.