map-systems

Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.

Quality

72%

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 ./.claude/skills/map-systems/SKILL.md

Quality

Content

77%

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

The content is highly actionable with a clear, well-validated multi-phase workflow, but it is a monolithic document with repeated boilerplate and references that are not clearly organized into one-level-deep progressive disclosure.

Suggestions

Factor the repeated review-mode boilerplate into a single shared section and reference it from each phase to cut duplication.

Split the gate-check / director-gates detail into a referenced file with a clearly signaled 'See ... for ...' navigation section, rather than re-explaining it inline.

Move the long implicit-systems inference pattern (Phase 2b) into a reference file so the main body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient procedural guidance that assumes Claude's competence, but the review-mode boilerplate is repeated verbatim across Phases 3, 4, and 5, and the gate-check option is re-explained in Phase 7, so it could be tightened rather than fully lean.	2 / 3
Actionability	Concrete file paths, exact AskUserQuestion prompts, named skills/commands to invoke, and a ready-to-use fail message make the guidance copy-paste ready, matching the fully executable/specific anchor.	3 / 3
Workflow Clarity	A clear seven-phase sequence includes explicit validation checkpoints — a fail-if-missing gate, per-phase approval via AskUserQuestion, review-mode checks, gate spawns, and 'Wait for approval. Write only after yes' — providing feedback loops for the fragile batch operations.	3 / 3
Progressive Disclosure	The ~355-line SKILL.md is a single monolithic document; references to director-gates.md, templates, and session-state are one-line inline mentions rather than clearly signaled, organized reference sections, so structure exists but progressive disclosure is not fully realized.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 is specific and well-differentiated with concrete actions, but it omits any 'Use when...' trigger guidance and relies on somewhat technical phrasing that users would not naturally say, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when breaking down a game concept into systems, planning systems architecture, or deciding design order.'

Surface natural user phrasings such as 'game design', 'break down my game', or 'plan my systems' alongside the technical terms.

Mention the systems-index output artifact explicitly so the trigger maps to a recognizable deliverable.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index' — matching the anchor for multiple specific concrete actions rather than the partial coverage at level 2.	3 / 3
Completeness	It clearly answers 'what does this do' but lacks any 'Use when...' trigger guidance for 'when', and per the guidelines a missing explicit trigger clause caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Domain keywords like 'game concept', 'systems', and 'dependencies' are relevant, but a user would not naturally say 'decompose a game concept'; common variations like 'game design', 'break down my game', or 'systems index' phrasings are missing, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The systems-decomposition niche is clearly distinct from sibling skills like /design-system, with triggers tied to game concept decomposition that are unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	10 / 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: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/map-systems/SKILL.md
Commit: 984023d

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.