Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill 3d-web-experience73
Quality
59%
Does it follow best practices?
Impact
99%
1.19xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/3d-web-experience/SKILL.mdQuality
Discovery
54%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively identifies its technical domain with good trigger terms for 3D web development technologies, making it distinctive. However, it critically lacks explicit 'when to use' guidance and appears truncated, significantly limiting Claude's ability to know when to select this skill over others. The description reads more like a topic list than actionable selection criteria.
Suggestions
Add an explicit 'Use when...' clause specifying triggers like 'when the user asks about Three.js, 3D animations, WebGL shaders, or building interactive 3D web experiences'
Complete the truncated description and add concrete action verbs describing what the skill does (e.g., 'Creates 3D scenes, implements camera controls, optimizes WebGL performance')
Include file extensions or project indicators that would trigger selection (e.g., '.glb files', '.gltf models', 'three.js projects')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (3D web experiences) and lists technologies (Three.js, React Three Fiber, Spline, WebGL) plus some use cases (product configurators, 3D portfolios, immersive websites), but the description is truncated ('and bringing ...') and doesn't provide comprehensive concrete actions like 'create', 'animate', or 'optimize'. | 2 / 3 |
Completeness | The description only addresses 'what' (expertise areas and technologies) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The truncation also suggests incomplete information. | 1 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Three.js', 'React Three Fiber', 'Spline', 'WebGL', '3D', 'interactive 3D scenes', 'product configurators', '3D portfolios', 'immersive websites' - these are terms developers and designers would naturally use when seeking help with 3D web development. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on 3D web technologies (Three.js, React Three Fiber, Spline, WebGL) creates a clear niche that is unlikely to conflict with general web development or other skills. The specific technology stack makes it distinctly identifiable. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable 3D web development guidance with executable code examples and useful comparison tables. The main weaknesses are the lack of validation/verification steps in workflows and some unnecessary introductory content. The anti-patterns section adds practical value but the overall structure could benefit from better progressive disclosure.
Suggestions
Add validation checkpoints to the 3D Model Pipeline (e.g., 'Verify GLB loads in online viewer before deploying', 'Check console for WebGL errors')
Remove or condense the Role description and Capabilities list - they don't add actionable value
Split detailed API references or advanced patterns into separate linked files (e.g., R3F-ADVANCED.md, OPTIMIZATION.md)
Add error handling examples for common 3D loading failures (model not found, WebGL not supported, mobile fallbacks)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('You bring the third dimension to the web') and the Capabilities list is redundant given the patterns that follow. However, the code examples and tables are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable code examples for Spline, React Three Fiber, GLTF compression commands, and scroll-driven 3D. The bash commands and JSX snippets are copy-paste ready with real imports and proper syntax. | 3 / 3 |
Workflow Clarity | The 3D Model Pipeline has a clear 6-step sequence, but lacks validation checkpoints. There's no verification step after compression or guidance on what to do if the model doesn't load correctly. The decision tree is helpful but workflows for error recovery are missing. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections with tables and code blocks, but everything is inline in one file. The 'Related Skills' section mentions other skills but doesn't link to detailed reference materials. Some patterns (like the full optimization pipeline) could be split into separate files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.