CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webgl-laser

Create a fixed full-screen WebGL laser background effect with a thin white-hot vertical core, restrained brand-colored halo, and soft smoky fog around the beam. Use only for laser background effects, not full page layout, copy, generic hero scenes, particles, or unrelated motion systems.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

Excellent actionability — complete, executable WebGL code with error handling, reduced-motion support, and cleanup — and lean prose with no filler. Weaker on structure-to-files: everything lives in one long SKILL.md, and Visual Target / Taste Rules / Avoid overlap, plus no explicit verification step after integration.

Suggestions

Move the full fragment shader and initWebGLLaser initializer into a references/ file (e.g., references/laser-shader.js) and keep SKILL.md as an overview with the layering snippet and integration call, so ~180 lines of code are loaded only when needed.

Consolidate Visual Target, Taste Rules, and Avoid into a single section — they restate the same constraints (thin white-hot core, restrained brand halo, readable foreground) three times.

Add an explicit verification step after integration, e.g. confirm the shader compiled (the thrown errors) and visually check that foreground content remains readable against the glow.

DimensionReasoningScore

Conciseness

The body is code-dense with almost no explanation of concepts Claude already knows, and the shader constants are non-obvious craft knowledge that earns its place. Minor trimming is possible: Visual Target ("thin vertical beam... narrow colored halo", "Dark cinematic field") overlaps with Taste Rules ("The hottest beam core stays near white") and Avoid ("Making the beam thick enough to read as a glowing bar"), which restate the same constraints three ways.

4 / 5

Actionability

Fully executable, copy-paste-ready code covers the whole flow: hexToRgb01 accent parsing, complete vertex/fragment shaders, createShader/createProgram with compile/link error handling, an initWebGLLaser initializer with DPR-capped resize, reduced-motion handling, and a cleanup function, plus named tuning knobs with concrete default values (coreWidth 0.0045, glowWidth 0.035, smokeDensity 0.52). Nothing is pseudocode.

5 / 5

Workflow Clarity

Sections form a coherent build order (Layering markup/CSS -> Brand color -> Raw WebGL Setup -> Initializer -> Tuning Knobs), and error checkpoints exist via thrown compile/link errors. It falls short of anchor 5 because there is no explicit post-implementation verification step (e.g., confirming the beam renders and foreground content stays readable), keeping the checkpoint implicit.

4 / 5

Progressive Disclosure

The file is well-sectioned but ~180 lines of shader and initializer code are inlined in SKILL.md with no bundle files at all (references/, scripts/, assets/ are absent). This matches anchor 3 — structure present, but content that would reduce always-loaded tokens (the full shader source, deep tuning guidance) is inline rather than one level deep. Not anchor 4 because the split into a reference file is an obvious, unexploited organization improvement for a skill this size.

3 / 5

Total

16

/

20

Passed

Description

87%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: specific, third-person, with a concrete what and an explicit use/not-use boundary that both triggers correctly and fences off adjacent skills. The only gap is modest keyword breadth for natural user phrasings like glow or light beam.

DimensionReasoningScore

Specificity

"Create a fixed full-screen WebGL laser background effect with a thin white-hot vertical core, restrained brand-colored halo, and soft smoky fog" names the domain and concrete visual components in third-person imperative voice. It stops short of anchor 5 because it describes a single creation action with rich visual detail rather than multiple distinct actions, and gives no coverage of tuning/integration capability.

4 / 5

Completeness

"Create a fixed full-screen WebGL laser background effect..." explicitly answers what it does, and "Use only for laser background effects, not full page layout, copy, generic hero scenes, particles, or unrelated motion systems" gives an explicit trigger clause with concrete in/out scope. Both what and when are clearly and explicitly stated, matching the anchor-5 pattern; anchor 4 would require the 'when' to be less explicit than this.

5 / 5

Trigger Term Quality

Natural terms like "laser background effect", "beam"-adjacent "vertical core", "halo", "fog", and "WebGL" are present, and exclusion terms ("particles", "hero scenes") sharpen matching. A few common user phrasings are missing (e.g., "glow", "light beam", "neon", "sci-fi"), so it sits just below comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Use only for laser background effects, not full page layout, copy, generic hero scenes, particles, or unrelated motion systems" carves out a clear niche and explicitly disambiguates against the nearest competing skills (particle systems, hero sections, general motion). Conflict risk is minimal.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MengTo/Skills

Path

agent-skills/web-design/webgl-laser/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.