threejs-textures
Three.js textures - texture types, UV mapping, environment maps, texture settings. Use when working with images, UV coordinates, cubemaps, HDR environments, or texture optimization.
Install with Tessl CLI
npx tessl i github:cloudai-x/threejs-skills --skill threejs-textures89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 excellent trigger terms and clear 'Use when' guidance that makes it easy for Claude to select appropriately. The main weakness is that it lists topic categories rather than specific actionable capabilities, which slightly reduces specificity.
Suggestions
Replace topic categories with concrete actions, e.g., 'Load and apply textures, configure UV mapping, set up environment maps and cubemaps, optimize texture settings'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Three.js textures) and lists categories (texture types, UV mapping, environment maps, texture settings) but these are topic areas rather than concrete actions like 'apply', 'create', or 'optimize'. | 2 / 3 |
Completeness | Clearly answers both what (Three.js textures - texture types, UV mapping, environment maps, texture settings) and when (explicit 'Use when' clause with specific triggers like UV coordinates, cubemaps, HDR environments). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'images', 'UV coordinates', 'cubemaps', 'HDR environments', 'texture optimization' - these are terms developers naturally use when working with Three.js textures. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Three.js textures with distinct triggers (cubemaps, HDR environments, UV coordinates) that are unlikely to conflict with general image processing or other 3D skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive Three.js textures reference that excels in actionability and conciseness. The code examples are executable and well-organized across logical sections. Minor improvements could be made by adding validation steps for memory management operations and clearer guidance on error handling for texture loading failures.
Suggestions
Add explicit error handling patterns for texture loading failures, especially for the Promise wrapper section
Include validation checkpoints in the memory management section (e.g., how to verify textures are properly disposed)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting code examples without unnecessary explanations of basic concepts. Every section provides actionable code without verbose preambles about what textures are or how Three.js works. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. The skill provides complete, working code for every texture operation from basic loading to advanced techniques like texture pooling and procedural generation. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints for potentially problematic operations like texture disposal or render target setup. The CubeCamera section mentions 'expensive!' but doesn't provide guidance on when/how often to update. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers progressing from quick start to advanced topics. The 'See Also' section provides one-level-deep references to related skills. Content is appropriately structured for a comprehensive reference. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (629 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | 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.