CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

81%

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-geometry in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, code-dense Three.js geometry reference that assumes Claude's competence and avoids conceptual padding. Its main weakness is progressive disclosure: a large reference surface is delivered as a single monolithic file rather than split into well-signaled, one-level-deep reference files.

Suggestions

Move the exhaustive built-in geometry and BufferGeometry API listings into a references/ file (e.g., references/builtins.md, references/buffergeometry.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

Collect version-sensitive notes (BatchedMesh r183, the TextGeometry 'depth' vs older 'height' rename) into a single 'Version notes / Deprecated' section rather than scattering them inline.

Add a short validation/checklist step for the runtime-mutation workflows (e.g., after setAttribute changes: set needsUpdate, computeVertexNormals, computeBoundingBox) to make the implicit feedback loop explicit.

DimensionReasoningScore

Conciseness

The body is dense, mostly executable code with minimal prose and no padding about concepts Claude already knows ('The base class for all geometries. Stores data as typed arrays for GPU efficiency.'); not 5 because of some redundant variant examples and inline time-sensitive notes ('BatchedMesh (r183)', 'Was height in older versions') that would be cleaner in a deprecated/versioned section.

4 / 5

Actionability

Extensive copy-paste-ready JavaScript covering built-in geometries, custom BufferGeometry, points, lines, InstancedMesh, BatchedMesh, and utilities, with parameter lists inline, matching the fully-executable top anchor; not below 5 because common cases are concretely covered.

5 / 5

Workflow Clarity

Content is clearly organized by topic and implicit workflows (e.g., load font -> create TextGeometry -> center -> add to scene) are sequenced in code; not 5 because there are no explicit validation/checkpoint steps, though geometry creation is not a destructive or batch operation requiring the rubric's validation cap.

4 / 5

Progressive Disclosure

The file is well-sectioned with clear headers, but ~570 lines of API reference are entirely inline with no bundle files (references/scripts/assets absent) and no one-level-deep reference links, matching 'content that should be separate is inline'; not 4 because the absence of any external file split is more than a minor organization gap for a reference of this size.

3 / 5

Total

16

/

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, third-person description that clearly states what the skill does and gives an explicit, multi-trigger 'Use when...' clause. Minor gains are possible by converting capability categories into concrete actions and adding a few more natural synonyms.

DimensionReasoningScore

Specificity

Names the domain ('Three.js geometry creation') and lists several specific capability areas ('built-in shapes, BufferGeometry, custom geometry, instancing'), matching the 'lists several specific actions; minor gaps' anchor; not 5 because these are category nouns rather than fully concrete verb-actions and coverage omits items present in the body (points, lines, utilities).

4 / 5

Completeness

Explicitly answers both 'what' (geometry creation with the listed capability areas) and 'when' via a concrete 'Use when...' clause with multiple trigger phrases, matching the top anchor exactly; not below 5 because neither component is vague or missing.

5 / 5

Trigger Term Quality

Natural user phrases appear ('creating 3D shapes, working with vertices, building custom meshes, optimizing with instanced rendering'), giving good keyword coverage; not 5 because common synonyms/variations (e.g., 'mesh', 'geometry', 'point cloud') are not comprehensively enumerated.

4 / 5

Distinctiveness Conflict Risk

The 'Three.js geometry creation' niche is clearly distinct with specific triggers; not 5 because 'vertices' and 'custom meshes' create minor overlap risk with sibling skills (threejs-shaders 'Custom vertex manipulation', threejs-materials) noted in See Also.

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