threejs

Three.js skills for creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/threejs/SKILL.md

Quality

Content

37%

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

The body is token-efficient and well-sectioned, but it functions as a pointer to an upstream repository rather than a self-contained skill: it lacks executable guidance, a real workflow, and any local bundle references. Actionability and workflow clarity are the weakest dimensions.

Suggestions

Add at least one concrete, executable example (e.g., a minimal Three.js scene setup snippet or a specific install/invoke command) so the body provides actionable guidance rather than only linking out.

Provide a short, explicitly sequenced workflow (install bundle → load skill → run/verify a basic scene) with a verification checkpoint, instead of the two vague pointer steps.

Either ship the referenced assets/scripts/references locally and link them with one-level-deep signaled references, or clearly justify in the body why the skill is intentionally a thin catalogue entry pointing upstream.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept explanations Claude already knows; the ~28-line catalogue entry has no padding, so every token earns its place despite the slightly descriptive framing.	3 / 3
Actionability	The body provides no executable code or commands that accomplish the skill's actual 3D purpose — the only command is `open https://github.com/...`, and it describes ("advertises the skill", "install the upstream bundle") rather than instructing, deferring all real work to an external repo.	1 / 3
Workflow Clarity	No sequenced multi-step workflow with validation checkpoints is present; the "How to use" section gives two vague steps (inspect README, ask the agent to invoke) and the real 3D workflow is entirely absent from the body.	1 / 3
Progressive Disclosure	Sections are organized (What it does, Source, How to use) but no local bundle files exist and the only reference is an off-repo URL rather than a clearly signaled one-level-deep local reference, so content that should be split is deferred externally rather than disclosed progressively.	2 / 3
	Total	7 / 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.

The description is specific and distinctive with strong natural trigger terms, but it omits an explicit "Use when..." clause inside the description field, which caps its completeness at 2. Adding a single usage-trigger sentence would raise the completeness score.

Suggestions

Append a "Use when..." clause to the description text (e.g., "Use when building 3D scenes, WebGL visuals, or interactive 3D experiences in the browser") so the when-guidance is explicit within the description field rather than only in the frontmatter triggers.

Consider adding a concrete verb-driven action phrase (e.g., "create, animate, and render") alongside the capability list to reinforce the specificity of actions.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capability areas — "scenes, materials, controls, and post-processing" — beyond merely naming the 3D domain, matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	The description answers "what" clearly but contains no "Use when..." clause or equivalent explicit trigger guidance within the description text itself; the when-guidance lives only in the separate frontmatter triggers, so completeness caps at 2 per the rubric rule.	2 / 3
Trigger Term Quality	Triggers ("threejs", "three.js", "3d web", "webgl scene", "3d interactive") cover the natural phrasings a user would say, with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	"Three.js skills for creating 3D elements and interactive experiences in the browser" carves a clear niche with distinct triggers that are unlikely to conflict with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/threejs/SKILL.md
Commit: a2ba3ee

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.