CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shader-programming-glsl

Expert guide for writing efficient GLSL shaders (Vertex/Fragment) for web and game engines, covering syntax, uniforms, and common effects.

Quality

73%

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/shader-programming-glsl/SKILL.md

The canonical home for this skill is shader-programming-glsl in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 compact, code-first reference with executable examples, sensible best practices, and a useful troubleshooting loop. Its main weaknesses are brief re-teaching of basic GLSL concepts, a Shadertoy-specific example presented without context, and no use of progressive disclosure to keep the core file lean.

Suggestions

Trim explanations of GLSL basics Claude already knows (what vertex/fragment shaders do, uniform/varying definitions, swizzling mechanics) and keep only non-obvious guidance.

Flag the raymarching example as Shadertoy-specific, or provide a standard GLSL ES entry point (uniform declarations for iResolution and a main()) so the code is copy-paste runnable in WebGL.

Move the raymarching example and additional effect recipes (blur, bloom, color correction) into a references/ file with clearly signaled links to keep SKILL.md an overview.

DimensionReasoningScore

Conciseness

The body is dominated by executable code with brief sections, but it does spend a few lines on concepts Claude already knows ('Vertex Shader: Transforms 3D coordinates to 2D screen space', the uniform/varying definitions, and basic swizzling examples). Not a 5 because these textbook explanations could be trimmed; not a 3 because the padding is minor relative to the whole.

4 / 5

Actionability

Provides mostly executable, concrete GLSL (basic vertex/fragment shaders, UV varying passing, a complete SDF raymarching example, and do/don't best practices). Not a 5 because the raymarching example uses Shadertoy-only conventions ('mainImage', 'iResolution') without noting it won't compile in standard WebGL, and the varying example is fragmentary (missing the 'attribute vec3 position' / 'uv' declarations).

4 / 5

Workflow Clarity

Sections are logically sequenced (structure, uniforms/varyings, vector math, worked example, best practices, troubleshooting) and the Troubleshooting section provides a recovery loop for the most common failure (black screen -> check gl_Position.w, uniform values, UV range). Not a 5 because there are no general validation checkpoints for verifying a shader compiles/renders beyond that single troubleshooting entry; not a 3 because no destructive or batch operations are involved and the guidance is easy to follow.

4 / 5

Progressive Disclosure

The single SKILL.md is well-sectioned with clear headers and no nested references (no bundle files exist, and the body references none). Not a 5 because the skill exceeds 50 lines and content like the full raymarching example could be split into a reference file with clearly signaled links.

4 / 5

Total

16

/

20

Passed

Description

61%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 focused, technically credible description that clearly identifies the GLSL shader niche with good natural keywords, but it entirely lacks a 'when to use' trigger clause, capping its completeness and practical discoverability.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing or debugging shaders in WebGL, Three.js, or game engines, or when the user mentions GLSL, vertex/fragment shaders, or .frag/.vert files.'

Convert topic mentions into concrete actions (e.g. 'Write and optimize vertex/fragment shaders, pass data via uniforms and varyings, and implement effects like blur, bloom, and raymarching') to lift specificity.

Add synonyms and file extensions (WebGL, Three.js, .frag, .vert, .glsl) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('writing efficient GLSL shaders (Vertex/Fragment)') and covers 'syntax, uniforms, and common effects', but these are topic mentions rather than a list of several specific actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because it doesn't enumerate multiple distinct concrete actions like the 'extracts text, fills forms, converts pages' example.

3 / 5

Completeness

It clearly answers 'what' ('writing efficient GLSL shaders... covering syntax, uniforms, and common effects') but contains no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say: 'GLSL', 'shaders', 'Vertex/Fragment', 'uniforms', 'effects', and 'web and game engines'. Not a 5 because common variations and extensions like 'WebGL', 'Three.js', or '.frag/.vert' files are absent.

4 / 5

Distinctiveness Conflict Risk

'GLSL shaders (Vertex/Fragment)' defines a clear niche with distinct triggers. Not a 5 because the broad phrase 'for web and game engines' leaves minor overlap risk with general graphics or game-engine skills.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/shader-programming-glsl/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.