CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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

A highly actionable, well-organized Three.js lighting reference with executable code for every light type, shadow pipeline, and IBL setup, plus valuable non-obvious details (cost table, shadow acne fixes, r183 clearcoat note). Its weaknesses are inlining an entire API reference in SKILL.md with no progressive disclosure to separate files, and re-treading basic API and helper usage Claude already knows.

Suggestions

Split per-light API detail, Light Probes, and IBL sections into clearly signaled one-level-deep reference files (e.g., "Light types: see references/light-types.md"), keeping Quick Start, the cost table, and shadow setup/debugging inline.

Trim sections that restate knowledge Claude already has — helper constructor listings, property listings like "spotLight.angle; // Cone angle", and the trivial Light Animation section — keeping only non-obvious notes such as RectAreaLightUniformsLib.init() being WebGL-only.

In the IBL section, merge the duplicated RGBELoader.load callback examples (the raw equirectangular and PMREM variants load the same file twice) into a single coherent workflow showing the preferred PMREM path.

DimensionReasoningScore

Conciseness

The format is tight (dense executable code, minimal prose), but substantial sections restate API knowledge Claude already has: helper constructor listings ("const dirHelper = new THREE.DirectionalLightHelper(dirLight, 5)"), trivial animation ("light.position.x = Math.cos(time) * 5"), and property listings ("spotLight.angle; // Cone angle"). Mostly efficient but could be tightened to the genuinely additive material (cost table, acne fixes, r183 clearcoat note).

3 / 5

Actionability

Fully executable, copy-paste-ready code throughout, covering all light types, shadow configuration ("dirLight.shadow.bias = -0.0001", "dirLight.shadow.normalBias = 0.02"), IBL pipelines ("pmremGenerator.fromEquirectangular(texture).texture"), and ready-made setups. The RectAreaLightUniformsLib.init() prerequisite and per-type gotchas are correctly captured.

5 / 5

Workflow Clarity

The shadow setup sequence is clearly ordered ("1. Enable on renderer / 2. Enable on light / 3. Enable on objects") with troubleshooting guidance ("Shadow bias (fixes shadow acne)"). This is a reference skill with no destructive or batch operations requiring validation loops, so the anchor 4 fit (clear sequence, most checkpoints) is closer than anchor 5's explicit validate/fix/retry structure.

4 / 5

Progressive Disclosure

No bundle files exist; the entire ~480-line API reference (per-light sections, IBL, Light Probes) is inlined in SKILL.md. Section structure is good, but content that clearly belongs in separate reference files (per-light API detail, advanced light probes, IBL) is inline with no external references at all, matching anchor 3.

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 description that clearly and explicitly states both what the skill covers and when to use it, with concrete trigger phrases and low conflict risk. Minor room for improvement: use verb-led capabilities and add user-facing synonyms like "HDR" or "environment map" alongside the jargon term "IBL".

DimensionReasoningScore

Specificity

Names the domain and lists several concrete capability areas ("light types, shadows, environment lighting") plus actions ("adding lights, configuring shadows, setting up IBL, optimizing lighting performance"). Falls short of anchor 5 because the 'what' is noun topics rather than a comprehensive list of concrete actions, and coverage items like helpers are absent.

4 / 5

Completeness

Explicitly answers both: what ("Three.js lighting - light types, shadows, environment lighting") and when ("Use when adding lights, configuring shadows, setting up IBL, or optimizing lighting performance") with four concrete trigger phrases, matching the anchor 5 pattern rather than anchor 4 whose 'when' could be more explicit.

5 / 5

Trigger Term Quality

Covers natural phrases users would say ("adding lights", "configuring shadows", "optimizing lighting performance") but misses synonyms like "HDR", "environment map", or "realistic lighting", and "IBL" is jargon. Better than anchor 3 since the main natural terms are present.

4 / 5

Distinctiveness Conflict Risk

Clear niche ("Three.js lighting") with triggers (lights, shadows, IBL) that would not fire for sibling skills like materials, textures, or postprocessing. Minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/threejs-lighting/SKILL.md

Reviewed

Table of Contents

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.