CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/game-test-categories-reference

Pure-reference catalog of the testing categories that apply to a video-game build before it ships. Defines the six canonical buckets the industry tests against - functional / compliance / compatibility / performance / localization / accessibility - plus the multiplayer and content-rating sub-axes. Cross-references each bucket to the platform-holder vocabulary that drives it (Microsoft Xbox Requirements / XR test cases, Sony TRC, Nintendo Lotcheck, Steam Direct review). Use as the taxonomy lookup when planning a game test pass, scoping QA effort, or mapping platform-cert findings back to internal test categories.

79

Quality

99%

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

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured pure-reference taxonomy that adds genuinely non-obvious game-certification domain knowledge, routes detail to a single real one-level-deep reference file, and pairs its triage workflow with an explicit verification step. The main latent risk is mild redundancy across the table, cheatsheet, and anti-patterns sections, but each serves a distinct purpose.

DimensionReasoningScore

Conciseness

Dense with niche domain specifics Claude does not already know (CFR/SRI/ION severity codes, 16.67ms/60Hz and 33.33ms/30Hz budgets, the Xbox bench matrix, XAG sub-axes) and avoids explaining basic concepts; the few prose passages each carry reference value.

3 / 3

Actionability

Concrete, specific guidance throughout - named severity codes, exact frame-time/load budgets, a symptom-to-category cheatsheet with severity hints, and a step-by-step triage procedure; as an instruction-only reference it supplies copy-usable specifics rather than vague direction.

3 / 3

Workflow Clarity

The triage workflow is a clearly sequenced six-step process with an explicit verification checkpoint at step 6 ("Verify before closing... a mismatched category or stale XR number is the common triage error") that functions as a feedback loop catching the documented failure mode.

3 / 3

Progressive Disclosure

Well-organized overview plus clearly signaled one-level-deep references; the single bundle file references/platform-cert-details.md exists and holds the detail tables (severity model, bench layout) that back the taxonomy, with no nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

100%

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 high-quality, third-person description that states concrete capabilities and gives an explicit, multi-trigger Use-when clause tied to natural game-QA phrasing. Its only minor risk is length, but every clause carries specific information rather than fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/capabilities: "Defines the six canonical buckets", "Cross-references each bucket to the platform-holder vocabulary", and a taxonomy lookup applied to six named QA tasks (planning a test pass, scoping QA effort, mapping findings, preparing a submission checklist, reviewing certification requirements, triaging failures).

3 / 3

Completeness

Explicitly answers both what ("Pure-reference catalog of the testing categories...") and when ("Use as the taxonomy lookup when planning a game test pass, scoping QA effort...") with an explicit multi-trigger Use-when clause.

3 / 3

Trigger Term Quality

Good coverage of natural terms a game-QA user would actually say - "game test pass", "scoping QA effort", "submission checklist", "first-party certification requirements", "cert testing failures" - alongside the domain vocabulary (TRC, Lotcheck, XR) that pins the niche.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (video-game ship/cert testing taxonomy cross-referenced to platform-holder vocabularies) with triggers specific to game QA/submission that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents