phaser-2d-game

Implement 2D browser games with Phaser. Use when the user wants a Phaser, TypeScript, and Vite stack for scenes, gameplay systems, cameras, sprite animation, and DOM-overlay HUD patterns.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%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.

An efficient, well-structured architectural overview that assumes competence and avoids padding, but it offers no executable code or validation steps and leans on a referenced detail file (phaser-architecture.md) that is not present in the bundle.

Suggestions

Add at least one concrete, copy-paste-ready example (e.g. a minimal Phaser scene + Vite config snippet or a manifest key usage) to lift actionability from directional to executable.

Include a brief validation/checkpoint step in the build sequence (e.g. 'confirm the scene reads simulation state through the integration boundary before adding view effects') to give the workflow explicit feedback points.

Either ship the referenced ../../references/phaser-architecture.md (and verify the sibling SKILL.md paths) or inline the directory-shape detail so progressive disclosure is actually resolvable from the bundle.

Dimension	Reasoning	Score
Conciseness	The body is lean and high-signal, assuming Claude already knows Phaser/Vite and giving only architectural guidance (e.g. "Keep gameplay state outside Phaser scenes") with no filler or concept explanations, matching the score-3 anchor.	3 / 3
Actionability	Guidance is concrete and directional (asset manifest keys, scene split, camera models) but contains no executable code, commands, or copy-paste examples, and the concrete directory shape is deferred to a reference, fitting score 2 rather than the fully-executable score 3.	2 / 3
Workflow Clarity	The Architecture section gives a clear build sequence (Boot/preload -> Menu/shell -> Gameplay -> overlay) but has no validation checkpoints or feedback loops, matching the score-2 anchor of sequence present with checkpoints missing.	2 / 3
Progressive Disclosure	Sections are well-organized with clearly signaled one-level references, but the primary detailed reference (../../references/phaser-architecture.md) does not exist in the bundle and sibling skill paths are also absent, so the promised progressive disclosure is not actually delivered, pulling this to score 2.	2 / 3
	Total	9 / 12 Passed

Description

100%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 tight, third-person description that names concrete capabilities, provides an explicit use-trigger, and carves out a distinct Phaser/TypeScript/Vite niche. It is concise without padding and avoids vague language.

Dimension	Reasoning	Score
Specificity	It states a concrete action ("Implement 2D browser games with Phaser") and enumerates multiple specific capability areas ("scenes, gameplay systems, cameras, sprite animation, and DOM-overlay HUD patterns"), matching the score-3 anchor for multiple specific concrete actions rather than the partial coverage of score 2.	3 / 3
Completeness	It answers both what ("Implement 2D browser games with Phaser") and when via an explicit "Use when the user wants a Phaser, TypeScript, and Vite stack..." trigger clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	It surfaces the natural terms a user would actually say ("Phaser", "TypeScript", "Vite", "2D browser games"), giving good coverage rather than just some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The Phaser + TypeScript + Vite niche with scoped subsystem triggers is a clear, distinct niche unlikely to fire for unrelated skills; it is not the broad-overlap case of score 2.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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.

Repository: openai/plugins
Path: plugins/game-studio/skills/phaser-2d-game/SKILL.md
Commit: 11c74d6

Reviewed: 17 days ago

Table of Contents

Discovery Implementation Validation

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.