CtrlK
BlogDocsLog inGet started
Tessl Logo

web-games

Web browser game development principles. Framework selection, WebGPU, optimization, PWA.

50

Quality

55%

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 ./.agents/skills/game-development/web-games/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-structured, concise reference material with concrete tool and format recommendations, but it lacks executable code examples and any multi-step workflow with checkpoints. Adding minimal code snippets for the common cases (GPU feature detection, a basic game loop, service-worker setup) would notably improve actionability.

Suggestions

Add a few copy-paste-ready snippets, e.g. `if (!navigator.gpu) { /* WebGL fallback */ }` for WebGPU feature detection and a minimal Web Audio resume-on-gesture example.

Provide a short ordered workflow for the most common path (pick framework → set up render loop → bundle/compress assets → add PWA service worker) with explicit checkpoints.

Move the PWA and audio sections' boilerplate requirements into a concise checklist so the body stays lean.

DimensionReasoningScore

Conciseness

The body is largely lean reference material (tables, a decision tree, terse bullets) that assumes Claude's competence; only the closing 'Remember: Browser is the most accessible platform' line and a few obvious reminders could be trimmed.

4 / 5

Actionability

It names concrete tools and formats (Phaser 4, PixiJS 8, KTX2, Draco, navigator.gpu, Web Audio API) and gives routing guidance, but contains no executable code or commands, leaving the common cases without copy-paste-ready detail.

3 / 5

Workflow Clarity

The framework decision tree provides clear routing, but the remaining sections are organized principles rather than a sequenced multi-step workflow, and no validation checkpoints are present (none are required since the skill is non-destructive).

3 / 5

Progressive Disclosure

Content is well-organized into seven numbered sections with no nested references and no bundle files to navigate; it exceeds the 50-line simple-skill threshold, so it stops just short of a 5.

4 / 5

Total

14

/

20

Passed

Description

48%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 concise and names a distinct niche with relevant keywords, but it omits any 'when to use' trigger guidance and describes topics rather than concrete actions. Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building browser-based games, HTML5 games, or 2D/3D web games.'

Reframe the topic list as concrete actions, e.g. 'Select game frameworks, adopt WebGPU, optimize assets, and configure PWA support.'

Include common synonyms users say (HTML5 game, canvas game, JavaScript game) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists the domain ('Web browser game development principles') and several subtopics ('Framework selection, WebGPU, optimization, PWA'), but these are topic nouns rather than concrete actions; no verbs describe what the skill does.

2 / 5

Completeness

It states a clear 'what' (web browser game development principles across four areas) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

It includes relevant natural terms ('Web browser game', 'WebGPU', 'PWA') but misses common synonyms users would say like 'HTML5 game', 'canvas game', 'JavaScript game', or '2D/3D game'.

3 / 5

Distinctiveness Conflict Risk

'Web browser game development' is a clearly delineated niche distinct from general web development, with only minor overlap risk against closely related game-dev or frontend skills.

4 / 5

Total

12

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
vudovn/ag-kit
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.