game-development

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

Quality

71%

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 ./.agents/skills/game-development/SKILL.md

Quality

Content

85%

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

The content is a tightly organized orchestrator body: lean table-driven guidance with a clear routing workflow and well-signaled one-level-deep sub-skill references. Its main weakness is illustrative pseudocode instead of executable examples.

Suggestions

Replace the pseudocode blocks (game loop, input mapping) with minimal executable snippets for at least one engine, or explicitly justify the abstract form.

Add a short 'validation checkpoint' to the routing examples (e.g. confirm the chosen sub-skill's prerequisites before proceeding) to harden the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven with no padding explaining what game engines or patterns are; almost every token earns its place, matching the score-3 'lean and efficient' anchor.	3 / 3
Actionability	The selection matrices (pattern, AI, collision, ms performance budget) and routing examples are concrete, but the code blocks are illustrative pseudocode ('INPUT -> Read player actions', '"jump" -> Space') rather than executable code, which the rubric penalizes.	2 / 3
Workflow Clarity	The routing workflow is unambiguous and clearly sequenced ('If the game targets... Use Sub-Skill' tables plus arrow-stepped examples), and the reference material is well-organized; this is a clear sequenced decision process.	3 / 3
Progressive Disclosure	Sub-skills are referenced one level deep and clearly signaled via routing tables (e.g. `game-development/web-games`), with no nested/2+-level reference chains and content appropriately organized for discovery.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 clearly identifies the game-development niche and its orchestration role, but it is thin on multiple specific actions and omits an explicit 'Use when' trigger, leaving it mid-range on completeness and trigger coverage.

Suggestions

Add concrete platform actions to the description, e.g. 'Routes Unity, Godot, Unreal, and Phaser projects to platform-specific sub-skills for rendering, networking, and asset pipelines.'

Append an explicit trigger clause such as 'Use when building or debugging games with any game engine.'

Include natural engine name keywords (Unity, Godot, Unreal, Phaser) directly in the description rather than only in when_to_use.

Dimension	Reasoning	Score
Specificity	It names the domain ('Game development') and a concrete action ('Routes to platform-specific skills') but lists only a single action rather than multiple specific capabilities, so it sits below the score-3 anchor.	2 / 3
Completeness	It answers 'what' (orchestrator that routes to sub-skills) but has no explicit 'Use when...' trigger clause in the description field, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	'Game development' is a natural keyword, but the description lacks the engine variations (Unity, Godot, Unreal) that users would actually say; those appear only in when_to_use, giving partial coverage.	2 / 3
Distinctiveness Conflict Risk	'Game development orchestrator' is a clear niche with domain-bound triggers that are unlikely to fire for non-game skills, matching the score-3 anchor.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
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	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/game-development/SKILL.md
Commit: 04514f0

Reviewed: about 13 hours 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.