threejs-lighting

Three.js lighting - light types, shadows, environment lighting. Use when adding lights, configuring shadows, setting up IBL, or optimizing lighting performance.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is threejs-lighting in CloudAI-X/threejs-skills

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise reference with executable code throughout and well-organized sections. It loses points on workflow clarity (no validation checkpoints for shadow setup) and progressive disclosure (monolithic single-file treatment with no detail offloaded to bundle files).

Suggestions

Add an explicit validation/verification checkpoint after shadow setup, e.g. confirm the CameraHelper frustum covers the scene and re-tighten it before finalizing.

Split advanced/reference material (per-light property listings, Light Probes, IBL details) into a references/ file and link to it from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Writing is lean and example-driven with terse, load-bearing prose ('Illuminates all objects equally. No direction, no shadows.') and no padding with concepts Claude already knows, matching the score-3 anchor for lean, competence-assuming content.	3 / 3
Actionability	Provides abundant fully executable, copy-paste-ready code with real constructors, imports, and property assignments (e.g. RGBELoader, PMREMGenerator, RectAreaLightUniformsLib), matching the score-3 anchor.	3 / 3
Workflow Clarity	The Shadow Setup section uses a clear numbered sequence ('1. Enable on renderer / 2. Enable on light / 3. Enable on objects') but lacks explicit validation checkpoints or error-recovery feedback loops, fitting score 2.	2 / 3
Progressive Disclosure	Well-headed sections aid navigation, but all reference material lives inline in a long encyclopedic single file with no bundle files offloading detail (e.g. per-light property listings, the 'Light Probes (Advanced)' section), fitting score 2.	2 / 3
	Total	10 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that names concrete capabilities and provides an explicit 'Use when...' trigger clause. Its main weakness is relying on the technical acronym 'IBL' and missing common natural phrasings like 'environment lighting' as trigger terms.

Suggestions

Replace or supplement the jargon term 'IBL' with natural phrasing users would say, e.g. 'setting up environment lighting (IBL/HDR)'.

Add common trigger variations such as 'environment maps', 'HDR lighting', or 'lightmaps' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and sub-areas — 'light types, shadows, environment lighting' and triggers 'adding lights, configuring shadows, setting up IBL, or optimizing lighting performance' — matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what ('Three.js lighting - light types, shadows, environment lighting') and when via an explicit 'Use when...' clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Has several natural terms ('adding lights', 'configuring shadows', 'lighting performance') but leans on the jargon acronym 'IBL' and omits common variations like 'environment lighting' or 'HDR' as triggers, fitting score 2.	2 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Three.js lighting) with distinct triggers (shadows, IBL, lighting performance) unlikely to fire for the wrong skill, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: calesthio/OpenMontage
Path: .agents/skills/threejs-lighting/SKILL.md
Commit: 0af32ce

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.