CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

webgl-landing-steering

Use when creating or refining WebGL-heavy landing pages and you need to steer toward a specific visual outcome (premium, technical, playful, cinematic) while balancing conversion clarity, performance, and implementation complexity.

Quality

79%

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 ./agent-skills/web-design/webgl-landing-steering/SKILL.md
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 dense, well-structured steering skill: it maps landing-page goals to concrete WebGL lanes, stacks, and fallback rules with a clear quality-gate checklist. Its gaps are the absence of any executable code or verifiable (command-based) validation steps, and one meta section (the Codex-style prompting template) that could be trimmed or offloaded to a reference file.

Suggestions

Add a small executable snippet for the recurring gates — e.g., the DPR cap (`renderer.setPixelRatio(Math.min(devicePixelRatio, 2))`), a `prefers-reduced-motion` check, and a `webglcontextlost` handler — to lift actionability to copy-paste-ready.

Convert subjective gates into verifiable checks (a target FPS/frame-time budget with a measurement method, or a contrast-check tool), so the workflow has explicit validation rather than judgment calls.

Move the per-lane visual/stack specs or the 'Prompting template' section into a reference file (e.g., references/lanes.md), keeping SKILL.md as the decision overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what WebGL or Three.js is and compresses guidance into dense, useful lists (e.g., 'Cap pixel ratio: `Math.min(devicePixelRatio, 1.5-2)`'). The 'Prompting template for Codex-style execution' section is meta-content of questionable necessity inside a skill body, keeping it below the level-5 'every token earns its place' anchor. It is well above level 3 since there is no padded or redundant explanation to cut.

4 / 5

Actionability

Concrete, decision-level guidance throughout: the page-type matrix maps situations to lanes ('Pricing / high-intent page: Mostly Lane A. Keep WebGL decorative only.'), stacks are specific ('Three.js + GLTF/DRACO/KTX2 pipeline'), and failure→fix pairs are actionable. As an instruction-only steering skill, missing code is not penalized, but there is no copy-paste-ready snippet covering the common cases, so it falls short of level 5.

4 / 5

Workflow Clarity

A clear numbered sequence (define intent → choose lane → steering matrix → quality gates → risk tiers → template → failure patterns) with the four quality gates acting as explicit checkpoints. The gates are subjective criteria ('Hero headline + CTA readable in under 3 seconds', 'Target stable frame time on common mobile devices') rather than verifiable commands, so it does not reach level 5. No destructive or batch operations, so the level-3 cap does not apply.

4 / 5

Progressive Disclosure

Well-organized sections with no dead or buried references (none exist), and the core decision guidance appropriately lives in SKILL.md. At ~116 lines it exceeds the under-50-line simple-skill exception, and content such as the four per-lane specs or the prompting template could plausibly be split into reference files, which keeps it at level 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

73%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, well-scoped description with an explicit 'Use when' trigger and a clearly delineated niche. Its main weakness is the second-person 'you need to steer' construction and an abstract 'what' clause, plus missing common trigger synonyms like Three.js or 3D hero.

Suggestions

Rewrite in third-person imperative voice (e.g., 'Steers WebGL-heavy landing pages toward a specific visual outcome...') to remove the 'you need to' second-person phrasing and recover the specificity penalty.

Add natural trigger synonyms users would say, such as 'Three.js', '3D hero section', 'shader background', or 'interactive landing page'.

Make the 'what' more concrete: name the actual deliverables (lane recommendation, visual spec, fallback plan, performance checklist) instead of the abstract 'steer toward a specific visual outcome'.

DimensionReasoningScore

Specificity

Names the domain ('WebGL-heavy landing pages') and several actions ('creating or refining', 'steer toward a specific visual outcome', 'balancing conversion clarity, performance, and implementation complexity'), which would rate 4, but the second-person phrase 'you need to steer' incurs the rubric's 1-point voice penalty. It is above level 2 because the actions are more concrete than 'Names the domain but actions are minimal or generic'.

3 / 5

Completeness

Both parts are explicit: 'Use when creating or refining WebGL-heavy landing pages' (when) and 'steer toward a specific visual outcome... while balancing conversion clarity, performance, and implementation complexity' (what). The 'what' is somewhat abstract ('steer'), falling short of the level-5 anchor's concrete what-and-when pairing.

4 / 5

Trigger Term Quality

Natural terms users would say are present ('WebGL-heavy landing pages', 'premium, technical, playful, cinematic', 'conversion', 'performance'), but common synonyms like 'Three.js', '3D hero', or 'shader background' are missing. Good coverage, not comprehensive — so 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

'WebGL-heavy landing pages' plus the four named visual lanes (premium, technical, playful, cinematic) define a clear niche with distinct triggers and minimal overlap with generic web-development or animation skills.

5 / 5

Total

16

/

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-landing-steering/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.