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.

62

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A well-structured, highly actionable skill body with concrete code and decision aids, but it is verbose in places and lacks validation feedback loops in its asset workflows. Splitting the larger reference material into bundle files would improve progressive disclosure.

Suggestions

Add explicit validate-and-retry checkpoints to the model optimization pipeline (e.g., verify file size and integrity after gltf-transform, re-run if it exceeds targets).

Move detailed code examples and the Validation Checks into reference files (e.g., references/optimization.md, references/validation.md) and link to them from the body to reduce inline bulk.

Trim the atmospheric 'Role' paragraph and de-duplicate the 'When to Use' list against the description to tighten conciseness.

DimensionReasoningScore

Conciseness

Largely efficient tables, code blocks, and a decision tree, but the 'Role'/'You bring the third dimension' prose and the repeated 'When to Use' list add some unnecessary padding; could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready code (React Three Fiber, Spline, gltf-transform commands), comparison tables, and a decision tree giving executable guidance.

3 / 3

Workflow Clarity

Workflows (optimization pipeline, configurator, portfolio) are sequenced and there is a Validation Checks section, but batch/destructive asset processing lacks explicit validate-then-retry checkpoints, capping clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the ~370-line body is a single monolithic document with code references and validation detail that could be split into separate files; sections are organized but content that should be separate is inline.

2 / 3

Total

9

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific third-person description with good trigger terms and a clear niche, but it omits an explicit 'Use when...' clause so it does not fully answer when Claude should invoke it. Adding a trigger clause would raise completeness to the top level.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when the user mentions 3D websites, Three.js, WebGL, React Three Fiber, Spline, or product configurators') so completeness and trigger guidance are explicit.

Consider folding the natural trigger phrases (3D website, WebGL, Spline) into the description rather than relying only on the separate 'When to Use' section in the body.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and domains ('building 3D experiences', 'Covers product configurators, 3D portfolios, immersive websites'), matching the anchor for several specific concrete actions.

3 / 3

Completeness

Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause; 'Covers product configurators...' is descriptive rather than explicit when-guidance, so completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes natural terms users would say ('Three.js', 'React Three Fiber', 'WebGL', 'Spline', '3D'), giving good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

The 3D web niche with specific tools (Three.js, WebGL, Spline) is clearly distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-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.