CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/platform-cert-overview-reference

Use when planning a game test pass or certification calendar across Xbox (XR), PlayStation (TRC), Nintendo (Lotcheck) and Steam: the six game QA test categories, submission workflows, severity terms and SLAs, mapping QA findings to platform terms and building a pre-submission checklist.

Quality

94%

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

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 well-structured reference skill: token-efficient tables of genuinely domain-specific knowledge, fully actionable triage and checklist workflows with explicit validation guards, and a clean one-level reference split that checks out against the actual bundle. The only gaps are minor — some repeated citations and the absence of an explicit error-recovery loop in the workflows.

Suggestions

Cite the Microsoft certification-guide URL once (e.g., in the regimes table or a Sources section) and reference it by name elsewhere, trimming the repeated inline links in the Performance, Multiplayer, checklist, and anti-pattern sections.

Add a brief error-recovery step to the checklist workflow (e.g., 'if a requirement ID no longer resolves in the current GDK/TRC list, re-verify against the latest version before emitting the row') to close the feedback loop the triage section already hints at.

DimensionReasoningScore

Conciseness

The body is dense with non-generalizable domain knowledge (CFR/SRI/ION codes, XR-133 limits, per-platform SLAs, bench matrices) presented largely in efficient tables, with time-sensitive version facts correctly isolated in a 'Versioning and deprecation' section. Minor trimming opportunities remain — the certification-guide URL is repeated ~5 times and a few prose passages (e.g., 'This is a heuristic, not a mandate...') could be tightened — which fits 'efficient; minor instances that could be trimmed' rather than the 'every token earns its place' top anchor.

4 / 5

Actionability

For an instruction-only reference skill the guidance is fully actionable: the checklist workflow specifies exact steps, the column schema '# | Requirement | Description | Test Category | Pass Signal | N/A?', per-platform ordering, the keep-and-mark-N/A policy, and a refusal rule; the triage table and anti-patterns table cite concrete requirement IDs (XR-024, XR-045, XR-133, XR-060), SLAs (5 BD, 3-5 BD plan for 7), and frame-time targets. This matches the 'specific examples cover the common cases' top anchor.

5 / 5

Workflow Clarity

Both multi-step workflows are clearly sequenced and include explicit checkpoints — 'confirm the category and requirement ID still resolve in the current requirements list before closing' in triage and 'Refuse to emit a checklist item whose claim has no available source' in checklist building. However, no error-recovery feedback loop (validate → fix → retry) is present, which the level 5 anchor requires, so it sits at 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all four cited files (references/xbox-certification.md, console-nda-regimes.md, steam-direct.md, platform-cert-details.md) exist, are clearly signaled from the body's per-regime sections, and contain no nested references (one level deep). The body appropriately keeps the taxonomy, comparison, and workflow while per-regime detail lives in the reference files — matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

18

/

20

Passed

Description

100%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 model description: explicit 'Use when' trigger guidance with concrete platform synonyms, followed by a comprehensive, specific list of capabilities. Voice and structure match the best reference examples with no padding or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "the six game QA test categories, submission workflows, severity terms and SLAs, mapping QA findings to platform terms and building a pre-submission checklist" — covering the domain comprehensively, which matches the top anchor rather than the 'minor gaps' level 4 anchor.

5 / 5

Completeness

It explicitly answers both questions: an explicit trigger clause "Use when planning a game test pass or certification calendar across Xbox (XR), PlayStation (TRC), Nintendo (Lotcheck) and Steam" plus a concrete 'what' after the colon. This matches the level 5 anchor with concrete trigger phrases, not the vaguer 'when' of level 4.

5 / 5

Trigger Term Quality

Natural trigger phrases ("game test pass", "certification calendar", "submission", "pre-submission checklist") are complemented by platform names with their regime synonyms — "Xbox (XR), PlayStation (TRC), Nintendo (Lotcheck) and Steam" — giving comprehensive synonym coverage users would actually say; level 4's 'a few natural terms missing' does not apply.

5 / 5

Distinctiveness Conflict Risk

The multi-platform game certification niche (XR / TRC / Lotcheck / Steam Direct) is highly distinct with platform-specific triggers; minimal overlap risk with any adjacent QA or publishing skill, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

20

/

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.

Reviewed

On this page