CtrlK
BlogDocsLog inGet started
Tessl Logo

game-studio

Route early browser-game work. Use when the user needs stack selection and workflow planning across design, implementation, assets, and playtesting before moving to a specialist skill.

70

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

85%Weight 40%Scale 1-3

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

A strong routing/umbrella skill body: highly actionable, with a clear workflow and good progressive-disclosure structure. The only real drag is mild redundancy between the Routing Rules and Default Workflow sections.

Suggestions

Collapse the duplicated 2D/Phaser vs Three.js vs R3F track guidance so it lives in one place (Routing Rules) and the Default Workflow references it rather than restating it.

Verify the eight ../../references/*.md files and eight sibling specialist skills actually ship in the bundle; the references are well-signaled but the target files were absent in this review snapshot.

DimensionReasoningScore

Conciseness

The body is lean and never explains concepts Claude already knows, but the 2D/3D/R3F track choice is restated in both "Routing Rules" and "Default Workflow" and the UI surface is mentioned repeatedly, so it could be tightened.

2 / 3

Actionability

It gives concrete routing targets (e.g. "../phaser-2d-game/SKILL.md"), explicit classification buckets, and named reference files, leaving no ambiguity about what to do for each request class.

3 / 3

Workflow Clarity

A clearly sequenced six-step Default Workflow with a closing playtest checkpoint, plus a "Do Not Stay Here When" exit condition and a "keep one coherent plan" coherence step; no destructive/batch operations require tighter feedback loops here.

3 / 3

Progressive Disclosure

The umbrella overview is appropriately split into a dedicated, one-level-deep References section pointing to specialist skills and reference docs, matching the well-signaled overview pattern. (Note: the referenced ../../references/*.md files and sibling skills are not present in this sandbox bundle.)

3 / 3

Total

11

/

12

Passed

Description

85%Weight 40%Scale 1-3

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 well-formed routing-skill description: it answers what and when, is third-person, and draws a clear boundary against specialists. Its main weakness is trigger phrasing skewed toward Claude-internal vocabulary over natural user language.

Suggestions

Add the natural user phrasing users actually say (e.g. "Use when the user says 'help me build a game' or is choosing a browser-game stack") so it triggers on common requests.

Reframe "stack selection and workflow planning" into more user-facing terms (e.g. "pick a 2D/3D engine and plan the build") to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Route early browser-game work" plus "stack selection and workflow planning across design, implementation, assets, and playtesting" names several distinct, concrete capabilities rather than vague domain labels.

3 / 3

Completeness

It states what the skill does (route early browser-game work) and an explicit "Use when the user needs…" trigger, satisfying both what and when.

3 / 3

Trigger Term Quality

"browser-game" is a reasonable natural keyword, but "stack selection" and "workflow planning" are Claude-internal phrasing; the most common user trigger ("build/make a game") is missing.

2 / 3

Distinctiveness Conflict Risk

The narrow "early browser-game work… before moving to a specialist skill" framing carves a clear niche distinct from the specialist skills it routes to, making wrong-skill triggers unlikely.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.