CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/platform-cert-overview-reference

Reference catalog of game-QA test categories and the four platform-holder certification regimes a multi-platform title submits to before release. Defines the six canonical test categories (functional / compliance / compatibility / performance / localization / accessibility) plus the multiplayer and content-rating cross-axes; documents the submission workflow, severity vocabulary, test-bench configurations, and known SLAs for Microsoft Xbox Requirements (XR), Sony TRC (gated PlayStation DevNet), Nintendo Lotcheck (gated Nintendo Developer Portal), and Steam Direct review; and includes the building-a-cert-checklist workflow that maps a target platform's requirement items to the six categories. Cites public sources inline; cites gated NDA portals by stable ID per PLUGIN_AUTHORING.md Step 4 fallback. Use when planning a game test pass or cert calendar, mapping internal QA findings to the platform's vocabulary, sequencing submissions across platforms, or emitting a pre-submission checklist.

69

Quality

87%

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

78%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 well-organized reference catalog that splits per-regime detail into one-level-deep bundle files and provides a concrete checklist-generation workflow. It is dense and mostly lean, with minor room to tighten prose and strengthen feedback loops.

Suggestions

Tighten the Overview prose so it does not restate dimensions already covered by the Cross-platform comparison summary table.

Add an explicit validate→fix→retry feedback loop to the 'Building a cert checklist' workflow (e.g. re-resolve requirement IDs after edits and re-run until no stale IDs remain).

Convert the most descriptive category/comparison tables into actionable 'how to use this' framing where possible to raise the share of instructional content.

DimensionReasoningScore

Conciseness

Mostly efficient and information-dense (tables for regimes, categories, comparison, anti-patterns) with only minor spots that could be trimmed, e.g. the Overview prose overlaps slightly with the cross-platform comparison table.

4 / 5

Actionability

Gives concrete actionable guidance — the checklist workflow specifies exact columns ('# | Requirement | Description | Test Category | Pass Signal | N/A?'), exact source URLs, and stable-ID citation rules — but a fair share of the body is descriptive reference (category/comparison tables) rather than instruction.

4 / 5

Workflow Clarity

The four-step checklist workflow and the triage workflow are clearly sequenced with explicit validation guards ('Refuse to emit a checklist item whose claim has no available source'; 'confirm the category and requirement ID still resolve... before closing'), but there is no strong validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Clear overview structure with well-signaled one-level-deep references: each regime points to its own file (xbox-certification.md, console-nda-regimes.md, steam-direct.md, platform-cert-details.md), all of which exist in references/.

5 / 5

Total

17

/

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 dense, specific description that clearly states both capabilities and trigger conditions for a well-scoped niche. It is slightly jargon-heavy but still uses several natural user phrases.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with comprehensive coverage: 'Defines the six canonical test categories', 'documents the submission workflow, severity vocabulary, test-bench configurations, and known SLAs' for four named platforms, and 'includes the building-a-cert-checklist workflow'.

5 / 5

Completeness

Explicitly answers both what ('Reference catalog of game-QA test categories and the four platform-holder certification regimes...') and when ('Use when planning a game test pass or cert calendar, mapping internal QA findings... or emitting a pre-submission checklist') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage including natural user phrases ('game test pass', 'cert calendar', 'pre-submission checklist', 'QA findings') and platform names (XR, TRC, Lotcheck, Steam Direct), though a few common synonyms a user might say (e.g. 'release readiness', 'going gold', 'compliance check') are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (game platform certification across Xbox/PlayStation/Nintendo/Steam) with distinct triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents