CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/platform-cert-overview-reference

Pure-reference catalog of the four platform-holder certification regimes a multi-platform title submits to before release: Microsoft Xbox Requirements (XR) / Xbox certification on learn.microsoft.com, Sony Technical Requirements Checklist (TRC) on the gated PlayStation DevNet portal, Nintendo Lotcheck on the gated Nintendo Developer Portal, and Steam Direct review on partner.steamgames.com. Documents the submission workflow, severity / pass-fail vocabulary, test-bench configurations, and known SLAs for each platform. Cites public sources inline; cites gated NDA portals by stable ID per PLUGIN_AUTHORING.md Step 4 fallback. Use when planning a cert calendar, mapping internal QA findings to the platform's vocabulary, or sequencing submissions across platforms.

70

Quality

88%

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

87%

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

A well-structured, information-dense reference skill with excellent progressive disclosure and actionable, specific guidance. The main gap is workflow clarity: the cross-platform sequencing is a clear process but lacks explicit validation checkpoints or feedback loops.

Suggestions

Add an explicit validation/retry checkpoint to the sequencing workflow (e.g. 'after each platform pass, confirm no open CFRs before submitting to the next').

Consider a short pre-submission checklist so the workflow reads as a gated process rather than an ordered recommendation.

DimensionReasoningScore

Conciseness

The body is lean and table-driven with no concept-explanation padding, and time-sensitive version facts are correctly isolated in a dedicated Versioning section so they do not penalize conciseness.

3 / 3

Actionability

It gives concrete, executable guidance — specific XR identifiers (XR-134, XR-045, XR-133, XR-060), SLAs in business days, bench matrices, and anti-pattern-to-fix pairs with real constants like XPRIVILEGE_*.

3 / 3

Workflow Clarity

The Sequencing section provides a clear numbered 1-4 process, but there are no explicit validation checkpoints or feedback loops; checkpoints are implicit rather than stated.

2 / 3

Progressive Disclosure

A concise overview points one level deep to three clearly signaled, verified reference files (xbox-certification.md, console-nda-regimes.md, steam-direct.md), with content appropriately split between the overview and per-regime references.

3 / 3

Total

11

/

12

Passed

Description

85%

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 an explicit Use-when clause and a well-defined niche. Its only weakness is trigger-term breadth: it relies on domain jargon a QA lead would say rather than covering the wider range of natural phrasings a user might use.

Suggestions

Add a couple of broader natural trigger phrases (e.g. 'console certification', 'submission requirements', 'cert pass/fail') so non-specialist users also match this skill.

Consider trimming the long parenthetical source citations in the description to keep the frontmatter focused on capabilities and triggers.

DimensionReasoningScore

Specificity

Names the four certification regimes and four concrete documented actions ('Documents the submission workflow, severity / pass-fail vocabulary, test-bench configurations, and known SLAs'), matching the multiple-specific-actions anchor.

3 / 3

Completeness

It states what the skill documents and gives an explicit 'Use when planning a cert calendar, mapping internal QA findings..., or sequencing submissions' clause, answering both what and when.

3 / 3

Trigger Term Quality

Natural triggers like 'planning a cert calendar' and 'sequencing submissions across platforms' are present, but the phrasing leans on insider QA vocabulary and omits common layperson variations, so it falls short of full coverage.

2 / 3

Distinctiveness Conflict Risk

The niche of platform-holder certification regimes is highly specific with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

11

/

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