Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-organized Three.js materials reference with executable code throughout, but it is a long monolithic single file that re-lists many standard properties and does not split detailed reference material into bundle files.
Suggestions
Move the exhaustive per-material property listings (especially MeshPhysicalMaterial) into a references/ file such as MATERIAL_PROPERTIES.md, keeping SKILL.md as a concise overview + Quick Start that links out for full property detail.
Trim standard base properties (color, transparent, opacity, map) that Claude already knows; retain only non-obvious properties and gotchas (e.g. aoMap requires uv2, linewidth >1 only on some systems, needsUpdate triggers) inline.
Add a short end-to-end example workflow (load texture → set maps → set uv2 for aoMap → assign to mesh) so the typical multi-step task sequence is explicit rather than implied across scattered sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Prose is lean with almost no concept explanation, but the ~515-line body exhaustively lists many standard base properties (color, transparent, opacity, map) Claude already knows, so it is mostly efficient yet could be tightened — score 2 rather than the lean 'every token earns its place' of 3. | 2 / 3 |
Actionability | Every section ships complete, executable, copy-paste-ready material definitions with commented property values and a working Quick Start, matching the score-3 anchor for fully executable examples. | 3 / 3 |
Workflow Clarity | For this reference skill the single action (instantiate a material and assign it to a mesh) is shown unambiguously in Quick Start, sections are well organized, and there are no destructive/batch operations that would require validation checkpoints, so the simple-skill leniency applies and it earns 3. | 3 / 3 |
Progressive Disclosure | No bundle files exist and the entire API reference — including the very long MeshPhysicalMaterial property listing — is inline in SKILL.md, so content that should be split into a reference file is inline; well-organized but not appropriately split, matching the score-2 anchor. | 2 / 3 |
Total | 10 / 12 Passed |