CtrlK
BlogDocsLog inGet started
Tessl Logo

web-games

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

52

Quality

57%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/game-development/web-games/SKILL.md

The canonical home for this skill is web-games in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 a well-organized, token-efficient reference covering framework selection, WebGPU, performance, assets, PWA, audio, and anti-patterns, but it lacks executable code, embeds time-sensitive version data outside a deprecated section, and offers no validation checkpoints.

Suggestions

Move version-specific facts (browser support versions, framework versions, the '~73%' figure) into a clearly dated 'Current support (as of 2025)' or 'Deprecated/old patterns' section so the durable guidance stays clean.

Add a few copy-paste-ready snippets, e.g. a `navigator.gpu` feature-detection + WebGL fallback block and an asset-compression command, to lift actionability.

For the asset loading and optimization flows, add explicit validation checkpoints (e.g. 'verify decoded texture size', 'confirm service worker caches the manifest') so the sequences qualify as workflows.

DimensionReasoningScore

Conciseness

The body is mostly lean tables and terse bullets with no over-explanation of concepts Claude already knows, but it embeds time-sensitive version facts ('Phaser 4', 'PixiJS 8', 'Babylon.js 7', 'Since v113', 'Firefox v131', 'Safari 18.0', '~73% global', '(2025)') outside any deprecated/old-patterns section, which the guidelines say should penalize conciseness.

3 / 5

Actionability

It gives concrete directives ('Check navigator.gpu', 'KTX2, Draco, WebP', 'Pause when hidden') and a decision tree, but contains no executable code or commands and the decision tree is pseudocode, fitting the 'some concrete guidance but incomplete' anchor.

3 / 5

Workflow Clarity

A numbered Optimization Priority (1-5) and a phased Loading Strategy give some sequence, but this is a principles/reference doc with no end-to-end workflow and no validation checkpoints, matching 'steps listed but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The content is a single self-contained file with seven well-organized numbered sections and no nested or buried references; with no bundle files present this is appropriately structured, though slightly above the under-50-line simple-skill exception.

4 / 5

Total

13

/

20

Passed

Description

61%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 clearly identifies a distinct niche and surfaces several natural trigger terms, but it describes topic areas rather than concrete actions and omits any explicit 'Use when...' guidance, capping completeness at 3.

Suggestions

Rewrite as concrete actions, e.g. 'Selects 2D/3D web game frameworks, configures WebGPU with WebGL fallback, optimizes asset loading, and sets up PWA/offline play.'

Add an explicit trigger clause: 'Use when building or optimizing browser-based games, choosing a game framework, or adopting WebGPU/PWA for games.'

Include natural synonyms users say, such as 'HTML5 game', 'browser game', or '.js game engine', to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Web browser game development principles') and four concrete sub-areas ('Framework selection, WebGPU, optimization, PWA'), but lists topics rather than verb-actions, so it sits between the 'minimal actions' (2) and '1-2 concrete actions' (3) anchors.

3 / 5

Completeness

It clearly states 'what' (web browser game development principles across four areas) but has no explicit 'Use when...' trigger clause, so per the boundary guidance completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like 'Web browser game', 'WebGPU', 'PWA', 'framework', and 'optimization' are phrases a user would naturally say when asking about web game development, with only a few synonyms (e.g. 'browser game', 'HTML5 game') missing.

4 / 5

Distinctiveness Conflict Risk

'Web browser game development' is a clear, distinct niche with low conflict risk, though the absence of explicit trigger phrases leaves minor overlap risk with general web-dev skills.

4 / 5

Total

14

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.