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

83%

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-materials in CloudAI-X/threejs-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable and easy to navigate per-section, with complete executable code throughout. Its weaknesses are token efficiency (restating well-known Three.js property APIs inline) and the absence of any progressive disclosure — everything lives in one long SKILL.md with no reference files.

Suggestions

Move the exhaustive MeshPhysicalMaterial property listing and the Common Material Properties block into a references/ file (e.g., references/physical-material.md), keeping SKILL.md to the overview table, quick start, and one concise example per material type.

Remove sections that restate knowledge Claude already has, such as "Built-in Uniforms (auto-provided)" for ShaderMaterial, and keep only the non-obvious notes (e.g., the aoMap uv2 requirement, computeLineDistances for dashed lines).

Convert the inlined bulk listings into well-signaled one-level-deep references (e.g., "**Physical material properties**: See [PHYSICAL.md](references/physical.md)"), matching the See Also pointers to sibling skills.

DimensionReasoningScore

Conciseness

The body is code-dense with almost no padded prose, but sections like "Common Material Properties" and "Built-in Uniforms (auto-provided)", plus the exhaustive MeshPhysicalMaterial property dump, restate well-known Three.js API knowledge Claude already has; the ~520-line file could be tightened considerably.

3 / 5

Actionability

Every material type has complete, copy-paste-ready instantiation code with inline comments, plus concrete recipes (glass, car paint, gradient map, dashed lines, material pooling) that cover the common cases.

5 / 5

Workflow Clarity

This is a single-action reference skill rather than a multi-step workflow: the material-types table unambiguously guides selection and each section shows the full instantiation step, and there are no destructive or batch operations that would require validation checkpoints.

5 / 5

Progressive Disclosure

Internal structure is good (quick start, clear headers, overview table), but there are no bundle files at all — the ~250 lines of exhaustive property listings belong in reference files (e.g., a physical-material properties reference), leaving SKILL.md as a monolithic lookup page.

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 description that names the domain concretely, lists the main material types, and includes an explicit multi-condition 'Use when' clause. Its main weakness is overlap on the texture and shader triggers with sibling skills in the same family.

DimensionReasoningScore

Specificity

"PBR, basic, phong, shader materials, material properties" enumerates several concrete material types, but capabilities are framed as domain nouns rather than actions (verbs like create/configure appear only in the when-clause), leaving minor coverage gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

The description clearly states what ("Three.js materials - PBR, basic, phong, shader materials, material properties") and explicitly answers when with four concrete trigger conditions ("Use when styling meshes, working with textures, creating custom shaders, or optimizing material performance"), matching the both-what-and-when 5 anchor.

5 / 5

Trigger Term Quality

"styling meshes", "working with textures", "creating custom shaders", "optimizing material performance" plus "PBR" and "phong" are natural trigger phrases, but common variations users might say (e.g., "texture mapping", "material setup", "three.js material") are missing.

4 / 5

Distinctiveness Conflict Risk

The Three.js materials niche is clear with distinct triggers, but "working with textures" and "creating custom shaders" directly overlap with the sibling threejs-textures and threejs-shaders skills referenced in See Also, giving minor conflict risk with closely related skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (521 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

calesthio/OpenMontage

Path

.agents/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.