Individual skill
scenario-godot-rendering-lighting
Use when lighting or rendering a Godot 4.7 3D scene: pick a renderer (Forward+, Mobile, Compatibility), choose GI (SDFGI, VoxelGI, LightmapGI, reflection probes), bake lightmaps without a mouse, tune WorldEnvironment, tonemapper (AgX, ACES, Filmic), glow, fog, volumetric fog and god rays, shadows and shadow acne, quality presets for PC and phones, Compositor post effects, or when 'my scene looks flat', 'too dark indoors', 'light leaks', 'lightmap is black', 'looks different on mobile'.
skills/game-engines/godot/scenario-godot-rendering-lighting/SKILL.md
Source commit f29bf06ab89088695ed3431ac99d20a090441a2f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,601
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- blender Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- codex Repository topic
- game-assets Repository topic
- game-development Repository topic
- generative-ai Repository topic
- image-generation Repository topic
- mcp Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 19,867 bytesreferences/critique.mddoc · 4,111 bytesreferences/expert-notes.mddoc · 12,606 bytesreferences/gui-paths.mddoc · 12,024 bytesreferences/procedures.mddoc · 20,843 bytesreferences/sources.mddoc · 10,220 bytesscripts/agentkit/rendering/compositor/grayscale.glslasset · 923 bytesscripts/agentkit/rendering/compositor/post_effect.gdasset · 3,418 bytesscripts/agentkit/rendering/compositor_tools.gdasset · 1,839 bytesscripts/agentkit/rendering/gi_bake.gdasset · 9,693 bytesscripts/agentkit/rendering/graphics_tiers.gdasset · 5,121 bytesscripts/agentkit/rendering/light_audit.gdasset · 14,224 bytesscripts/agentkit/rendering/lookdev.gdasset · 5,924 bytesscripts/agentkit/rendering/sweep.gdasset · 7,818 bytesscripts/gd_lighting.pyruns · 10,604 bytes
Read excerpt
# Godot rendering and lighting (lighter / graphics technical artist)
Target: Godot 4.7.2.stable, macOS Apple Silicon (Metal by default).
Expert level here means that lighting comes from a measured loop: a calibration scene, one variable
at a time, a rendered image looked at after every change, numbers on that image, and a GPU cost for
every effect. The renderer and the GI method are chosen first, because they decide what the other
settings can do. The art direction (value pattern, warm and cool, focal contrast) is judged on
pixels the agent actually opened, never on the inspector. If a sibling skill named here is missing
from your available skills, load it with `skill_get` (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
**REQUIRED BACKGROUND:** scenario-godot-expert (channels, `gd_run`, the review loop, 4.7 traps).