threejs-skills

Create 3D scenes, interactive experiences, and visual effects using Three.js. Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

46%Scale 1-5

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

This skill provides comprehensive, executable Three.js guidance with good code examples, but suffers from significant verbosity and poor content organization. It explains many concepts Claude already knows, repeats patterns multiple times, and inlines ~450+ lines of content that should be split across multiple files. The workflow lacks validation checkpoints despite WebGL rendering being prone to silent failures.

Suggestions

Reduce content by 50%+: remove explanatory comments like '// Scene - contains all 3D objects', eliminate the 'When to Use' section, remove geometry/material description lists (Claude knows what a sphere is), and deduplicate repeated animation loop examples.

Split into bundle files: move Advanced Techniques (shadows, env maps, fog), Modern Practices (WebGPU, Timer, GSAP), and Production Patterns (LOD, instancing, loading) into separate referenced files, keeping SKILL.md as a concise overview with the core setup pattern.

Add validation checkpoints to the workflow: after scene setup, include a 'verify render works with a basic colored cube before adding complexity' step, and integrate troubleshooting checks (black screen, missing objects) as inline validation rather than a separate section.

Remove the 'Recommended Production Stack' ASCII tree and 'When to Use What' section — these are architectural decisions Claude can make contextually without being told.

Dimension	Reasoning	Score
Conciseness	The skill is significantly verbose at ~450+ lines. It explains concepts Claude already knows (what a scene is, what a camera does, what each geometry type is for), includes redundant patterns (animation loop shown 3+ times, mouse tracking shown multiple times), and has sections like 'When to Use' that list obvious triggers. The comments like '// Scene - contains all 3D objects' and '// Camera - defines viewing perspective' are unnecessary for Claude.	2 / 5
Actionability	The skill provides extensive executable code examples that are copy-paste ready, covering scene setup, materials, lighting, raycasting, particles, shadows, post-processing, and more. Minor gaps exist (e.g., the custom camera controls example has a naive rotation implementation that won't produce good orbit behavior), but overall the guidance is concrete and executable.	4 / 5
Workflow Clarity	The 'Systematic Development Process' and 'Example Workflow' sections provide a reasonable sequence of steps, but there are no validation checkpoints or error recovery loops. For a skill involving WebGL rendering where black screens and invisible objects are common failure modes, the troubleshooting section is separate from the workflow rather than integrated as validation steps. No 'verify at this step' guidance is provided.	3 / 5
Progressive Disclosure	The content is a monolithic wall of text with no bundle files to offload detail into. Advanced techniques (shadows, environment maps, post-processing, WebGPU, GSAP, scroll interactions, LOD, instanced meshes, production stacks) are all inlined rather than split into separate reference files. References to 'threejs-postprocessing' and 'threejs-shaders' skills are mentioned but no actual bundle files exist. The skill would benefit enormously from splitting into core setup + advanced references.	2 / 5
	Total	11 / 20 Passed

Description

82%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.

This is a solid skill description that clearly communicates both purpose and trigger conditions. Its main weakness is that the capability descriptions are somewhat high-level ('3D scenes, interactive experiences, visual effects') rather than listing more granular concrete actions. The trigger terms are good but could include a few more natural variations.

Suggestions

Add more specific concrete actions such as 'build particle systems, create camera animations, render 3D models, add lighting and shadows, implement orbit controls' to improve specificity.

Include additional trigger term variations like 'threejs', '3D models', 'mesh', 'scene rendering', or 'WebGL shaders' to capture more natural user phrasings.

Dimension	Reasoning	Score
Specificity	Names the domain (Three.js/3D) and lists a few actions ('Create 3D scenes, interactive experiences, and visual effects'), but these are somewhat broad categories rather than highly specific concrete actions like 'build particle systems, create camera controls, render geometries'.	3 / 5
Completeness	Clearly answers both 'what' ('Create 3D scenes, interactive experiences, and visual effects using Three.js') and 'when' ('Use when user requests 3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements') with explicit trigger phrases.	5 / 5
Trigger Term Quality	Includes good natural keywords: '3D graphics', 'WebGL', '3D visualizations', 'animations', 'interactive 3D elements', 'Three.js'. Missing some variations like 'threejs', '.js 3D library', 'WebGL renderer', '3D models', 'mesh', or 'scene graph' that users might naturally say.	4 / 5
Distinctiveness Conflict Risk	Three.js and 3D/WebGL are a clear niche with distinct triggers. Unlikely to conflict with other skills unless there are competing 3D libraries, and the explicit mention of 'Three.js' and 'WebGL' makes it highly distinguishable.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (716 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/threejs-skills/SKILL.md
Commit: 0159794

Reviewed: about 10 hours 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.