shader-dev

Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.

Quality

80%

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 ./skills/shader-dev/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete executable GLSL/WebGL2 code and a clear sequenced workflow plus self-check loops. Its weaknesses are redundancy from listing techniques twice and progressive disclosure gaps — the referenced bundle files are missing and the index is inline.

Suggestions

Create the referenced techniques/ and reference/ files (or remove the structure tree and routing-table links) so the signaled navigation actually resolves — currently none of the bundle files exist on disk.

Eliminate the dual technique listing: keep the routing table for intent→technique routing and move the per-technique descriptions into the technique files instead of repeating all 36 inline in the index.

Drop marketing fluff and de-duplicate the two 'Common Pitfalls' sections by merging them into a single, clearly grouped checklist.

Dimension	Reasoning	Score
Conciseness	Mostly efficient concrete content, but the 36 techniques are listed twice (routing table then technique index) and the inline index re-describes entries that belong in the technique files, so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance: WRONG/CORRECT GLSL blocks for gl_FragCoord, main() wrapper, function order, macro limits, JS TDZ ordering, and a debugging code table.	3 / 3
Workflow Clarity	The 'How to Use' section gives a clear 4-step sequence (routing table → technique file → reference link → WebGL2 rules) and is reinforced by self-check and debugging sections that act as feedback loops.	3 / 3
Progressive Disclosure	The overview design is sound with one-level-deep signaled references, but the referenced technique/ and reference/ bundle files do not exist on disk, breaking actual navigation, and substantial content (the technique index) is inline rather than split out.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

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 is specific and distinctive, naming many concrete shader techniques with natural trigger terms, but it omits any explicit 'when to use' guidance, capping completeness at 2. Mild buzzword fluff ('Comprehensive', 'stunning') is present.

Dimension	Reasoning	Score
Specificity	Quotes 'ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing' — a list of multiple specific concrete techniques matching the score-3 anchor, though 'Comprehensive' and 'stunning visual effects' add mild marketing fluff.	3 / 3
Completeness	It clearly states what ('Comprehensive GLSL shader techniques for creating stunning visual effects — ...') but has no 'Use when...' or equivalent explicit trigger clause, so per the guidelines completeness caps at 2.	2 / 3
Trigger Term Quality	'GLSL shader techniques', 'ray marching', 'fluid simulation', 'particle systems' are natural terms a graphics user would say, giving good coverage; slightly misses common variations like 'ShaderToy', 'fragment shader', or 'WebGL'.	3 / 3
Distinctiveness Conflict Risk	'GLSL shader techniques' is a clear, narrow niche with distinct triggers unlikely to conflict with other skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 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
relative_links	Relative link issues: 37 missing	Warning

	Total	15 / 16 Passed

Repository: MiniMax-AI/skills
Path: skills/shader-dev/SKILL.md
Commit: 60aaae5

Reviewed: 1 month 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.