corner-lasers

Create a corner-anchored laser composition with thin beams, a bright emitter node, bloom, and atmospheric glow or fog.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/corner-lasers/SKILL.md

Quality

Content

61%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 lean, well-organized, and gives clear directional guidance for a single-purpose visual effect, but it lacks executable code or concrete parameters and leaves the Workflow section empty. It is a competent instruction-only skill with room to add implementation specifics.

Suggestions

Fill the empty '## Workflow' section with an explicit ordered sequence (e.g. 1. pick corner emitter, 2. derive beam directions, 3. render SDF beams, 4. add bloom hotspot, 5. layer atmospheric glow) to raise workflow clarity.

Add a minimal executable shader snippet or concrete falloff/parameter ranges (bloom radius, beam thickness, fog density) so the guidance is copy-paste ready rather than purely directional.

Remove the verbatim 'Use When' echo of the frontmatter description and the redundancy of color/atmosphere points across 'Visual target', 'Implementation guidance', and 'Tuning knobs' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is efficient with tight bullets and no padding of concepts Claude already knows, but the empty '## Workflow' heading, verbatim 'Use When' echo of the description, and repeated color/atmosphere points across sections keep it at anchor 4 rather than 5.	4 / 5
Actionability	Guidance is concrete and directional ('signed-distance or line-distance logic', 'off-center corner point', 'concentrated bloom at the corner emitter') but provides no executable shader code or specific parameter values, matching the incomplete-but-concrete anchor 3.	3 / 5
Workflow Clarity	An implicit sequence exists within Implementation guidance (anchor -> beams -> bloom -> atmosphere -> motion), but the '## Workflow' section is empty and the sequence is not explicitly laid out, fitting anchor 3; the task is non-destructive so no validation cap applies.	3 / 5
Progressive Disclosure	The short, well-sectioned body needs no external references and is well organized, but the empty '## Workflow' heading is a minor structural gap that holds it at anchor 4 rather than 5.	4 / 5
	Total	14 / 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 is specific and distinctive about its visual niche but lacks an explicit 'when to use it' trigger clause, which caps completeness and limits trigger-term coverage. It is solid but not exemplary.

Suggestions

Add a 'Use when...' clause naming concrete user triggers, e.g. 'Use when creating corner-anchored laser or beam effects with bloom and atmospheric glow.'

Broaden trigger terms with natural synonyms users might say, such as 'light rays', 'neon beams', or 'portal seam', to improve discovery.

Frame the action as multiple concrete steps (e.g. 'anchor a corner emitter, draw thin SDF beams, add bloom and volumetric haze') to raise specificity above a single 'Create' verb.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete visual elements ('thin beams, a bright emitter node, bloom, and atmospheric glow or fog') but offers only a single action ('Create'), so it matches anchor 3 rather than the multi-action anchor 4.	3 / 5
Completeness	It gives a clear 'what' but contains no 'Use when...' clause or equivalent trigger guidance, so per the judging guideline completeness is capped at anchor 3.	3 / 5
Trigger Term Quality	It includes relevant natural terms a user might say ('laser', 'beams', 'bloom', 'glow', 'fog') but misses common variations or synonyms like 'light rays', 'neon', or 'shader effect', placing it at anchor 3.	3 / 5
Distinctiveness Conflict Risk	'corner-anchored laser composition' carves a distinct niche with low conflict risk, but the absence of explicit triggers leaves minor overlap with generic glow/bloom effect skills, fitting anchor 4.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MengTo/Skills
Path: agent-skills/web-design/corner-lasers/SKILL.md
Commit: 4c716b5

Reviewed: 10 days 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.