CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/3d-web-experience/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides genuinely useful, executable code examples across the 3D web stack with good coverage of common patterns (loading, scroll, performance, fallbacks). However, it suffers from structural issues including duplicated section headers, redundant role/expertise/capabilities sections, and a monolithic format that would benefit from splitting into separate reference files. Validation checkpoints are identified but not woven into the workflows.

Suggestions

Remove duplicated section headers (e.g., '3D Stack Selection' and '3D Model Pipeline' each appear twice) and consolidate the Role/Expertise/Capabilities sections into a single brief overview.

Integrate the Validation Checks directly into the relevant workflows as explicit checkpoint steps (e.g., after model compression, verify file size; after scene setup, test WebGL fallback).

Split detailed content (model pipeline, performance optimization, scroll patterns) into separate referenced files to improve progressive disclosure and reduce the monolithic structure.

Add a feedback loop to the model optimization pipeline: e.g., 'If output > 5MB, reduce texture resolution and re-compress; verify with a test load before proceeding.'

DimensionReasoningScore

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/Expertise/Capabilities sections overlap heavily with each other and with the description. The 'Common Scroll Effects' bullet list and some explanatory lines ('3D that responds to scroll', 'Keeping 3D fast') add little value. However, the code examples themselves are reasonably lean.

2 / 3

Actionability

The skill provides fully executable code examples across multiple frameworks (Spline, R3F, Three.js+GSAP), concrete CLI commands for model compression, specific configuration values (DPR settings, triangle counts), and copy-paste ready patterns for loading, scroll integration, fallbacks, and performance optimization.

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. The Validation Checks section identifies issues but isn't integrated into the workflows as checkpoints.

2 / 3

Progressive Disclosure

The content is a monolithic wall of text with no references to external files despite being long enough (~300+ lines) to warrant splitting. Advanced topics like GLSL shaders (listed in expertise) have no content or reference. The Collaboration section references other skills but there are no bundle files for deeper content. The structure is flat with duplicated headers creating confusion.

1 / 3

Total

8

/

12

Passed

Description

54%Scale 1-3

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 niche in 3D web development with good technology-specific trigger terms that make it highly distinctive. However, it lacks an explicit 'Use when...' clause, which is a significant gap for completeness. The actions described are more categorical than concrete—it would benefit from listing specific actions like 'create 3D scenes, animate objects, set up lighting and cameras.'

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 interactive 3D product viewers.'

Replace vague phrases like 'bringing depth to web experiences' with concrete actions such as 'create 3D scenes, animate objects, configure lighting and cameras, build interactive product viewers.'

DimensionReasoningScore

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 'when' is entirely absent (not even implied beyond the domain listing), this scores low.

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'. These cover both framework-specific and use-case-specific terms users would naturally mention.

3 / 3

Distinctiveness Conflict Risk

The 3D web development niche with specific technologies (Three.js, React Three Fiber, Spline, WebGL) is highly distinctive and unlikely to conflict with other skills. The combination of framework names and use cases creates a clear, unique identity.

3 / 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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.