blender-rendering

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 Blender). No account, no API key, no paid service, and nothing is sent anywhere. A GPU is picked automatically for Cycles when one is available (OptiX, then CUDA, HIP, Metal, oneAPI, otherwise CPU); EEVEE still needs a GPU context even in the background, so on a machine without a GPU use Cycles on CPU or Workbench instead. This listing installs only the blender-rendering skill: blender-core, which SKILL.md says holds the execution model, blender-lighting-lookdev (scene lighting and cameras), blender-geometry-nodes (named by SKILL.md for describing compositor nodes) and the 19 other blender-* skills in the same repository are NOT installed. Install "blender-rendering" for me. It covers rendering with Blender 5.2 Cycles, EEVEE and Workbench: preview, final and product quality presets, automatic GPU selection and matching denoiser, adaptive sampling and light paths, AgX, Khronos PBR Neutral and ACES color management, PNG, EXR and MP4 output with passes, the 5.0 compositor API, and command-line or multi-camera batch rendering. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-rendering/ folder at the pinned commit: SKILL.md, scripts/_bpyx.py, scripts/render_batch.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-rendering/ 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 ea4c7616fc1559cf8f1838e5e1cd6d49ff3c13fe716af3d8bd7aeca5877eeb45 - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/render_batch.py: SHA-256 2ee9043b297148b9d76b54fc22390e1e6062e2e27c33ab0386dcfa2fdb59c432 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,599 bytes) and two Python scripts under scripts/ (scripts/_bpyx.py, 4,503 bytes; scripts/render_batch.py, 6,960 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). The word "socket" in SKILL.md is a Blender compositor node socket, not a network socket. No script in this folder reads any environment variable. - scripts/render_batch.py runs inside Blender, not on the host by itself: it applies the chosen engine and preset to the current scene (Cycles samples, adaptive threshold and denoiser, or EEVEE render samples and raytracing), picks a GPU backend in that order OptiX, CUDA, HIP, Metal, oneAPI and falls back to CPU, sets resolution, color view and look, output format (PNG, JPEG, EXR, multilayer EXR, MP4 or WebM) and transparent film when asked, creates the output folder with os.makedirs, then renders the frames and cameras I name with bpy.ops.render.render and reports the written files and seconds per image as JSON. scripts/_bpyx.py is the shared helper it imports (argument parsing after "--", JSON output, enum and object helpers); it is a synced copy of the repository's shared/_bpyx.py. - At use time, everything runs locally in my own Blender, on a scene file I point you at: either through blender-core's routes (live through blender-mcp or headless through its launcher, neither of which this listing installs), or directly with a Blender command such as blender -b scene.blend -P render_batch.py -- --preset final --frames 1. Rendering writes image or video files only to the output path I choose, and a render can take a long time and use the GPU heavily. No use is launched by this install. - The scope is rendering only: engines, presets, sampling, denoising, light paths, color management, output formats and passes, the compositor notes, and batch rendering. SKILL.md states the execution model is in blender-core and scene lighting and cameras are in blender-lighting-lookdev, and it points to blender-geometry-nodes for describing compositor nodes; none of those skills is installed by this listing, so routing and execution know-how from them is missing until they are installed separately. 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-rendering folder into the agent's skills directory, in a folder named "blender-rendering", 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, provide a GPU if I want EEVEE or fast Cycles rendering, and install blender-core, blender-lighting-lookdev or any other specialized blender-* skill separately if I want them; 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.