CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

map-systems

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

Quality

71%

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

Quality

Content

77%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 exemplary orchestration workflow: concrete prompts, exact paths, and explicit validation/feedback loops at every phase make it highly actionable and clear. Its weaknesses are repetition — the review-mode and gate-response boilerplate restated three times — and inlined meta-detail that should live in reference files.

Suggestions

Factor the repeated review-mode check and NOT ASSESSED handling into a single stated rule (e.g. one "Gate protocol" section referenced by each phase) to cut ~30 lines of duplication.

Move the docs.density exposition and the systems-index table-column contract blockquote into a short reference file (e.g. references/index-contract.md) and link to it from the body.

Tighten the Phase 4 reasoning-style guidance by keeping one worked example instead of three parallel quote-patterns plus the bracket caveat.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the review-mode check ("solo → skip... lean → skip... full → spawn") and the NOT ASSESSED gate-response protocol are each repeated nearly verbatim three times, and the opening docs.density exposition is dense meta-explanation — more than the "minor instances" of anchor 4.

3 / 5

Actionability

Provides copy-paste-ready AskUserQuestion prompts, a verbatim failure message ("No game concept found. Run /brainstorm first..."), concrete inference lists ("'Inventory' implies: item database, equipment slots, weight/capacity rules..."), exact file paths, verdicts, and session-state fields — fully executable guidance covering common cases.

5 / 5

Workflow Clarity

Phases 1–7 are clearly sequenced with lettered steps, explicit user-approval checkpoints at every phase, and true feedback loops (REJECT → revise and re-run the gate; NOT ASSESSED → supply the missing input and re-run), matching anchor 5's explicit-validation-and-recovery pattern.

5 / 5

Progressive Disclosure

Pointers to external docs are clearly signaled and one level deep ("the spawned agent reads its own gate file; do not read it in the parent session"), but no reference files exist in the bundle and substantial detail that belongs in separate files is inlined — the docs.density exposition, the table-column contract blockquote, and the repeated gate boilerplate.

3 / 5

Total

16

/

20

Passed

Description

55%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 lists several concrete actions covering the full workflow, but it omits any "when to use" trigger guidance and never mentions the game-design domain it serves. This weakens both completeness and natural trigger-term coverage, and leaves it open to collision with non-game "system design" requests.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to break a game concept into systems, map system dependencies, or plan GDD design order."

Name the domain in the first sentence ("Decompose a game concept into individual systems...") so game-design requests match and software-architecture requests don't.

Include natural user phrasings such as "game systems", "what systems does my game need", and "systems index" as trigger terms.

DimensionReasoningScore

Specificity

Names four concrete actions ("Decompose a concept into individual systems, map dependencies, prioritize design order, create the systems index"), but never names the domain (game design), leaving "concept" and "systems" abstract — a minor coverage gap that fits anchor 4 better than 5.

4 / 5

Completeness

The "what" is clear and multi-action, but there is no "Use when..." clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords exist ("systems", "dependencies", "decompose", "design order") but the most natural user terms — "game", "game design", "break down" — are missing, matching anchor 3 (some relevant keywords, missing common variations) rather than 4.

3 / 5

Distinctiveness Conflict Risk

"Decompose a concept into individual systems" could overlap with software architecture or general planning skills, though "systems index" and "design order" give it some niche vocabulary — anchor 3 (somewhat specific but could still overlap).

3 / 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.

Validation — 14 / 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

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/map-systems/SKILL.md

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.