Three.js asset loading - GLTF, textures, images, models, async patterns. Use when loading 3D models, textures, HDR environments, or managing loading progress.
Install with Tessl CLI
npx tessl i github:cloudai-x/threejs-skills --skill threejs-loaders89
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 completeness. The explicit 'Use when' clause with specific scenarios makes it easy for Claude to know when to select this skill. The main weakness is that capabilities are listed as categories rather than concrete actions.
Suggestions
Rephrase capabilities as concrete actions: 'Loads GLTF/GLB models, configures texture settings, sets up HDR environments' instead of just listing asset types.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Three.js asset loading) and lists asset types (GLTF, textures, images, models) but doesn't describe concrete actions like 'load', 'convert', or 'optimize' - it's more of a category list than specific capabilities. | 2 / 3 |
Completeness | Clearly answers both what (Three.js asset loading for GLTF, textures, images, models, async patterns) and when (explicit 'Use when' clause covering loading 3D models, textures, HDR environments, or managing loading progress). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'GLTF', '3D models', 'textures', 'HDR environments', 'loading progress' are all terms developers naturally use when working with Three.js asset loading. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Three.js asset loading with distinct triggers (GLTF, HDR environments, loading progress) that wouldn't conflict with general 3D or JavaScript 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 skill document that provides comprehensive, executable coverage of Three.js asset loading patterns. The content is appropriately concise, assumes Claude's competence, and offers practical code for all major loader types. The main weakness is the lack of explicit validation workflows for complex multi-step setups like configuring Draco or KTX2 loaders.
Suggestions
Add explicit validation steps for GLTF+Draco and GLTF+KTX2 setup workflows (e.g., 'Verify decoder path is accessible before loading models')
Include a brief troubleshooting checklist for common loading failures (CORS, missing decoders, path issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, jumping directly into executable code examples without explaining what Three.js is or how loaders work conceptually. Every section provides actionable code without unnecessary preamble. | 3 / 3 |
Actionability | All code examples are complete and executable, covering the full range of loader types with copy-paste ready snippets. Includes practical patterns like promisified loaders, retry logic, and asset managers. | 3 / 3 |
Workflow Clarity | While individual loading patterns are clear, the skill lacks explicit validation checkpoints for multi-step processes like GLTF+Draco setup. Error handling is covered but not integrated into step-by-step workflows with verification points. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections progressing from Quick Start to advanced topics. References to related skills (threejs-textures, threejs-animation, threejs-materials) are clearly signaled at the end without deep nesting. | 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 (624 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 | |
Table of Contents
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.