CtrlK
BlogDocsLog inGet started
Tessl Logo

web-games

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

54

Quality

61%

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-claude/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

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 a well-organized, lean reference of web game development principles with concrete actionable guidance, but it carries time-sensitive version numbers that hurt conciseness and lacks a true multi-step workflow with validation checkpoints.

Suggestions

Move or quarantine time-sensitive version data (framework versions, browser-support version numbers, '(2025)' dates) into a clearly labeled 'Current versions (verify before use)' or 'Deprecated/old patterns' section so dated info does not penalize conciseness.

Add at least one concrete, copy-paste-ready code snippet for the most common task (e.g., WebGPU feature detection with WebGL fallback, or AudioContext resume on first interaction) to lift actionability to fully executable.

Provide a short explicit workflow for the highest-stakes decision (e.g., framework selection -> feature-detection check -> fallback setup) with a verification checkpoint, to raise workflow clarity above reference-level.

DimensionReasoningScore

Conciseness

The body is lean and table-driven, assuming Claude's competence, but it embeds time-sensitive version info ("Phaser 4", "PixiJS 8", "Chrome v113", "(2025)") outside any deprecated/old-patterns section, which the rubric explicitly penalizes, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Concrete, specific guidance appears throughout ("Check navigator.gpu", "KTX2, Draco, WebP", "Create AudioContext on first click/tap", "Use Web Audio API"), and while no executable code snippets are present, the rubric notes instruction-only skills are not penalized for absent code when guidance is actionable, matching 'mostly executable guidance; concrete code or commands with minor gaps'.

4 / 5

Workflow Clarity

The framework-selection decision tree provides a clear sequenced choice, but the skill is predominantly reference material (comparison tables, optimization lists) with no multi-step process and no validation checkpoints, fitting 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

No bundle files exist; the single file is well-organized into seven clearly numbered sections with a table-driven overview, so structure is good even without external references, matching 'good structure; most content is appropriately placed; references mostly clear; minor organization gaps'.

4 / 5

Total

14

/

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 names a clear domain and several relevant topic areas with good keyword coverage, but it omits an explicit 'Use when' trigger clause, capping completeness. It is concise and mostly distinct from other skills.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when building or optimizing browser-based games, or when the user mentions web games, HTML5 games, or canvas/WebGL rendering').

Include natural synonyms users say, such as 'HTML5 game', 'canvas game', or 'JavaScript game', to broaden trigger coverage.

Reframe topic areas as concrete actions (e.g., 'Select a game framework, adopt WebGPU rendering, optimize asset loading, and package as a PWA') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ("Web browser game development") plus several concrete topic areas ("Framework selection, WebGPU, optimization, PWA"), but these are subject areas rather than specific executable actions like 'build' or 'render', matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

It clearly states the 'what' ("Web browser game development principles") but provides no 'Use when...' clause or equivalent trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("Web browser game", "Framework", "WebGPU", "optimization", "PWA"), though common synonyms like 'HTML5 game', 'canvas game', or 'JavaScript game' are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The web-browser-game niche is clearly distinct from most skills, though 'optimization' and 'PWA' create minor overlap risk with general web-development skills, matching 'mostly distinct; minor overlap risk'.

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.