threejs-lighting
Three.js lighting - light types, shadows, environment lighting. Use when adding lights, configuring shadows, setting up IBL, or optimizing lighting performance.
Install with Tessl CLI
npx tessl i github:cloudai-x/threejs-skills --skill threejs-lighting95
Does it follow best practices?
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with explicit 'Use when' triggers and good domain specificity for Three.js lighting. The main weakness is that the capabilities section lists categories rather than concrete actions, which could be more specific about what operations the skill enables.
Suggestions
Replace category listing with specific actions: 'Configure point/spot/directional lights, set up shadow maps, implement HDR environment lighting' instead of 'light types, shadows, environment lighting'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Three.js lighting) and lists categories (light types, shadows, environment lighting) but doesn't specify concrete actions like 'create point lights', 'configure shadow maps', or 'set up HDR environment maps'. | 2 / 3 |
Completeness | Clearly 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'lights', 'shadows', 'IBL' (image-based lighting), 'lighting performance'. These are terms developers naturally use when working with 3D lighting. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche - Three.js lighting is distinct from general 3D work, other Three.js skills (geometry, materials, animation), and generic lighting concepts. Terms like 'IBL' and 'Three.js' create clear boundaries. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent reference skill that efficiently covers Three.js lighting with executable code examples, clear organization, and appropriate depth. The overview table provides quick reference while detailed sections offer complete, working code. The content respects token budget while being comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting code examples and tables without unnecessary explanation. It assumes Claude knows what Three.js is and jumps straight into actionable content without explaining basic concepts. | 3 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code examples with proper imports. The code is complete with constructor parameters documented inline and runtime modification examples included. | 3 / 3 |
Workflow Clarity | The shadow setup section provides clear numbered steps (1. Enable on renderer, 2. Enable on light, 3. Enable on objects). For a reference-style skill covering multiple light types, the organization is logical and each section is self-contained. | 3 / 3 |
Progressive Disclosure | Content is well-organized with a quick start, overview table, then detailed sections per light type. References to related skills (threejs-materials, threejs-textures, threejs-postprocessing) are clearly signaled at the end without deep nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
- 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.