balance-check

Analyzes game combat, economy, progression and loot balance data to identify outliers and recommend fixes.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill balance-check-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: balance-check
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/balance-check
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill balance-check-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the detection of balance problems in game systems so designers can quickly find outliers, broken progressions, degenerate strategies, and economy imbalances after data or design changes.

Core Features & Use Cases

  • Multi-domain analysis: Evaluates combat (DPS, time-to-kill), economy (faucets, sinks, infinite loops), progression (XP/power curves), and loot (rarity, pity timers, acquisition rates).
  • Design-aware checks: Reads design documents and balance configuration files to compare intended targets against actual values and surfaces deviations with prioritized recommendations.
  • Use Case: Run a balance audit after tuning a weapon or changing gold rewards to find dominating options, broken pacing, or runaway inflation before pushing changes live.

Quick Start

Run a balance-check on the combat system by pointing the skill at the relevant data file or saying "balance report" for the system you want analyzed.

Frequently Asked Questions about balance-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find broken progression curves and economy imbalances in game design data?

Game balance analysis detects broken progressions and economy imbalances by reading configuration files and design documents to compare intended targets against actual values, surfacing deviations with prioritized recommendations.

What is the best way to calculate DPS and time-to-kill outliers after tuning weapon stats?

Calculating DPS and time-to-kill outliers involves reading combat balance tables to identify dominating options and pacing issues, applying a fix-and-verify workflow to ensure changes resolve the deviations before going live.

How do I detect infinite resource loops and verify pity-timer math in loot configuration files?

Detecting infinite resource loops and verifying pity-timer math requires analyzing economy faucets, sinks, and loot acquisition rates within configuration files to identify degenerate strategies and runaway inflation.

Can I audit multiple game systems like combat, progression, and loot simultaneously using balance tables?

Multi-domain analysis allows you to audit combat, economy, progression, and loot systems simultaneously by evaluating balance tables and configuration files to detect pricing, pacing, and dominance issues across all domains.

Does game balance analysis work without importing external dependencies or framework components?

Game balance analysis operates independently without external dependencies or components, reading local balance tables, configuration files, and GDDs directly to calculate progression curves and generate prioritized fix recommendations.

When should I run a balance audit on my game's progression and economy systems?

You should run a balance audit after tuning a weapon, changing gold rewards, or modifying data configurations to catch dominating options, broken pacing, or runaway inflation before pushing changes live.