CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threejs-shaders

Three.js shaders - GLSL, ShaderMaterial, uniforms, custom effects. Use when creating custom visual effects, modifying vertices, writing fragment shaders, or extending built-in materials.

Quality

78%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, code-dense reference whose Three.js-specific content (built-in uniforms, onBeforeCompile injection points, uniform update patterns, TSL) is genuinely valuable. Its weaknesses are structural: standard GLSL reference material that Claude already knows is inlined, and the single large file with no bundle split or explicit workflow makes it heavier on the context window than it needs to be.

Suggestions

Move the 'GLSL Built-in Functions' section (and optionally the basic Gradient/Noise snippets) into a references/ file or delete them — they restate GLSL spec knowledge Claude already has and cost ~80 lines of context.

Split the body into a lean SKILL.md (Quick Start, ShaderMaterial vs RawShaderMaterial, uniform update patterns, debugging) plus a references/patterns.md for the full effect cookbook (fresnel, rim, dissolve, instancing, TSL), one level deep and clearly signaled.

Add a short explicit workflow (create material → wire uniforms → update in animation loop → check compiler errors via renderer.debug / console output of shader sources) so the Debugging section becomes an explicit checkpoint rather than an isolated tip.

DimensionReasoningScore

Conciseness

The Three.js-specific sections (built-in uniforms/attributes, onBeforeCompile injection points, uniform update patterns, TSL comparison) are dense and valuable, but the 'GLSL Built-in Functions' section (~55 lines of standard spec functions like abs, sin, mix, clamp) and the trivial 'Gradient' patterns restate what Claude already knows. Mostly efficient with a clearly cuttable block of padding — anchor 3, not 2 because the majority of the file is non-obvious, code-dense material.

3 / 5

Actionability

Nearly every JavaScript example is complete and copy-paste ready (Quick Start, texture sampling, vertex displacement, fresnel, rim lighting, instancing, onBeforeCompile with its animation-loop update, TSL quick start), covering the common cases. The few GLSL fragments (noise, gradient, dissolve) are shader chunks — the natural reusable unit — with full boilerplate shown elsewhere, so this matches the top anchor rather than 4.

5 / 5

Workflow Clarity

Well-organized as a reference (basics → patterns → extending materials → debugging), and the Debugging section covers compile-error checking and visual debugging, but there is no explicit end-to-end sequence or validation checkpoints for assembling a shader; the reader must synthesize their own process. Anchor 3 — sections are coherent and navigable (above 2) but lack an explicit step sequence (below 4).

3 / 5

Progressive Disclosure

No bundle files exist; everything is inlined in a single ~690-line SKILL.md. Section headers are clear, but the inline GLSL function/API reference and the TSL section are exactly the 'content that should be separate is inline' pattern of anchor 3. Not 4: with a file this large, the split opportunities are more than minor organization gaps.

3 / 5

Total

14

/

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 names a clear domain, lists concrete capabilities, and includes an explicit and specific 'Use when...' clause with natural trigger phrases. Minor overlap risk with sibling Three.js material/postprocessing skills and a few missing keyword variations keep it just short of the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions ('creating custom visual effects, modifying vertices, writing fragment shaders, or extending built-in materials') alongside concrete nouns (GLSL, ShaderMaterial, uniforms). Matches anchor 4 ('several specific actions; minor gaps') rather than 5 because 'custom effects' is slightly generic and actions like uniform setup/debugging are unnamed.

4 / 5

Completeness

Explicitly answers both: 'what' ('Three.js shaders - GLSL, ShaderMaterial, uniforms, custom effects') and 'when' with four concrete trigger phrases ('Use when creating custom visual effects, modifying vertices, writing fragment shaders, or extending built-in materials'). Structure parallels the good presentation-skill example; the 'when' clause is explicit and specific, so above anchor 4.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'shaders', 'GLSL', 'fragment shaders', 'ShaderMaterial', 'vertices', 'visual effects'. Not 5 because common variations like 'vertex shader', 'WebGL', 'materials', or '.glsl' are missing.

4 / 5

Distinctiveness Conflict Risk

Most triggers (fragment shaders, GLSL, ShaderMaterial, modifying vertices) are strongly shader-specific, giving a clear niche. Not 5 because 'extending built-in materials' and 'custom visual effects' overlap with closely related sibling skills (threejs-materials, threejs-postprocessing) referenced in the body's See Also.

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 (688 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-claude/skills/threejs-shaders/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.