game-development

Game development orchestrator. Routes to platform-specific skills based on project needs.

Quality

35%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/game-development/SKILL.md

Quality

Content

42%Scale 1-5

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

This orchestrator skill has a clear routing structure with well-organized tables directing to sub-skills, but suffers from two main issues: it explains many concepts Claude already knows (game loops, collision types, design patterns) without adding novel or project-specific value, and it lacks actionable, executable guidance—everything remains at the conceptual/descriptive level. The referenced sub-skills don't exist in the bundle, making the routing promises hollow.

Suggestions

Remove or drastically reduce the Core Principles sections (game loop, collision types, AI selection, design patterns) — Claude already knows these concepts well. Replace with project-specific decision rules or configuration templates.

Add at least one concrete, executable code example for bootstrapping a game project (e.g., a minimal game loop implementation in a specific framework) to improve actionability.

Either provide the referenced sub-skill files in the bundle or replace sub-skill references with inline actionable guidance for the most common cases (e.g., web-based 2D games).

Add a concrete workflow with validation steps for starting a new game project: e.g., 1) determine platform → 2) scaffold project with specific command → 3) verify build runs → 4) implement game loop.

Dimension	Reasoning	Score
Conciseness	The skill contains useful reference tables and routing information, but several sections explain concepts Claude already knows well (game loop fundamentals, what input abstraction is, basic collision types, common design patterns). The anti-patterns table and AI selection matrix are general game dev knowledge that doesn't need to be spelled out. However, the routing tables and pattern selection matrix are reasonably efficient.	3 / 5
Actionability	The skill is almost entirely descriptive and conceptual rather than actionable. There are no executable code examples, no specific commands, no concrete framework recommendations, and no copy-paste ready snippets. The game loop is shown as pseudocode concepts, and the routing tables point to sub-skills that don't exist in the bundle. The content tells Claude what patterns exist but not how to implement them.	2 / 5
Workflow Clarity	The routing examples at the bottom provide a reasonable sequence for which sub-skills to consult in order, and the routing tables are clear. However, there are no validation checkpoints, no feedback loops, and no concrete steps for actually starting a game project. For an orchestrator skill, the routing logic is present but lacks decision criteria beyond surface-level matching.	3 / 5
Progressive Disclosure	The skill references many sub-skills (web-games, mobile-games, 2d-games, etc.) which is good orchestrator design, but none of these sub-skills exist in the bundle. The routing tables are well-structured, but the core principles section inlines a significant amount of general knowledge that could either be omitted (Claude knows this) or placed in a separate reference file. The structure is reasonable but the balance between inline content and references is off.	3 / 5
	Total	11 / 20 Passed

Description

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

This description is too vague to effectively guide skill selection. It identifies the domain (game development) and its role (orchestrator/router) but fails to specify what platforms it supports, what concrete actions it performs, or when it should be triggered. Without a 'Use when...' clause and without naming specific platforms or game development scenarios, Claude would struggle to reliably select this skill.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g., 'Use when the user wants to start a game project, mentions game engines like Unity, Godot, or Unreal, or needs help choosing a game development platform.'

List the specific platforms and skills it routes to, e.g., 'Routes game development tasks to Unity, Godot, Unreal Engine, or web-based game skills based on project requirements.'

Include natural trigger terms users would say, such as 'game', 'game engine', '2D game', '3D game', 'game project', and specific engine names.

Dimension	Reasoning	Score
Specificity	Names the domain ('game development') and mentions routing/orchestration, but provides no concrete actions beyond vague 'routes to platform-specific skills.' No specifics about what platforms, what types of routing decisions, or what game development tasks are supported.	2 / 5
Completeness	The 'what' is vaguely stated as routing to platform-specific skills, but there is no 'when' clause or explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3, and the 'what' itself is too vague to reach that cap.	2 / 5
Trigger Term Quality	'Game development' is a relevant keyword, but it's the only natural term present. Missing common variations like 'game', 'game engine', 'Unity', 'Godot', 'Unreal', 'game project', or any platform-specific terms that users would naturally mention.	2 / 5
Distinctiveness Conflict Risk	'Game development orchestrator' is somewhat specific as a meta-routing skill, but 'routes to platform-specific skills based on project needs' is vague enough that it could overlap with any project-routing or orchestration skill. The game development focus provides some distinction.	3 / 5
	Total	9 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/game-development/SKILL.md
Commit: 57c135b

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.