cli-hub-matrix-game-development

Capability-based multi-tool matrix for game development: engine, 3D/2D/audio assets, AI-generated assets, agent playtesting, packaging, store publishing, and telemetry.

Quality

67%

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 ./cli-hub-matrix/game-development/SKILL.md

Quality

Content

68%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 an efficient, actionable capability matrix with concrete commands and well-structured sections, but it reads more as a reference catalog than a sequenced workflow — the recipes are one-liners and validation feedback loops are absent. Progressive disclosure is good with one-level-deep external references.

Suggestions

Turn the recipes into short numbered workflows with explicit validation checkpoints (e.g. preflight → build into builds/<version>/ with manifest → validate export → gate publish behind user confirmation → ship telemetry), especially for the destructive publish.store path.

Resolve or remove the placeholder Unity/Unreal engine rows, or explicitly state the gap inline so Claude does not treat them as available providers.

Trim the cryptic 'Scenario S4 / v2 capability-based' framing and de-duplicate the known-gap notes (keep only the consolidated 'Known gaps' section) to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly tables/terse bullets that assume Claude's competence with little padding, but the cryptic 'Scenario S4 / v2 capability-based' framing and duplicated known-gap notes (the per-capability 'Known gap' plus the 'Known gaps' section) could be trimmed, keeping it just below the lean 5-anchor.	4 / 5
Actionability	Provides executable commands (install/preflight invocations, an importlib/env-var probe block, a concrete suggest-to-user template) and provider tables with Requires/Cost/Quality, but placeholder rows (Unity/Unreal all '—') and 'See S3 matrix' pointers to absent docs leave minor gaps.	4 / 5
Workflow Clarity	There is a rough sequence (Install → Preflight → Provider selection) and an explicit publish-gating checkpoint, but the end-to-end build→publish→telemetry flow is not laid out as a numbered, checkpointed workflow and the recipes are vague one-line capability lists rather than steps with validation feedback loops.	3 / 5
Progressive Disclosure	Content is well-organized under clear section headers with one-level-deep, clearly signaled external doc links (matrix_registry.schema.md, cli-matrix-plan.md) and no bundle nesting, though a few inline 'See S3 matrix' references lack explicit paths and the large capability tables are inlined rather than split out.	4 / 5
	Total	15 / 20 Passed

Description

66%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 communicates a comprehensive game-development capability matrix but omits any explicit 'when to use this' trigger guidance, which caps completeness. It is specific and largely distinct, with solid but not exhaustive natural keyword coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when developing or publishing a game — engines, game assets, AI-generated art/audio, agent playtesting, packaging, or store publishing (Steam/itch/console).'

Surface the natural product/brand terms users actually say (Steam, itch.io, Godot, Unity, Unreal) to improve trigger-term coverage and distinctiveness.

Reframe capability nouns as concrete actions (e.g. 'Author games, generate 3D/2D/audio assets, agent-playtest, package, and publish to stores') to push specificity toward the top anchor.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete capability areas ("engine, 3D/2D/audio assets, AI-generated assets, agent playtesting, packaging, store publishing, and telemetry") for comprehensive coverage, but uses noun-form capability labels rather than concrete action verbs like the 5-anchor examples, so it sits just below the top.	4 / 5
Completeness	The 'what' is clear and comprehensive ("Capability-based multi-tool matrix for game development" plus the capability list), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms a game-dev user would say ("game development", "assets", "agent playtesting", "packaging", "store publishing", "telemetry") with good coverage, but misses common synonyms and concrete markers users actually name (e.g. Steam, itch.io, Godot, Unity, Unreal, file extensions).	4 / 5
Distinctiveness Conflict Risk	Game development is a clear, mostly distinct niche with specific triggers, but the broad asset/AI-asset/telemetry scope creates minor overlap risk with general asset-creation skills (e.g. the S3 photogrammetry matrix).	4 / 5
	Total	15 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: HKUDS/CLI-Anything
Path: cli-hub-matrix/game-development/SKILL.md
Commit: 34f5195

Reviewed: 1 day 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.