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. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.

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 ./.agent/skills/3d-web-experience/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

This SKILL.md is essentially a table of contents with a role preamble but no substantive content. It contains no executable code, no concrete guidance, no workflows, and no examples — all value is deferred to 17 sub-skill files that are not provided. The main file fails to give Claude anything actionable to work with on its own.

Suggestions

Add at least one concrete, executable quick-start example (e.g., a minimal React Three Fiber scene setup) directly in the SKILL.md so Claude has immediate actionable guidance.

Include a brief workflow or decision tree inline (not just linked) that helps Claude determine which sub-skill to consult based on the user's request.

Add 1-2 sentence descriptions to each sub-skill link so Claude can navigate effectively without opening every file (e.g., '### 4. [Spline (Fastest Start)](./sub-skills/spline-fastest-start.md) — No-code 3D with embed workflow').

Remove the empty 'Patterns' section header and the generic role description to improve conciseness and signal completeness.

DimensionReasoningScore

Conciseness

The role description and capabilities list are somewhat verbose and explain things Claude already knows ('You know when 3D enhances and when it's just showing off'). The capabilities bullet list is essentially a feature list with no actionable content. However, the file is relatively short overall.

2 / 3

Actionability

The SKILL.md contains zero executable code, no concrete commands, no specific examples, and no actionable guidance. It is entirely a table of contents pointing to sub-skills with no inline content to act on. If all sub-skills are missing (no bundle files provided), Claude has nothing concrete to execute.

1 / 3

Workflow Clarity

There is no workflow, no sequencing, no validation steps, and no process described. The numbered list is just a directory of links, not a workflow. A user or Claude would have no idea what steps to follow for any 3D web task from this file alone.

1 / 3

Progressive Disclosure

The file does attempt progressive disclosure by linking to 17 sub-skill files, which is a reasonable structure. However, the links are not clearly signaled with descriptions of what each contains (just titles), and with no bundle files provided, we cannot verify the references exist. The 'Patterns' section header is empty, suggesting incomplete organization.

2 / 3

Total

6

/

12

Passed

Description

89%

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 solid skill description with explicit trigger guidance and good keyword coverage across both technology names and use cases. Its main weakness is that the capability description leans more toward listing categories and technologies rather than concrete actions, and includes some fluffy language like 'bringing depth to web experiences.' Overall it performs well for skill selection purposes.

Suggestions

Replace vague phrases like 'bringing depth to web experiences' with concrete actions such as 'create 3D scenes, animate models, set up lighting and cameras, build interactive 3D components.'

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 about categories of output than concrete actions (e.g., no verbs like 'create,' 'render,' 'animate'). 'Bringing depth to web experiences' is vague fluff.

2 / 3

Completeness

Clearly answers both 'what' (building 3D web experiences with specific technologies and use cases) and 'when' (explicit 'Use when:' clause listing trigger terms like '3D website, three.js, WebGL, react three fiber, 3D experience').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Three.js,' 'React Three Fiber,' 'Spline,' 'WebGL,' '3D website,' '3D experience,' 'product configurators,' '3D portfolios.' Good coverage of both library names and use-case terms.

3 / 3

Distinctiveness Conflict Risk

The 3D web development niche is quite distinct. The specific technology names (Three.js, React Three Fiber, Spline, WebGL) and use cases (product configurators, 3D portfolios) make it unlikely to conflict with general web development or other skills.

3 / 3

Total

11

/

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.

Validation10 / 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
Dokhacgiakhoa/antigravity-ide
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.