Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.
Install with Tessl CLI
npx tessl i github:cloudai-x/threejs-skills --skill threejs-fundamentals99
Does it follow best practices?
Validation for skill structure
Discovery
100%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 strong skill description that effectively communicates both capabilities and usage triggers. It uses proper third-person voice, lists specific Three.js concepts, and provides clear guidance on when to select this skill. The description is concise yet comprehensive for its domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'scene setup, cameras, renderer, Object3D hierarchy, coordinate systems' - these are distinct, concrete Three.js concepts rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems') and when ('Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: '3D scenes', 'cameras', 'renderers', 'object hierarchies', 'transforms'. These match how developers naturally describe Three.js work, though could benefit from mentioning 'Three.js' in the trigger clause. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Three.js with distinct technical triggers like 'Object3D hierarchy', 'coordinate systems', and 'renderer' that are unlikely to conflict with other skills. The Three.js context makes this clearly distinguishable. | 3 / 3 |
Total | 12 / 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 Three.js fundamentals skill that exemplifies good skill design. It provides comprehensive, executable code examples organized in a logical progression from basic setup to advanced patterns, all while maintaining token efficiency by avoiding explanations of concepts Claude already knows. The content is immediately actionable with copy-paste ready code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing code examples without unnecessary explanations of basic concepts. Every section delivers actionable information without padding or verbose descriptions of what Three.js is. | 3 / 3 |
Actionability | Excellent executable code throughout - the Quick Start is copy-paste ready, all API examples are concrete with real parameters, and common patterns include complete, working implementations for cleanup, animation, and responsive handling. | 3 / 3 |
Workflow Clarity | For a reference-style skill covering fundamentals, the workflow is appropriately clear. The Quick Start demonstrates the complete setup sequence, and the cleanup pattern shows proper disposal order. No destructive batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from Quick Start to Core Classes to Math Utilities to Common Patterns. The 'See Also' section provides one-level-deep references to related skills for geometry, materials, and lighting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 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 |
Total | 14 / 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.