3d-web-experience
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 depth to web experiences.
51
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/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 has strong trigger terms with specific technology names and use cases that clearly define a 3D web development niche. However, it lacks an explicit 'Use when...' clause, which is a significant gap for skill selection. The actions described are more categorical than concrete, leaning toward domain description rather than actionable capabilities.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about 3D graphics on the web, Three.js scenes, React Three Fiber components, WebGL shaders, or building interactive 3D experiences.'
Replace vague phrases like 'bringing depth to web experiences' with concrete actions such as 'create 3D models, set up lighting and cameras, animate objects, configure materials and textures.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (3D web experiences) and lists some specific use cases like 'product configurators, 3D portfolios, immersive websites,' but the actions are more like categories than concrete actions (e.g., 'building' is the only verb, and 'bringing depth to web experiences' is vague). | 2 / 3 |
Completeness | Describes what the skill covers but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also somewhat vague ('bringing depth to web experiences'), this falls to a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Three.js', 'React Three Fiber', 'Spline', 'WebGL', '3D', 'product configurators', '3D portfolios', 'immersive websites', and 'interactive 3D scenes'. These cover a good range of terms a user working with 3D web content would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The 3D web development niche is quite distinct, and the specific technology names (Three.js, React Three Fiber, Spline, WebGL) make it very unlikely to conflict with other skills. This has a clear, well-defined domain. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong, actionable code examples across multiple 3D web technologies and covers a good breadth of scenarios from stack selection to performance optimization. However, it suffers from structural issues including duplicated headers, redundant sections (Expertise vs Capabilities), a monolithic layout that would benefit from splitting into referenced files, and workflows that lack explicit validation/feedback loops for error recovery.
Suggestions
Remove duplicated section headers (e.g., '3D Stack Selection' and '3D Model Pipeline' each appear twice) and consolidate the overlapping 'Expertise' and 'Capabilities' sections into one.
Split detailed content (validation checks, model pipeline, performance optimization) into separate referenced files and keep SKILL.md as a concise overview with clear navigation links.
Add explicit validation checkpoints and feedback loops to workflows — e.g., after model compression, verify file size and visual quality before proceeding; in the configurator workflow, add testing steps between stages.
Remove the fluffy role description paragraph ('You bring the third dimension...moments of wonder') which doesn't add actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has significant redundancy — section headers are duplicated (e.g., '3D Stack Selection' appears twice, '3D Model Pipeline' appears twice), the 'Expertise' and 'Capabilities' sections overlap heavily, and the role description is fluffy. However, the code examples themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable code examples for Spline, React Three Fiber, scroll-driven 3D, GLTF compression CLI commands, loading indicators, mobile detection, and fallback strategies. These are copy-paste ready and cover the key scenarios well. | 3 / 3 |
Workflow Clarity | The model optimization pipeline and product configurator workflows list steps in sequence, but lack explicit validation checkpoints or feedback loops. For example, the model pipeline says 'Test file size' but doesn't specify what to do if it fails, and the configurator workflow has no verification steps between stages. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to external files despite the content being extensive (~300+ lines). The validation checks, collaboration workflows, model pipeline details, and performance optimization could all be split into separate referenced files. No bundle files exist to support progressive disclosure. | 1 / 3 |
Total | 8 / 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
d68b997
- 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.