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 covering key 3D web technologies and a distinct niche, but lacks an explicit 'Use when...' clause which significantly hurts completeness. The capability descriptions lean toward categories and marketing language ('bringing depth to web experiences') rather than concrete actions. Adding explicit trigger guidance and replacing vague phrases with specific actions would substantially improve it.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Three.js, React Three Fiber, WebGL, 3D rendering on the web, or building interactive 3D scenes.'
Replace vague phrases like 'bringing depth to web experiences' with concrete actions such as 'set up 3D scenes, configure lighting and materials, animate objects, and optimize WebGL performance.'
Include file extension or format triggers users might mention, such as '.glb', '.gltf', 'GLTF models', or '3D model loading'.
| 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 vague compared to 'create interactive 3D product configurators'). 'Bringing depth to web experiences' is fluffy. | 2 / 3 |
Completeness | Describes what it does (building 3D web experiences) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also somewhat vague, placing this at 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', 'interactive 3D scenes'. These cover both library-specific and conceptual terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The 3D web development niche is quite distinct with specific technology names (Three.js, React Three Fiber, Spline, WebGL) that clearly differentiate it from general web development or other skills. Unlikely to conflict with non-3D skills. | 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 good, actionable code examples across multiple 3D web technologies and covers a broad range of scenarios from stack selection to performance optimization. However, it suffers from structural issues: duplicated headers, a monolithic format that would benefit from splitting into referenced files, and workflows that lack explicit validation checkpoints. The content is moderately verbose with redundant sections (expertise vs capabilities, duplicated section titles).
Suggestions
Remove duplicated section headers (e.g., '3D Stack Selection' and '3D Model Pipeline' each appear twice) and consolidate the overlapping expertise/capabilities lists into a single concise section.
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 to workflows — e.g., after model compression, verify file size and visual quality; after scene setup, test on mobile device or emulator before proceeding.
Remove boilerplate sections like the generic 'Limitations' that don't add 3D-specific value, and trim the 'When to Use' trigger list which largely restates the description.
| 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), and the role description, expertise list, and capabilities list overlap heavily. The 'Limitations' and 'When to Use' sections are boilerplate. However, the code examples themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable code examples for Spline, React Three Fiber, GLTF compression CLI commands, scroll-driven 3D, performance optimization patterns, and fallback strategies. These are copy-paste ready and cover the key scenarios well. | 3 / 3 |
Workflow Clarity | The model pipeline has a clear numbered sequence but lacks explicit validation checkpoints — there's no 'verify the output works' step after compression, no feedback loop for when file size exceeds targets. The product configurator and immersive portfolio workflows are high-level numbered lists without validation steps. For operations like model compression and optimization, missing verification caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files despite being long enough to warrant splitting. The validation checks, collaboration patterns, model pipeline details, and performance optimization could each be separate referenced files. There are no bundle files to support progressive disclosure, and the skill doesn't attempt to organize content across files. | 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
43af20c
- 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.