bmad-gds

AI-driven Game Development Studio using BMAD methodology. Routes game projects through Pre-production, Design, Architecture, Production, and Game Testing phases with 6 specialized agents. Supports Unity, Unreal Engine, Godot, and custom engines.

2.08x

Quality

45%

Does it follow best practices?

Impact

96%

2.08x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent-skills/bmad-gds/SKILL.md

Quality

Discovery

40%

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 establishes a clear domain (game development with BMAD methodology) and mentions specific engines, giving it good distinctiveness. However, it lacks concrete action verbs describing what the skill actually does and critically omits any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'when the user wants to create a game', 'start a game project', 'game development workflow', or 'build a Unity/Unreal/Godot game'.

Replace abstract phase names with concrete actions: instead of 'Routes through Pre-production', say 'Creates game design documents, defines core mechanics, plans technical architecture'.

Include natural user language variations like 'make a game', 'game idea', 'game prototype' that users would actually say when needing this skill.

Dimension	Reasoning	Score
Specificity	Names the domain (game development) and lists phases (Pre-production, Design, Architecture, Production, Game Testing) and mentions engine support, but doesn't describe concrete actions like 'creates game design documents' or 'generates architecture diagrams'.	2 / 3
Completeness	Describes what it does (routes game projects through phases with agents) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Unity', 'Unreal Engine', 'Godot', and 'Game Development', but missing common user phrases like 'make a game', 'game project', 'build a game', or 'game design'.	2 / 3
Distinctiveness Conflict Risk	The combination of BMAD methodology, specific game engines (Unity, Unreal, Godot), and game development phases creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Implementation

50%

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

This skill provides a comprehensive command reference for a game development workflow system, with good structural organization via tables. However, it lacks concrete examples of command usage, expected outputs, and validation steps. The content reads more like a feature list than actionable guidance for executing the workflow.

Suggestions

Add a concrete example showing one complete mini-workflow (e.g., brainstorm → brief → GDD) with sample inputs and expected outputs

Include validation checkpoints in the Typical Workflow section (e.g., 'Verify GDD completeness before proceeding to architecture')

Remove the redundant Quick Reference table or consolidate it with the phase-based command tables

Add links to detailed documentation for complex commands or reference external files for agent-specific guidance

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient with table-based command references, but includes some redundancy (Quick Reference duplicates earlier tables) and the 'When to use this skill' section explains obvious use cases Claude could infer.	2 / 3
Actionability	Commands are clearly listed with descriptions, but there's no concrete example of what running a command produces, no sample inputs/outputs, and no executable code showing how to actually use the workflow beyond command names.	2 / 3
Workflow Clarity	The 'Typical Workflow' section provides a clear 8-step sequence, but lacks validation checkpoints, error handling guidance, or feedback loops for when steps fail or need iteration.	2 / 3
Progressive Disclosure	Content is organized into logical sections with tables, but everything is in one file with no references to detailed documentation for individual commands, agents, or advanced usage patterns.	2 / 3
	Total	8 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: supercent-io/skills-template
Commit: c033769

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