CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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 ./skills/threejs-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable and well-structured content with excellent version-specific guidance and complete code, but it suffers from significant duplication (the animation loop and import patterns are repeated multiple times), explanations of basics Claude already knows, and a monolithic single-file layout that should offload advanced material to reference files. The description-quality frontmatter is strong, but the body needs consolidation to respect the context window.

Suggestions

Deduplicate the animation-loop and import examples: the same pattern appears in Core Setup, Common Patterns (Rotating Object), the raycasting hover example, the mouse-interaction example, and again in Modern Three.js Practices — keep one canonical version and reference it instead of repeating it.

Move the advanced material (Advanced Techniques, Modern Three.js Practices: GSAP, scroll interactions, LOD/instancing, WebGPU, production stack) into separate reference files such as references/advanced.md and references/modern-practices.md, linked from a short overview section, so the main SKILL.md stays lean.

Add an explicit verification checkpoint in the Systematic Development Process or Example Workflow (e.g., "confirm the scene renders and check the browser console for errors before delivering") so error recovery is part of the workflow rather than only a reactive Troubleshooting section.

Trim teaching comments that explain concepts Claude already knows (what ambient/directional light is, per-material type descriptions, "Renderer - draws the scene") and keep only version-specific and non-obvious guidance.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with several duplicated and padded sections: the animation-loop pattern appears five times (Core Setup, Rotating Object, raycast hover, mouse interaction, scroll-based), the ES-module import block is repeated verbatim in "Modular Imports", and a Summary section restates the systematic process. It also explains basics Claude already knows ("// Ambient light - general illumination", "Directional light - like sunlight", per-material type descriptions). Not 1 because the version-specific guidance (Timer vs Clock, outputColorSpace rename, setAnimationLoop, r183 WebGPU) is genuinely non-obvious and earns its tokens.

2 / 5

Actionability

Guidance is fully executable and copy-paste ready: a complete import-map setup block, scene/camera/renderer initialization, resize handler, OrbitControls with damping, raycasting for selection and hover, particle systems, shadows, and tone mapping. The common cases (rotating object, orbit controls, interaction, performance) are each covered with complete runnable code; only trivial placeholders like "texture-url.jpg" remain, which is expected for pattern documentation.

5 / 5

Workflow Clarity

The "Systematic Development Process" sequences steps 1-5 (define scene, build geometry, apply materials, add lighting, handle responsiveness) and the "Example Workflow" walks a concrete request end-to-end to "Result: Smooth, interactive 3D sphere ✓". Not 5 because verification is reactive (a separate Troubleshooting section) rather than an explicit checkpoint inside the workflow itself; well above 3 because both sequence and error-recovery guidance are present and clear.

4 / 5

Progressive Disclosure

The file has clear section headers and reasonable internal organization, so it is above the minimal-structure anchor, but it is a monolithic ~715-line SKILL.md with no bundle files at all. Roughly 180 lines of advanced material ("Advanced Techniques", "Modern Three.js Practices", GSAP, scroll interactions, LOD/instancing, production stack) belong in separate reference files; the only pointers are to sibling skills ("threejs-postprocessing", "threejs-shaders"), not to any actual bundle files.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description: third-person, concise, concrete about both capabilities and triggers. The only gaps are a few missing natural trigger synonyms (notably "Three.js" and "3D model") and slight overlap risk from the broad words "animations" and "visual effects".

DimensionReasoningScore

Specificity

"Create 3D scenes, interactive experiences, and visual effects using Three.js" names the domain and three concrete actions, matching the anchor for several specific actions with minor gaps in coverage. It is not 5 because the what-clause omits capabilities like animations, textures, and optimization, and well above 3 because it lists more than 1-2 actions.

4 / 5

Completeness

It explicitly answers both parts: 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 concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Trigger phrases "3D graphics, WebGL experiences, 3D visualizations, animations, or interactive 3D elements" are natural terms users would say, giving good coverage. Not 5 because common synonyms are missing: "Three.js" itself, "3D model", and "rendering" never appear as triggers.

4 / 5

Distinctiveness Conflict Risk

The Three.js/WebGL 3D rendering niche is clearly distinct from most skills, but the trigger words "animations" and "visual effects" could also naturally fire for 2D animation, video, or motion-graphics skills, creating minor overlap risk. It is far more specific than the generic overlap anchors at 1-3.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/threejs-skills/SKILL.md

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.