Blender Lighting & Lookdev

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, through its Python API bpy). Install Blender yourself first if you do not have it. No account, no API key and no paid service is needed to install or use the skill itself. An optional Blender MCP server is mentioned for live sessions and for one HDRI route (see below); it is not required and is not installed here. This listing installs only the blender-lighting-lookdev skill: the 21 other blender-* skills in the same repository are NOT installed, even though SKILL.md routes tasks to them. Install "blender-lighting-lookdev" for me. It is a lighting, cameras and look-dev skill for Blender 5.2: studio 3-point and product lighting, HDRI environments, sun and sky exteriors, interiors, light linking, physically based light units, camera focal lengths, composition and depth of field, cyclorama backdrops, and looping turntables for asset presentation, with a one-call script that builds a framed camera, a light rig and an optional backdrop without modifying the asset. Repository: https://github.com/EL4CTEO/blender-skills (the skill is the whole skills/blender-lighting-lookdev/ folder at the pinned commit: SKILL.md, scripts/_bpyx.py, scripts/turntable.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-lighting-lookdev/ 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 13dac79bcdd6350f7a5cf52fce8951de9c409fd3fcf6beab762782053001a6ba - scripts/_bpyx.py: SHA-256 a3339ba8a678469e8ed29510e32a7331e0235202191ca4edb977af4720819b4b - scripts/turntable.py: SHA-256 ed3db9b538fda3bd6852ea1ce83aea32e0b3e99c258577b3dd000c50a847cd93 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 both scripts, 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,341 bytes), scripts/_bpyx.py (4,503 bytes) and scripts/turntable.py (7,687 bytes). The two scripts are Blender Python: turntable.py imports only math, os, sys, bmesh, bpy and mathutils, plus the local _bpyx.py helper; _bpyx.py imports only argparse, json, sys and bpy. There is no network code, no subprocess, no package install, no environment-variable or secret reading, and no telemetry in either script. - 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 and no remote service of their own. - scripts/turntable.py runs only inside Blender, on objects I name: it builds everything in a new LD_Lookdev collection - a camera framed to the objects' bounding sphere (set the render resolution before running, because framing depends on the aspect ratio), a studio key/fill/rim area-light rig scaled to the asset (or an HDRI environment, or both), an optional 18%-grey cyclorama backdrop, and a pivot that orbits the camera, the lights and the backdrop in a seamless loop (frame N+1 equals frame 1). The asset itself is not modified; re-running the script replaces only the previous LD_-prefixed look-dev objects it created. It also sets the scene camera, the frame range and the world Background node. Only when I pass --save does the shared CLI helper write a .blend file to the path I give. - scripts/_bpyx.py is the shared helper copied into every skill of this repository (identical to shared/_bpyx.py at the pinned commit): argument parsing after "--", one compact "@@JSON@@" result line, and the optional --save handling above. It contacts no host. - At use time, the rest of SKILL.md is local work inside Blender on files I provide: lighting recipes (product, reflective, exterior, interior, portrait and stylized setups), light linking and portals, physical light units, camera and composition rules, and a look-dev approval procedure that checks a material under 2-3 different HDRIs. One use-time network touch is disclosed here before it ever happens: SKILL.md names Poly Haven (CC0) HDRIs fetched through an optional blender-mcp server's search_assets / import_asset tools, only if I already run such a server and only on a use where I ask for that route. The script itself never downloads anything: its --hdri argument only loads an HDRI file already on my machine, from a local path I give. Rendering itself is not in this folder: SKILL.md points to render_batch.py in the blender-rendering skill for rendering the turntable. - SKILL.md points to sibling skills that are NOT part of this install: the execution model lives in blender-core, render settings live in blender-rendering, and full time-of-day, night and fog environments live in blender-time-of-day; it also mentions checks in blender-pbr-materials and blender-asset-qa. Do not copy or install any sibling skill here; I will install one separately if I want it. 3. When I say "yes, install", install it as a skill: copy the whole skills/blender-lighting-lookdev folder into the agent's skills directory, in a folder named "blender-lighting-lookdev", keeping every file (SKILL.md, scripts/_bpyx.py, scripts/turntable.py). Do not use the upstream routes for this listing (the Claude Code plugin marketplace install or install/install.sh / install.ps1), because they install all 22 skills of the repository; this listing installs this one folder only, and only from the pinned commit. 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 any .blend file, asset and local HDRI file myself, connect a blender-mcp server myself only if I want live sessions or the Poly Haven route, and install any sibling skill myself, only if and when I want it; using the skill is a separate step that only starts when I ask for it, and no lighting setup, turntable or render runs 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.