CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threejs-geometry

Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.

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

Quality

Content

57%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 well-organized, code-dense reference that is highly actionable for common geometry tasks, but it functions as a monolithic inlined API catalog. Splitting bulk reference material into a references/ file, trimming capabilities Claude already knows, and adding one or two explicit task workflows with checkpoints would raise quality across the board.

Suggestions

Move the bulk API catalogs (full built-in geometry parameter listings, Interleaved Buffers, BatchedMesh, Morph Targets) into a references/ file (e.g. references/geometry-api.md) and keep SKILL.md as a lean overview with one exemplar per topic plus clearly signaled one-level-deep pointers.

Trim or cut content that restates what Claude already knows — e.g. '// Normals (required for lighting)', '// UVs (for texturing)', the item-size table, and basic parameter listings for BoxGeometry/PlaneGeometry — keeping only the non-obvious details (parameter orders, version quirks like "depth // Was 'height' in older versions", segment-count guidance).

Add one or two explicit multi-step workflows with checkpoints for the most common tasks — e.g. 'build custom geometry: set position -> set index -> computeVertexNormals -> verify with computeBoundingBox' and 'choose rendering path: <10 meshes use Mesh, identical copies use InstancedMesh, mixed geometries use BatchedMesh' — and make the Quick Start self-contained (define scene/material) so it is copy-paste executable.

DimensionReasoningScore

Conciseness

The body is mostly dense, comment-annotated code with little prose padding, but at ~580 lines it inlines a full API reference — including parameter listings for basic shapes (BoxGeometry, SphereGeometry) and reminders like '// Normals (required for lighting)' and '// UVs (for texturing)' — much of which Claude already knows or could be trimmed into a separate reference file. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, given the volume of content Claude can largely derive itself.

3 / 5

Actionability

Examples are concrete, syntactically executable constructor patterns covering common cases — e.g. the full InstancedMesh loop with 'dummy.updateMatrix(); instancedMesh.setMatrixAt(i, dummy.matrix)' and 'positions.needsUpdate = true'. It falls short of fully copy-paste ready (anchor 5) because many snippets depend on undefined surrounding variables ('scene', 'material', 'count', 'index', 'geo1'), including the Quick Start itself.

4 / 5

Workflow Clarity

Task sections such as 'Modifying BufferGeometry' imply a correct order with implicit checkpoints ('positions.needsUpdate = true', 'Recompute normals after position changes'), but the skill presents no explicit multi-step workflows — e.g. going from a requirement to a chosen geometry to an optimized/instanced mesh — and validation checkpoints are only implicit. This matches 'steps listed but validation gaps; sequence present but checkpoints missing or implicit' rather than 4.

3 / 5

Progressive Disclosure

Sections are clearly headed (Quick Start, Built-in Geometries, BufferGeometry, InstancedMesh, Performance Tips), but the entire ~580-line API reference is inlined in SKILL.md with no references/, scripts/, or assets/ files at all — bulk reference material (e.g. the full built-in geometry parameter catalog, Interleaved Buffers, BatchedMesh) is exactly the content that should live one level deep in a separate file. This matches anchor 3 ('content that should be separate is inline') rather than 4, since no offloading exists at all.

3 / 5

Total

13

/

20

Passed

Description

88%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, with a clear capability list and an explicit 'Use when...' trigger clause. The only improvements are adding a few more natural trigger synonyms and sharpening the boundary against sibling Three.js skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete capability areas — 'built-in shapes, BufferGeometry, custom geometry, instancing' — which comprehensively cover the geometry-creation domain with no vague filler. It matches the top anchor (multiple specific concrete actions, comprehensive coverage) rather than 4, since there are no notable gaps in capability coverage.

5 / 5

Completeness

It explicitly answers both questions: the 'what' is 'Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing' and the 'when' is the explicit trigger clause 'Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering'. Both are concrete, matching the top anchor's structure exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'creating 3D shapes', 'working with vertices', 'building custom meshes', and 'optimizing with instanced rendering' align well with what a user would say. Not 5 because common variations are missing — e.g. 'point cloud', 'low-poly/low poly mesh', 'merge geometries', or '3D model' — while existing terms are solid but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

'Three.js geometry creation' carves a clear niche distinct from materials or shaders, but the trigger 'building custom meshes' has minor overlap risk with closely related sibling skills (the body itself references threejs-fundamentals and threejs-materials). This matches 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict top anchor.

4 / 5

Total

18

/

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 (581 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-geometry/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.