CtrlK
BlogDocsLog inGet started
Tessl Logo

balance-check

Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.

76

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A well-structured, actionable, and concise workflow with a real verification loop. The only meaningful gap is progressive disclosure: the multi-domain checklists and report template are all inline in a single long file rather than split into clearly signaled reference files.

Suggestions

Move the four domain-specific checklists (Combat/Economy/Progression/Loot) into one-level-deep reference files (e.g. references/combat-balance.md) and link them from a lean Phase 4 overview, so the core SKILL.md stays a concise routing document.

Extract the Phase 5 report template into references/balance-report-template.md and reference it by link to reduce inline bulk.

Consider splitting the Phase 6 fix-and-verify cycle into its own reference once the per-domain files are pulled out, preserving the verify-loop guidance while shortening the main body.

DimensionReasoningScore

Conciseness

Lean, phase-based instruction that assumes Claude's competence; it does not re-explain what game balance or DPS is, and nearly every line is actionable rather than padding.

3 / 3

Actionability

Concrete per-domain checks ('Calculate DPS for all weapons/abilities at each power tier', 'Map all resource faucets and sinks'), an exact report template, and literal AskUserQuestion prompts/options/file paths give copy-ready guidance for an instruction skill.

3 / 3

Workflow Clarity

A clearly sequenced 6-phase process with an explicit fix→re-run→verify feedback loop in Phase 6 ('offer to re-run the relevant balance checks to verify no new outliers were introduced').

3 / 3

Progressive Disclosure

The ~110-line body inlines four full domain checklists (Combat/Economy/Progression/Loot) plus a complete report template that could be split into one-level-deep reference files; no references signal deeper, optional material. Not a level-3 'appropriately split' structure, but better than a monolithic wall, so above a 1.

2 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete analytical capabilities, gives explicit natural-language triggers, and answers both 'what' and 'when' in third person without padding. No significant weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'identify outliers, broken progressions, degenerate strategies, and economy imbalances' — rather than vague language, matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what ('Analyzes game balance data files, formulas, and configuration…') and when ('Use after modifying any balance-related data or design. Use when user says…') with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural user phrases ('balance report', 'check game balance', 'run a balance check') that a user would actually say, with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear game-balance niche with distinct triggers unlikely to fire for unrelated skills; no overlap with generic analysis skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository
Donchitos/Claude-Code-Game-Studios
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.