Cameras lights
Agent Kaizen skill for Claude Code & Codex: faithful, identifier-preserving reference for Blender and the bpy Python API, operators, add-ons & extensions, .blend files, shader/geometry nodes, materials, F-curves, keyframes & animation, cameras, lights, rendering, linked libraries. Routes to six area subskills.
npx -y skills add LevyBytes/AI-SKILL-blender --skill cameras-lightsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a Blender task involves cameras, lights, rendering, render engine, EEVEE, Cycles. Part of the Blender reference router; covers cameras, lights, the render engines, and rendering behavior.
SKILL.md
1.6 KB, as published. Nobody here has run it
Blender Cameras, Lights, and Rendering Reference
Faithful, original-prose reference for cameras, lights, the render engines, and rendering behavior. Identifiers (operator names, bpy paths, enum
values, shortcuts, numbers) are preserved verbatim. One subject per file across 39 reference files.
When to use this
Use this sub-skill when the task involves cameras, lights, rendering, render engine, EEVEE, Cycles. It applies even when "Blender" is not named but
a .blend file, bpy, or a relevant operator/shortcut is in play.
Workflow
- Open
references/INDEX.md(orreferences/topics.json) and pick the one file that matches — the INDEX "Covers" column lists the subjects in each file. - Read only that file; open another only if the task spans subjects. Grep across files when a subject may be split:
rg -n "PATTERN" references/*.md. - Treat every operator name,
bpypath, enum value, shortcut, and number as an exact reference fact — never invent or paraphrase identifiers.
Gotchas
Recurring failure modes and what to do instead live in the sibling GOTCHA.md.
References
All depth lives in references/ — start at references/INDEX.md, with metadata in
references/topics.json. One subject per file.
Verification
python "$env:DEVROOT\SKILLS\skills\skill-drafting\scripts\validate_skill_package.py" "$env:DEVROOT\SKILLS\skills\blender\cameras-lights"