CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threejs-materials

Three.js materials - PBR, basic, phong, shader materials, material properties. Use when styling meshes, working with textures, creating custom shaders, or optimizing material performance.

Quality

75%

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/skills/threejs-materials/SKILL.md

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

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.

The body is a well-organized, genuinely useful materials reference with executable-leaning examples and valuable real-world gotchas. Its main weaknesses are its monolithic inline structure (no reference files despite ~550 lines of API detail), significant overlap with knowledge Claude already has, and boilerplate filler sections.

Suggestions

Move the exhaustive per-material property catalogs (especially MeshPhysicalMaterial, MeshStandardMaterial, and the shader material sections) into references/ files (e.g., references/pbr.md, references/shaders.md), keeping only the selection table, Quick Start, and gotchas in SKILL.md.

Delete the boilerplate 'When to Use' section ('Use this skill when tackling tasks related to its primary domain or functionality as described above') and the redundant 'Common Material Properties' block that repeats properties already shown per-material.

Add a brief explicit material-selection workflow (e.g., 1. pick candidate from the overview table by use case, 2. apply the performance hierarchy, 3. check the gotchas list) so users get a guided path rather than only an implicit one.

DimensionReasoningScore

Conciseness

The code-with-inline-comments style is dense and avoids prose padding, but the ~550-line body largely restates the well-documented three.js materials API that Claude already knows, the 'Common Material Properties' section repeats properties shown in earlier examples, and the closing 'When to Use' section ('Use this skill when tackling tasks related to its primary domain or functionality as described above') is pure boilerplate. It could be tightened or trimmed substantially.

3 / 5

Actionability

Concrete, near-executable snippets cover the common cases (Quick Start, glass, car paint) and surface real gotchas — aoMap requiring uv2, computeLineDistances() for dashed lines, when needsUpdate is required, linewidth >1 only working on some systems, alphaTest vs transparency. It falls short of 5 because many snippets reference undefined variables (texture, geometry, envTexture, camera) and so are not fully copy-paste ready.

4 / 5

Workflow Clarity

As a reference catalog there is no multi-step process to sequence, and the opening material-selection table plus the 'Basic > Lambert > Phong > Standard > Physical' performance ordering provide implicit guidance for choosing a material. However, there is no explicit decision path (e.g., 'pick from the table, then apply the performance rules'), so the guidance remains implicit rather than clearly sequenced.

3 / 5

Progressive Disclosure

Section headers, an overview table, and a Quick Start give the body reasonable structure, but the entire per-material API catalog (e.g., the full MeshPhysicalMaterial property listing, ShaderMaterial examples) is inlined in SKILL.md with no bundle files at all — content that clearly belongs in separate reference files. The 'See Also' section also points to sibling skills ('threejs-textures', 'threejs-shaders', 'threejs-lighting') that are not part of this bundle.

3 / 5

Total

13

/

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: it clearly scopes the Three.js materials domain, uses third person, and pairs a specific capability list with an explicit, multi-phrase 'Use when' trigger clause. The only weakness is mild overlap between its texture/shader triggers and closely related sibling skills.

DimensionReasoningScore

Specificity

The description names the domain ('Three.js materials') and lists several specific capabilities ('PBR, basic, phong, shader materials, material properties'), giving broad coverage. It falls short of a 5 because it enumerates topics rather than concrete actions (no verbs like create, configure, or dispose), but exceeds a 3 since it goes well beyond 1-2 items.

4 / 5

Completeness

It explicitly answers both questions: the 'what' ('Three.js materials - PBR, basic, phong, shader materials, material properties') and the 'when' via a concrete 'Use when styling meshes, working with textures, creating custom shaders, or optimizing material performance' clause with specific trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural phrases users would say: 'styling meshes', 'working with textures', 'creating custom shaders', 'optimizing material performance', plus 'PBR'. A few natural synonyms are missing (e.g., 'reflective', 'glass', 'metallic', 'shiny surfaces'), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Three.js material system specifically), so it will not trigger for unrelated skills. However, 'working with textures' and 'creating custom shaders' overlap directly with closely related sibling skills the body itself cites ('threejs-textures', 'threejs-shaders'), matching the 'minor overlap risk' 4 anchor rather than 5.

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 (549 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/skills/threejs-materials/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.