Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.
Install with Tessl CLI
npx tessl i github:cloudai-x/threejs-skills --skill threejs-geometry92
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 well-crafted skill description that follows best practices. It uses third person voice, lists specific capabilities, includes an explicit 'Use when...' clause with natural trigger terms, and carves out a clear niche within the Three.js ecosystem that distinguishes it from other potential 3D or rendering skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'built-in shapes, BufferGeometry, custom geometry, instancing' - these are distinct, concrete capabilities within the Three.js geometry domain. | 3 / 3 |
Completeness | Clearly answers both what ('Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing') and when ('Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: '3D shapes', 'vertices', 'custom meshes', 'instanced rendering', plus technical terms like 'BufferGeometry' that developers would search for. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Three.js geometry with distinct triggers like 'BufferGeometry', 'vertices', 'instanced rendering' - unlikely to conflict with other 3D or general coding skills. | 3 / 3 |
Total | 12 / 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 reference skill that excels at providing comprehensive, executable code examples for Three.js geometry creation. The content is well-organized and token-efficient, covering everything from basic shapes to advanced instancing. The main weakness is the lack of explicit validation workflows for common error-prone operations like buffer updates and geometry disposal.
Suggestions
Add a brief troubleshooting section or validation checklist for common issues (e.g., 'If geometry doesn't update: check needsUpdate = true', 'If memory leaks: ensure dispose() is called')
Include explicit workflow steps for the BufferGeometry modification pattern showing the validate-update-flag cycle
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting code examples without unnecessary explanations of basic concepts. Every section provides direct, actionable code without padding or verbose descriptions of what Three.js or geometry fundamentals are. | 3 / 3 |
Actionability | Fully executable code examples throughout with complete, copy-paste ready snippets. Every geometry type includes concrete constructor parameters, and advanced patterns like InstancedMesh show complete working implementations. | 3 / 3 |
Workflow Clarity | While individual code examples are clear, the skill lacks explicit validation steps or feedback loops for common pitfalls like forgetting needsUpdate flags or disposing geometry. The 'Modifying BufferGeometry' section hints at update patterns but doesn't provide a clear workflow with checkpoints. | 2 / 3 |
Progressive Disclosure | Well-organized with clear section hierarchy from Quick Start through increasingly advanced topics. References to related skills (threejs-fundamentals, threejs-materials, threejs-shaders) are clearly signaled at the end without deep nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (549 lines); consider splitting into references/ and linking | Warning |
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 | 12 / 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.