balance-check

Analyze game balance data files against design documents to detect outliers and imbalances.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill balance-check-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: balance-check
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/balance-check
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill balance-check-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies broken or imbalanced game economy, progression, loot, or combat tuning so you can catch outliers, degenerate strategies, and economy disruptions after any changes.

Core Features & Use Cases

  • Balance domain identification: Determines whether the check should focus on Combat, Economy, Progression, or Loot based on the provided system argument or file contents.
  • Design-grounded analysis: Reads balance-related data files and the corresponding GDD to compare actual values against intended targets and expected ranges.
  • Actionable reporting and fixes: Produces a structured health summary, outliers, degenerate strategies, and prioritized recommendations, then guides an iterative fix-and-verify cycle.

Example use case: After adjusting weapon stats, XP curves, resource faucets/sinks, or loot rarity tables, run a balance report to confirm the economy doesn’t generate infinite loops, progression doesn’t create dead zones or power spikes, and no single strategy strictly dominates.

Quick Start

Run the balance-check skill for your target system by providing the system name or the path to the relevant balance data file.

Frequently Asked Questions about balance-check

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

FAQPage Schema
How do I detect broken game progression curves and economy imbalances from design data?

Game balance analysis detects broken progression curves and economy imbalances by reading configuration files and design documents to identify outliers, degenerate strategies, and disrupted resource loops before they ship.

What is the best way to validate combat DPS and time-to-kill tuning after adjusting weapon stats?

Validating combat tuning after weapon adjustments requires running a balance check that compares actual DPS and time-to-kill values against intended targets to catch degenerate strategies and strict dominance issues.

How do I check loot probability tables for broken rarity distributions and infinite resource loops?

Checking loot probability tables involves analyzing rarity configurations against design goals to detect infinite resource loops and economy disruptions caused by faucet and sink imbalances.

Can I use a balance check for game economy analysis on configuration files without a full design document?

Balance checks require reading relevant data from asset files and balance design documents from the GDD to compare actual values against intended targets and expected ranges for accurate analysis.

When do I need to run a game balance validation report during the development workflow?

Game balance validation is needed after making balance-related changes to weapon stats, XP curves, resource faucets, or loot tables to confirm progression has no dead zones and no strategy strictly dominates.