CtrlK
BlogDocsLog inGet started
Tessl Logo

threejs-fundamentals

Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.

73

Quality

90%

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

The canonical home for this skill is threejs-fundamentals in CloudAI-X/threejs-skills

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is highly actionable and token-efficient, dominated by executable code with minimal prose. Its weaknesses are the lack of validation-anchored workflows and a monolithic single-file structure that forgoes progressive disclosure into separate reference files.

Suggestions

Add an explicit validation checkpoint to the cleanup and loader patterns (e.g. assert geometry/material arrays are disposed and verify the renderer is torn down) to lift workflow clarity.

Split the large inline API reference into one-level-deep bundle files (e.g. references/cameras.md, references/math.md) and link them from a concise SKILL.md overview to enable progressive disclosure.

For risky operations such as mergeGeometries or LOD setup, include a brief verify step (e.g. check draw-call count or bounding boxes) so the performance patterns read as validated workflows.

DimensionReasoningScore

Conciseness

The body is almost entirely lean code blocks plus terse one-line descriptions (e.g. "Container for all 3D objects, lights, and cameras."), with no padded explanation of concepts Claude already knows.

3 / 3

Actionability

It provides copy-paste-ready, executable examples throughout (camera setup, renderer config, Object3D transforms, math utilities, cleanup), with specific property names and arguments.

3 / 3

Workflow Clarity

It is organized into clear sections, but there are no multi-step workflows with explicit validation checkpoints or feedback loops; patterns like "Proper Cleanup" are presented as standalone snippets rather than sequenced, validated processes.

2 / 3

Progressive Disclosure

Everything lives inline in one ~480-line file with no bundle files; the broad API reference (cameras, math utilities, patterns) is content that could be split into one-level-deep reference files, matching the "content that should be separate is inline" anchor.

2 / 3

Total

10

/

12

Passed

Description

100%

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 third-person, specific, and complete with an explicit trigger clause, covering a well-scoped niche with low conflict risk. It hits the top anchor on all four dimensions.

DimensionReasoningScore

Specificity

"Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems" names multiple distinct, concrete capabilities, matching the anchor for listing several specific actions.

3 / 3

Completeness

It states what the skill covers and follows with an explicit "Use when ..." trigger clause, clearly answering both what and when.

3 / 3

Trigger Term Quality

"setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms" are natural phrases a user would say, with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Three.js fundamentals niche (scene/camera/renderer/transforms) is distinct from the sibling skills it lists (geometry, materials, lighting) and unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
calesthio/OpenMontage
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.