CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

balance-check

Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data. 'Check game balance'.

Quality

79%

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/balance-check/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

A thoroughly actionable, well-sequenced analysis workflow with strong validation checkpoints and a genuine fix-verify feedback loop. Its one real weakness is token efficiency: the no-data preamble over-explains rules its own numbered steps already state.

Suggestions

Condense the 'Insufficient input' section to the numbered FOUND/ABSENT procedure plus one line of rationale; cut the other-skill failure anecdotes and the 'Absence of evidence' paragraph, which restate steps 3-4.

Specify how to 'Plot the XP curve and power curve' (e.g., a table in the report vs. an actual plot) since the Progression Analysis output medium is left ambiguous.

Give a worked DPS or time-to-kill formula convention so 'Calculate DPS for all weapons/abilities' has a concrete starting point.

DimensionReasoningScore

Conciseness

The 'Insufficient input' section pads its numbered procedure with rationale paragraphs ('A verdict of NOT ASSESSED is a success', 'Absence of evidence is never evidence of absence') and anecdotes about other skills' failure modes ('an asset audit returning COMPLIANT', '>99% headroom'), while the phase sections themselves are lean.

3 / 5

Actionability

Provides copy-paste-ready specifics — the Grep invocation with flags, exact paths ('assets/data/', 'design/registry/entities.yaml'), a worked outlier row ('player_damage_base 140 against 90-110'), and exact AskUserQuestion options and save-file naming — but leaves 'Plot the XP curve and power curve' without a method.

4 / 5

Workflow Clarity

Six ordered phases with an explicit pre-flight FOUND/ABSENT check, section-level 'NOT ASSESSED — NO DATA' stop rules, a worst-finding Health Summary rule ('first match wins'), and a fix-then-reverify feedback loop ('re-run the relevant balance checks to verify no new outliers were introduced') — explicit validation and error recovery are both present.

5 / 5

Progressive Disclosure

Well-organized single-file structure with phase headers, a complete report template, and no nested references; the four domain checklists are compact enough to live inline, though the ~195-line body (exceeding the simple-skill range) could shed the long insufficiency section to a reference file.

4 / 5

Total

16

/

20

Passed

Description

78%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.

A specific, distinct description with a concrete quoted trigger; it sits comfortably above the generic-skill baseline. Its main limits are a single narrow when-clause and missing natural synonyms for balance complaints.

Suggestions

Broaden the when-clause beyond the single quoted phrase, e.g. "Use when checking game balance, tuning weapons, economy, XP curves, or loot tables".

Add natural synonyms users would actually say (e.g. 'overpowered', 'too grindy', 'DPS check', 'tuning pass') to improve trigger-term coverage.

Mention the fix-and-verify cycle or report output in the capability clause so the description covers what the skill actually does end-to-end.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Find balance outliers, broken progressions, degenerate strategies, economy imbalances in formulas and data' — but all four are variations of 'find problems' and omit the fix/verify and report-save halves of the skill, leaving minor coverage gaps.

4 / 5

Completeness

The 'what' is explicit ('Find balance outliers... in formulas and data') and the 'when' is present as the concrete trigger 'Check game balance', so it is not capped at 3; however the when-clause is a single narrow phrase rather than the multi-condition trigger set of the top anchor.

4 / 5

Trigger Term Quality

The quoted 'Check game balance' is an exact natural trigger phrase and 'balance outliers'/'economy imbalances' are terms a game designer would say, but common variations like 'overpowered', 'too grindy', or 'tuning' are missing.

4 / 5

Distinctiveness Conflict Risk

'Degenerate strategies' and the trigger 'Check game balance' carve a clear game-balance niche with a distinct trigger phrase and minimal overlap with non-game skills; it clearly matches the clear-niche anchor rather than the minor-overlap anchor below it.

5 / 5

Total

17

/

20

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.

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

Path

.claude/skills/balance-check/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.