CtrlK
BlogDocsLog inGet started
Tessl Logo

game-development

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

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/game-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is a lean, table-driven reference that assumes Claude's competence and provides concrete decision matrices plus clear routing examples; it lacks executable code and explicit validation checkpoints but neither is strictly required for this orchestrator-style skill.

DimensionReasoningScore

Conciseness

The body is table-driven and dense, assuming Claude knows terms like ECS, AABB, quadtree, and GOAP; only light explanatory prose ('Every game... follows this pattern') keeps it from a 5.

4 / 5

Actionability

Concrete decision matrices (pattern selection, AI by complexity, collision strategy) and explicit routing examples give actionable guidance; the code blocks are conceptual diagrams rather than executable code, but as an instruction-only orchestrator that is acceptable with minor gaps.

4 / 5

Workflow Clarity

Routing Examples 1-3 lay out a clear sequenced workflow (start with platform sub-skill, then dimension, then specialty), and no destructive/batch operations are present so the validation cap does not apply; only minor explicit-checkpoint gaps remain.

4 / 5

Progressive Disclosure

Sections are well-organized and routing to one-level-deep sub-skills is clearly signaled; no bundle files exist to verify, and the self-contained content is appropriately structured with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%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.

The description clearly identifies the skill as a game-development orchestrator with a routing function, but it leans on the separate when_to_use field for triggers and lists only one action, leaving completeness and trigger coverage mid-range.

Suggestions

Fold the concrete trigger terms from when_to_use (Unity, Godot, Unreal, Phaser, game engine) into the description so natural user keywords appear in the scored field.

Add a brief 'Use when...' clause directly in the description to satisfy both 'what' and 'when' in one field.

Name one or two more concrete actions (e.g., 'selects patterns, budgets performance, routes to sub-skills') to lift specificity from 3 to 4-5.

DimensionReasoningScore

Specificity

Names the domain ('Game development') and one concrete action ('Routes to platform-specific skills based on project needs'), but offers only a single routing action rather than a comprehensive list of capabilities.

3 / 5

Completeness

It states clearly what the skill does ('orchestrator... routes to platform-specific skills') but the 'when' trigger is absent from the description; the when_to_use field carries that burden instead.

3 / 5

Trigger Term Quality

'Game development' and 'platform-specific' are relevant, but the description omits the natural terms users say (Unity, Godot, Unreal, game engine) which only appear in when_to_use, not in the description field itself.

3 / 5

Distinctiveness Conflict Risk

'Game development orchestrator' with explicit platform routing is a clear niche with minimal overlap against other skills, though the bare term 'game development' is moderately broad.

4 / 5

Total

13

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.