threejs

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

Quality

48%

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

36%Weight 40%Scale 1-5

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

The body functions as a catalogue/pointer entry rather than a working skill: it is brief and lightly structured but offers almost no executable guidance, repeats frontmatter information, and delegates all real content to an external repo. Actionability and workflow clarity are the weakest dimensions.

Suggestions

Replace the non-executable `open https://...` block with a concrete install command or a specific clone/copy step with real target paths.

Remove the duplicated description and Source block from the body since they already live in the frontmatter, to improve token efficiency.

Either vendor the key upstream references into local files (references/) and link to them, or clearly state that this is a thin pointer skill so the lack of local progressive disclosure is intentional.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly free of explaining concepts Claude already knows, but it restates the description verbatim and repeats the upstream/category already in the frontmatter, matching score-3 'mostly efficient but some unnecessary content that could be tightened'. Not a 2 because it is not heavily padded; not a 4 because the duplicated description and source block are trimmable.	3 / 5
Actionability	The only 'code' block is `open https://github.com/CloudAI-X/threejs-skills` (a URL, not a shell command) plus 'inspect the upstream README for exact paths' — high-level hints with no specific, executable install steps, matching score-2 'minimal concrete guidance; missing the specific steps to execute'. Not a 3 because there is no executable code or command; not a 1 because it at least points to a concrete location.	2 / 5
Workflow Clarity	A rough sequence is present (advertise in OpenDesign → install upstream bundle → ask agent to invoke by name/trigger), but steps are poorly defined and validation is absent, matching score-2 'rough sequence but many gaps; validation absent'. Not a 3 because the install step is undefined rather than merely lacking checkpoints; not a 1 because some sequence exists.	2 / 5
Progressive Disclosure	No local bundle files exist (references/, scripts/, assets/ absent) and the body points offsite to GitHub rather than to organized local references; section headers give some structure but content is not split across files, matching score-3 'some structure but could be better organized; references not clearly signaled'. Not a 2 because it is not a monolithic wall of inline content; not a 4 because there are no real one-level-deep local references to navigate.	3 / 5
	Total	10 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 clearly conveys the Three.js domain and lists several concrete sub-areas, with a strong set of natural trigger phrases in the frontmatter. Its main weakness is the absence of an explicit 'Use when...' clause, which limits the completeness score.

Suggestions

Add an explicit 'Use when...' clause naming the trigger scenarios (e.g., 'Use when building 3D web scenes, WebGL visualizations, or interactive browser experiences').

Reframe the sub-area list as concrete actions (e.g., 'build scenes, configure materials, wire up controls, apply post-processing') to raise specificity.

Include file-extension or format synonyms (e.g., '.glb', '.gltf', 'WebGL') among the trigger terms for fuller coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing': it names the domain and several concrete sub-areas, but these are categories/objects rather than concrete actions, matching the score-3 anchor (domain + 1-2 specifics, not comprehensive actions). Not a 2 because it lists several specifics; not a 4 because no verb-driven actions are enumerated.	3 / 5
Completeness	It clearly states what ('creating 3D elements and interactive experiences in the browser — scenes, materials, controls, and post-processing') but has no explicit 'Use when...' clause, which per the guidelines caps completeness at 3. Not a 4 because the 'when' is missing rather than merely weak; not a 2 because the 'what' is clear, not vague.	3 / 5
Trigger Term Quality	The frontmatter triggers list 'threejs', 'three.js', '3d web', 'webgl scene', '3d interactive' — natural phrases a user would say with synonyms (three.js/threejs) and common variants; matches the score-4 'good coverage, a few natural terms missing'. Not a 5 because file-extension-style or broader synonyms are absent; not a 3 because coverage is clearly above 'some relevant keywords'.	4 / 5
Distinctiveness Conflict Risk	'Three.js', 'webgl scene', and '3d web' carve a clear niche with distinct triggers and low overlap risk with other skills, matching score-4 'mostly distinct; minor overlap'. Not a 5 because '3d interactive'/'3d web' could brush against general web/UI skills; not a 3 because the Three.js/WebGL framing is clearly specific.	4 / 5
	Total	14 / 20 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: d4138ea

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.