test-playable-web-games

Test a playable browser game end to end with deterministic fixtures and real browser evidence. Use for gameplay QA, regression testing, controls, accessibility, responsive/mobile testing, save flows, console checks, performance smoke tests, and release verification.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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 tight, well-structured testing skill that is actionable and concise. The one improvement is making the failure-recovery loop explicit (what to do when a check fails or a regression is found).

Suggestions

Add an explicit feedback loop for failures: e.g., when a screen-visible check or console check fails, state how to reproduce, confirm severity, and retry after a fix.

Clarify the verification checkpoint on regressions: spell out 'stop and file a regression' vs 'record and continue' so the test matrix doesn't get abandoned mid-run.

Optionally note how to re-seed fixtures when a deterministic state does not reproduce the reported bug.

Dimension	Reasoning	Score
Conciseness	Lean, actionable prose with no padding or explanation of concepts Claude already knows; every sentence earns its place.	5 / 5
Actionability	Concrete, specific guidance throughout (named journey stages, fixture examples like 'boss phase' and 'save migration', explicit feedback checks and report fields), fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	Clear four-section sequence (matrix, fixtures, verify, report) with verification checkpoints ('Confirm screen-visible feedback after each meaningful action', console inspection, baseline separation), but an explicit failure-recovery feedback loop is only implied rather than stated.	4 / 5
Progressive Disclosure	A simple, single-purpose skill under 50 lines with no need for external references; four well-organized section headers provide clear navigation per the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

92%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, specific description with explicit what/when structure and a broad concrete trigger list. The only gap is a few missing synonyms that would round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (gameplay QA, regression testing, controls, accessibility, save flows, console checks, performance smoke tests) with comprehensive coverage rather than minor gaps.	5 / 5
Completeness	Explicitly answers both what ('Test a playable browser game end to end with deterministic fixtures and real browser evidence') and when (a concrete 'Use for...' trigger clause listing many scenarios).	5 / 5
Trigger Term Quality	Good natural keyword coverage ('gameplay QA', 'regression testing', 'save flows', 'console checks', 'performance smoke tests') but lacks synonym/extension variants that anchor 5 expects.	4 / 5
Distinctiveness Conflict Risk	Targets a clear 'playable browser game' niche with game-specific triggers (gameplay QA, save flows, boss/encounter testing) unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 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/game-development/test-playable-web-games/SKILL.md
Commit: 4c716b5

Reviewed: 4 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.