CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threejs-interaction

Three.js interaction - raycasting, controls, mouse/touch input, object selection. Use when handling user input, implementing click detection, adding camera controls, or creating interactive 3D experiences.

Quality

80%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/threejs-interaction/SKILL.md

The canonical home for this skill is threejs-interaction in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable cookbook of executable Three.js interaction patterns with essentially no filler, held back from excellent by three things: ~660 lines monolithically inlined where a reference file split would fit, a few near-duplicate mouse-conversion snippets, and one broken example (PointerLockControls const reassignment) plus a stub dispose() method. Splitting the controls catalog into references/ and fixing the small code defects would lift the skill substantially.

Suggestions

Split the per-control catalog (FlyControls, FirstPersonControls, TrackballControls, MapControls, TransformControls, DragControls) into a references/controls.md and keep SKILL.md to the Quick Start, raycasting, selection, and coordinate-conversion core, per the progressive-disclosure gap.

Fix the PointerLockControls example: declare `let moveForward/moveBackward` instead of `const` so the keydown handler works as written, and implement or drop the `// Remove event listeners` stub in InteractionManager.dispose().

Deduplicate the mouse NDC-conversion snippet (repeated in Quick Start, Touch Support, Click to Select, Hover, and InteractionManager) into one canonical helper and reference it from the usage examples.

DimensionReasoningScore

Conciseness

The body is pure code with terse, useful comments and zero prose padding — it never explains concepts Claude already knows, and each API detail (e.g., the intersects-object field list, near/far/params options) is information Claude cannot reliably recall. It falls short of anchor 5 only because the mouse NDC-conversion snippet is repeated nearly verbatim across five-plus sections (Quick Start, Touch Support, Click to Select, Hover, InteractionManager), where one shared helper would be leaner. It is above anchor 3 because the tightening needed is minor and the duplication arguably keeps each example self-contained.

4 / 5

Actionability

Nearly every section is copy-paste-ready executable code covering the common cases (click, hover, touch, keyboard, box selection, coordinate conversion, all major controls). It misses anchor 5 on a few concrete gaps: the PointerLockControls example declares `const moveForward = false` and then reassigns it in the keydown handler (a runtime TypeError as written), InteractionManager.dispose() is a placeholder comment ("// Remove event listeners"), and the intersects comment cites the removed `Face3` type. These are minor relative to ~20 solid examples, matching anchor 4 (mostly executable, minor gaps).

4 / 5

Workflow Clarity

This is a cookbook-style reference, not a multi-step pipeline: the Quick Start leads with a minimal working click-detection setup, then sections address one task each unambiguously, and useful cross-concern guidance is included (disabling OrbitControls during TransformControls drags and DragControls drags). No validation checkpoints are required since nothing here is destructive or batch-oriented, so the workflow-clarity cap does not apply. It stays at anchor 4 rather than 5 because there is no guidance on choosing between similar controls (e.g., MapControls vs OrbitControls vs TrackballControls) or on wiring the pieces into a full interaction loop.

4 / 5

Progressive Disclosure

The body is ~660 lines entirely inlined in SKILL.md with no references/, scripts/, or assets/ bundle, yet it catalogs eight different control classes plus a selection subsystem — content that clearly belongs in one-level-deep reference files (e.g., references/controls.md), which is exactly anchor 3 (some structure, content that should be separate is inline). It is above anchor 2 because section headers are consistent and navigable, and a 'See Also' section points to sibling skills, but it cannot reach anchor 4 without splitting the per-control API detail out of SKILL.md so the overview stays lean.

3 / 5

Total

15

/

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 that clearly states what the skill does and gives an explicit, multi-trigger 'Use when' clause in third person, closely matching the rubric's good examples. The only weaknesses are minor: the capability list leans on topic nouns, and a few natural trigger terms (hover, drag, picking) are missing.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — "raycasting, controls, mouse/touch input, object selection" plus "implementing click detection, adding camera controls" — which is comparable in coverage to anchor-5 examples, but the first clause names topics as nouns rather than actions, leaving minor gaps (e.g., drag/hover interactions covered by the skill body are not named). It is above anchor 3 because more than 1-2 concrete capabilities are enumerated, but not a clean 5 since "controls" and "interactive 3D experiences" are generic compared to a fully enumerated action list.

4 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: the what ("raycasting, controls, mouse/touch input, object selection") and an explicit "Use when handling user input, implementing click detection, adding camera controls, or creating interactive 3D experiences". This matches the anchor-5 example structure (what + explicit 'Use when...' with multiple concrete triggers); anchor 4 would require the 'when' to be less explicit or specific, which it is not.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "user input", "click detection", "camera controls", "mouse/touch input", "interactive 3D". It sits at anchor 4 ("good keyword coverage; a few natural terms missing") because common variations users actually say — "hover", "drag", "pick/picking", "OrbitControls" — are absent, while the included terms are natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

The Three.js interaction niche (input, raycasting, selection, controls) is clearly distinct from sibling skills the body itself names (threejs-fundamentals, threejs-animation, threejs-shaders). Anchor 5 requires minimal conflict risk; "creating interactive 3D experiences" and "handling user input" are broad enough to occasionally overlap with adjacent three.js or general frontend skills, placing it at anchor 4 (mostly distinct, minor overlap risk with closely related skills).

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 (675 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

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/threejs-interaction/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.