CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-sequenced instruction skill: it maps the player journey, prescribes deterministic fixture states, and defines concrete evidence to capture without wasting a token on background explanation. Its only weakness is mild — the absence of a sample fixture or report template that would push actionability to copy-paste readiness.

DimensionReasoningScore

Conciseness

The ~24-line body contains zero padding and no concepts Claude already knows; every sentence adds game-QA-specific structure (test matrix stages, fixture states, evidence fields), matching the 'lean and efficient; every token earns its place' anchor. It is not the 4 anchor because there is no over-explanation to trim anywhere.

5 / 5

Actionability

It enumerates concrete fixture states ("combat phase, inventory loadout, boss phase, tutorial step, save migration, low health, and error states"), exact verification targets, and report fields ("reproduction steps, expected versus actual result, severity, device/viewport"), which is mostly executable guidance — fitting the 'concrete guidance with minor gaps' anchor for an instruction-only skill. Not 5 because there are no example commands, fixture snippets, or a sample report format to make the guidance copy-paste ready.

4 / 5

Workflow Clarity

The four sections form a clear sequence (build test matrix, prepare deterministic states, verify the player experience, report evidence) with checkpoints like "Confirm screen-visible feedback after each meaningful action" and "Inspect console warnings/errors", matching the 'clear sequence with most checkpoints present' anchor. Not 5 because error-recovery feedback loops (what to do when a check fails) are only implicit, and not 3 because validation checkpoints are explicitly stated.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and needs no external references; its well-organized section headers satisfy the rubric's exception for simple self-contained skills scoring 5. The body is a clear overview with no content that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

83%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 description with an explicit 'Use for...' trigger clause and natural, well-scoped keywords for game QA. It is clearly distinct from generic web testing skills, with only minor gaps in synonym coverage and a composite rather than enumerated action list.

DimensionReasoningScore

Specificity

"Test a playable browser game end to end with deterministic fixtures and real browser evidence" names the domain and several specific task areas (controls, save flows, console checks, performance smoke tests), matching the 'several specific actions; minor gaps' anchor. Not 5 because the capability statement is a single composite action while the task breadth lives in the trigger list rather than in distinct concrete actions.

4 / 5

Completeness

It clearly states what the skill does (end-to-end testing of a playable browser game with deterministic fixtures and real browser evidence) and includes an explicit 'Use for...' clause with concrete trigger phrases, matching the top anchor exactly. Both 'what' and 'when' are explicit, so neither the 4 anchor (implicit 'when') nor 3 anchor (missing 'when') applies.

5 / 5

Trigger Term Quality

The trigger list ("gameplay QA, regression testing, controls, accessibility, responsive/mobile testing, save flows, console checks, performance smoke tests, release verification") uses natural phrases users would say, matching the 'good keyword coverage; a few natural terms missing' anchor. Not 5 because synonyms like 'playtest', 'playthrough', or 'QA testing' variations are absent.

4 / 5

Distinctiveness Conflict Risk

"playable browser game", "gameplay QA", and "save flows" establish a clear niche that distinguishes it from general web-UI or code-testing skills, fitting the 'mostly distinct; minor overlap risk' anchor. Not 5 because 'accessibility' and 'responsive/mobile testing' could also activate broader web testing or general QA skills.

4 / 5

Total

17

/

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
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.