Content
57%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |