CtrlK
BlogDocsLog inGet started
Tessl Logo

game-development

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

57

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/game-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is a well-structured, lean orchestrator overview: concise tables, concrete decision matrices, clear routing sequences, and clean one-level-deep navigation to sub-skills. Its only gap is illustrative rather than executable code blocks.

DimensionReasoningScore

Conciseness

The body is table-driven and lean, assuming Claude's competence without textbook padding; only minor explanatory labels like 'INPUT → Read player actions' could be trimmed.

4 / 5

Actionability

Concrete decision matrices (pattern, performance budget in ms, collision types) with explicit decision rules and copy-paste-ready sub-skill routing paths provide actionable guidance, though the code blocks are illustrative diagrams rather than executable code.

4 / 5

Workflow Clarity

The 'Routing Examples' lay out clear ordered sequences across sub-skills; no destructive or batch operations are present, so the missing-validation cap does not apply, but there are no explicit validation checkpoints either.

4 / 5

Progressive Disclosure

With no bundle files present, the body functions as a concise single-level overview that routes outward via clearly signaled sub-skill tables, satisfying the simple-skill well-organization criterion.

5 / 5

Total

17

/

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, giving it a distinct niche. It is held back by a single generic action verb, missing trigger-term variations, and the absence of an explicit 'Use when...' clause.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when starting or structuring a game project across web, mobile, PC, or VR/AR platforms.'

Expand the action beyond a single generic verb by listing 2-3 concrete routing actions, e.g. 'Routes to platform, dimension, and specialty sub-skills and supplies core game-loop, pattern, and performance guidance.'

Include natural trigger synonyms users say, such as '2D/3D game', 'game design', or specific platform names, to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Game development orchestrator') and one concrete action ('Routes to platform-specific skills'), but does not enumerate multiple specific actions for comprehensive coverage.

3 / 5

Completeness

It states a clear 'what' (orchestrator that routes) but the 'when' is only weakly implied ('based on project needs') with no explicit 'Use when...' clause, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'Game development' is a natural user term, but common variations and synonyms (game design, 2D/3D, specific platforms) are absent, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The game-development-orchestrator niche is mostly distinct with minimal conflict risk, though 'based on project needs' is slightly broad and could overlap with a generic project-orchestrator skill.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.