prototype

Concept prototype — validate the core idea is worth designing before writing GDDs. Run right after /brainstorm and /setup-engine. Routes to HTML, Engine, or Paper path based on game type. Produces a throwaway build and a PROCEED/PIVOT/KILL verdict.

Quality

88%

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

77%

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

The content is highly actionable and clearly sequenced with strong validation checkpoints. Its main weaknesses are verbosity (repeated points and anecdotal padding) and a monolithic structure that could benefit from splitting detail into referenced files.

Suggestions

Consolidate the repeated 'confusion is data / ask what was confusing' guidance into a single playtesting-protocol block referenced from Phase 5, Phase 6, and the Paper path, instead of restating it three times.

Split the per-path detail (HTML/Engine/Paper reference tables, narrative-tool lists, Spike Mode) into reference files under references/ and link to them from the main flow, moving progressive disclosure from a 2 toward a 3.

Trim anecdotal padding (game-jam name-drops like Celeste/VVVVVV, the Love2D/Balatro/Nuclear Throne asides) to one-line optional notes so each token earns its place.

Dimension	Reasoning	Score
Conciseness	The body runs ~570 lines and, while much of it is genuinely novel domain knowledge, it repeats points (e.g., 'confusion is data' / 'ask what was confusing, not did you like it' appears 3+ times) and includes anecdotal padding (game-jam mentions of Celeste/VVVVVV, Love2D name-drops) that could be tightened.	2 / 3
Actionability	Provides fully concrete, copy-ready guidance — exact AskUserQuestion prompts with enumerated options, file-path conventions, required file headers, and per-path output specs — well beyond abstract direction.	3 / 3
Workflow Clarity	Nine phases are clearly sequenced with explicit validation checkpoints: 'If the concept is too vague to form a hypothesis, stop here', the 2-hour sunk-cost rule, the KILL checklist with a 2+-box threshold, and 'get confirmation before proceeding' gates.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single monolithic ~570-line document; content that could live in separate files (path reference tables, narrative-tool lists, Spike Mode) is inline, with no signaled one-level-deep references to split the material.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive — it states concrete actions, an explicit when-to-run trigger, and natural domain vocabulary. It is a strong frontmatter description with no notable weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'validate the core idea', 'Routes to HTML, Engine, or Paper path', 'Produces a throwaway build', and a 'PROCEED/PIVOT/KILL verdict' — matching the 'Lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both 'what' (throwaway build routing to HTML/Engine/Paper) and 'when' with an explicit equivalent of a 'Use when...' clause: 'Run right after /brainstorm and /setup-engine... before writing GDDs'.	3 / 3
Trigger Term Quality	Uses natural domain terms a user would actually say — 'concept prototype', 'validate the core idea', '/brainstorm and /setup-engine', 'GDDs', 'game type' — giving good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (concept prototyping in a game-dev pipeline with a PROCEED/PIVOT/KILL verdict) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (580 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/prototype/SKILL.md
Commit: 984023d

Reviewed: 3 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.