threejs-lighting

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

Quality

83%

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

78%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 reference packed with copy-paste ready code and a clear shadow-setup sequence, with only minor conciseness trim opportunities. Its main weakness is progressive disclosure: at ~480 lines with no bundle files, it is a monolithic inline reference rather than an overview pointing to one-level-deep detail files.

Suggestions

Split advanced sections (Light Probes, Environment Lighting/IBL, Common Lighting Setups, Light Animation) into separate reference files under references/ and link to them from SKILL.md so the main file stays a concise overview, improving progressive_disclosure.

Trim the brief analogy descriptions ('Like a light bulb', 'Like a flashlight or stage light', 'Simulates distant light source (sun)') and obvious code comments to tighten conciseness.

Add a short verification note in the shadow-setup workflow (e.g. add a CameraHelper or confirm shadows render) to give the one multi-step section an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is dominated by terse, directly useful code with one-line descriptions per section and no conceptual padding about what Three.js or lighting is; minor analogy fragments ('Like a light bulb', 'Simulates distant light source (sun)') and a few self-evident code comments could be trimmed, but it is efficient overall.	4 / 5
Actionability	Nearly every section provides copy-paste ready, executable JavaScript with real constructor signatures, positions, and property values, and the common cases (each light type, shadow setup, IBL) are fully covered; the few undefined cross-section variables (generic 'light' in animation, 'cubeTexture' in probes) appear only in advanced examples.	5 / 5
Workflow Clarity	The 'Enable Shadows' section gives a clear numbered 1-2-3 sequence (renderer, light, objects) and the IBL section has a logical load-set-PMREM flow; validation checkpoints are absent but the domain is non-destructive, so the cap-at-3 rule does not apply and the gaps are minor.	4 / 5
Progressive Disclosure	The skill is a single ~480-line monolithic SKILL.md with no bundle files and no references to separate detail files; advanced content (Light Probes, IBL/PMREM, Common Lighting Setups, Light Animation) is inlined where it could be split into one-level-deep reference files, fitting 'content that should be separate is inline' despite good internal section headers.	3 / 5
	Total	16 / 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, third-person description that pairs a concrete capability statement with an explicit 'Use when' trigger clause covering the core lighting tasks. Minor gaps in trigger synonyms and unmentioned body capabilities (helpers, probes, animation) prevent a perfect score on specificity and trigger_term_quality.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions ('adding lights, configuring shadows, setting up IBL, or optimizing lighting performance') alongside the domain pillars ('light types, shadows, environment lighting'), but omits body-covered capabilities like helpers, light probes, and animation, so minor gaps keep it just below comprehensive.	4 / 5
Completeness	Clearly answers WHAT ('Three.js lighting - light types, shadows, environment lighting') and WHEN via an explicit 'Use when adding lights, configuring shadows, setting up IBL, or optimizing lighting performance' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say are present ('Three.js lighting', 'lights', 'shadows', 'IBL', 'environment lighting'), giving good coverage; a few common variations (e.g. 'HDR', 'environment map', specific light-type names) are missing, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Three.js lighting specifically) with distinct triggers; overlap with sibling skills (materials/textures/postprocessing) is minimal because lighting is a well-bounded subdomain.	5 / 5
	Total	18 / 20 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: 1bab711

Reviewed: about 20 hours 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.