game-economy-inspection

CRITICAL - This skill orchestrates a multi-step inspection pipeline. Read each step file in references/steps/ before executing. Do not skip steps or fabricate data. CRITICAL - Step 00 and Step 01 are both mandatory gates. All uncertain values (timezone, event names, property names, distinguishing properties, thresholds, scenarios, time window) MUST be explicitly confirmed by the user via numbered text replies — never assume them. Step 00 not confirmed → MUST NOT proceed to Step 01; Step 01 not confirmed → MUST NOT proceed to Steps 02-05. CRITICAL - Use ae-cli for all data operations. Read references/adapters/ae-cli.md for command patterns. Never guess command names, flags, JSON payloads, project_id, event names, property names, or parameter formats. CRITICAL - references/config/project_mapping.md is the sole bridge between business concepts and database fields. {{event.xxx}} and {{prop.xxx}} are business concept placeholders, NOT actual field names. When switching projects, only modify this file. CRITICAL - Treat references/adapters/ae-cli.md as the source of truth for command syntax. Keep methodology and metric definitions tool-agnostic.

When to Use

Use game-economy-inspection for proactive health inspection of game economy ecosystems:

• Check whether cross-domain structures are gradually degrading even though macro economy totals still look normal
• Inspect whether nurturing currency is silently devaluing (evolution stones, spirit fragments, and other nurturing resources)
• Detect equipment recycle anomalies, material accumulation, and other economy-loop issues
• Detect hero/lineup meta imbalance and narrowing consumption outlets
• Run cross-domain correlation inspection on "multi-domain, gradual, single-metric-silent" ecosystem problems

Boundary with game-economy-balance