Name: shader-programming-glsl
Rating: 53.6 (1 reviews)
Author: administrakt0r

shader-programming-glsl

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

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

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

The body is a well-structured, mostly executable GLSL guide with good code examples and a clear topical flow, but it spends tokens explaining basic shader concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste code, but it explains basic concepts Claude already knows (vertex/fragment roles, uniform/varying definitions, swizzling) and the Overview restates the description.	3 / 5
Actionability	Provides concrete, executable GLSL examples (basic vertex/fragment shaders, UV/varying passing, a raymarching SDF sphere) covering common cases, with only minor gaps such as Shadertoy-specific conventions.	4 / 5
Workflow Clarity	Has a clear logical flow (structure → uniforms/varyings → math → examples → best practices → troubleshooting) and the 'When to Use' list grounds usage; no destructive/batch operations so missing validation checkpoints is acceptable.	4 / 5
Progressive Disclosure	A single self-contained file (~114 lines) with well-organized sections and no nested references; no bundle files exist, so content is appropriately inline with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

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

The description clearly identifies the domain and is mostly distinct, but it lacks an explicit 'Use when...' trigger clause and misses common synonyms (WebGL, Three.js) that users would naturally say.

Suggestions

Add an explicit trigger clause such as 'Use when writing or debugging GLSL shaders for WebGL, Three.js, or game engines.'

Include common synonyms and tool names users actually say (WebGL, Three.js, ShaderToy, fragment/vertex shaders) to improve trigger coverage.

Replace generic verbs ('covering') with concrete capabilities (e.g., 'write, debug, and optimize vertex/fragment shaders').

Dimension	Reasoning	Score
Specificity	Names the domain ('writing efficient GLSL shaders (Vertex/Fragment)') and a couple of concrete topics ('syntax, uniforms, and common effects'), but the actions are generic ('writing', 'covering') rather than a comprehensive list of capabilities.	3 / 5
Completeness	Has a clear 'what' (an expert guide covering syntax, uniforms, and effects) but no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('GLSL shaders', 'Vertex/Fragment') but omits common variations like 'WebGL', 'Three.js', or 'fragment/vertex shader' that users typically invoke.	3 / 5
Distinctiveness Conflict Risk	'GLSL shaders (Vertex/Fragment) for web and game engines' is a clear, fairly niche trigger with minimal overlap risk against other skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 57c135b

Reviewed: 20 hours ago

Table of Contents

Discovery Implementation Validation

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.