Content
78%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 strong, highly actionable material catalog with executable examples throughout and good selection guidance. Its weakness is progressive disclosure: a large inlined API reference that would benefit from being split into reference files.
Suggestions
Move the exhaustive per-material property listings (especially MeshPhysicalMaterial's clearcoat/transmission/sheen/iridescence/anisotropy keys and the built-in uniforms reference) into a references/ file, keeping SKILL.md to a quick-start, the comparison table, and one compact example per material.
Add a short 'choose then verify' note (e.g. render a test frame and confirm the material looks correct under scene lighting) to give the configuration workflow an explicit checkpoint.
Trim minor editorial padding like 'Recommended for realistic results' and 'Full control - no built-in uniforms/attributes' so every line adds information Claude doesn't already have.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean — code blocks with terse inline comments and brief one-line intros like 'No lighting calculations. Fast, always visible.' — with only minor padding ('Recommended for realistic results', 'Full control - no built-in uniforms/attributes') that could be trimmed. | 4 / 5 |
Actionability | Every material type ships a complete, copy-paste-ready constructor example with its properties, plus targeted worked examples (glass, car paint) and a built-in-uniforms reference, covering the common cases fully. | 5 / 5 |
Workflow Clarity | A comparison table and Quick Start make material selection unambiguous and the Performance Tips give ordered guidance; as a non-destructive reference skill it avoids the destructive-cap, but lacks any explicit verify-the-render feedback loop. | 4 / 5 |
Progressive Disclosure | Section structure is clear and navigable, but the ~540-line body inlines a full per-material property API reference (e.g. MeshPhysicalMaterial's clearcoat/transmission/sheen keys, built-in uniforms) that belongs in reference files, and no bundle files exist to absorb it. | 3 / 5 |
Total | 16 / 20 Passed |