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. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.
Install with Tessl CLI
npx tessl i github:Dokhacgiakhoa/antigravity-ide --skill 3d-web-experienceOverall
score
62%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 excels across all dimensions. It provides specific technologies and use cases, includes natural trigger terms developers would use, has an explicit 'Use when' clause, and occupies a distinct niche in 3D web development that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and domains: 'building 3D experiences', 'product configurators', '3D portfolios', 'immersive websites', and names specific technologies (Three.js, React Three Fiber, Spline, WebGL). | 3 / 3 |
Completeness | Clearly answers both what (building 3D experiences, product configurators, portfolios, immersive websites) AND when with explicit 'Use when:' clause listing specific trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '3D website', 'three.js', 'WebGL', 'react three fiber', '3D experience'. These are exactly what developers would search for when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on 3D web development with distinct triggers like 'three.js', 'WebGL', 'react three fiber' that are unlikely to conflict with general web development or other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill file functions as a pure index/table of contents with no substantive content of its own. While it appropriately delegates to sub-skills, it fails to provide any actionable guidance, quick-start examples, or workflow clarity in the main file. The philosophical 'Role' description wastes tokens on concepts Claude already understands.
Suggestions
Add a 'Quick Start' section with a minimal executable Three.js or R3F example (10-15 lines) so users can immediately see working code
Include a brief decision tree or flowchart in the main file (e.g., 'Need quick prototype? → Spline. Need full control? → R3F') rather than just linking to sub-skills
Remove or drastically shorten the 'Role' paragraph - Claude doesn't need philosophical framing about balancing visual impact with performance
Add a simple workflow for a common task (e.g., '1. Choose stack → 2. Optimize model → 3. Implement loading → 4. Add interactions') with links to relevant sub-skills at each step
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary fluff like the philosophical 'Role' description about 'moments of wonder' and 'when 3D enhances vs showing off' - Claude doesn't need this framing. The capabilities list is also somewhat redundant given the sub-skill links. | 2 / 3 |
Actionability | The main skill file contains zero executable code, no concrete commands, and no specific examples. It's entirely a table of contents pointing elsewhere with no actionable guidance in the file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. The numbered list is just a flat index of sub-skills with no indication of when to use what, no decision flow, and no validation steps for any 3D implementation process. | 1 / 3 |
Progressive Disclosure | The skill does use sub-skills for detailed content (good), but the main file provides almost no overview content - it's essentially just a link dump. A good progressive disclosure pattern would include quick-start content or decision guidance before pointing to detailed modules. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
91%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 | |
- 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.