puzzle-iaa-analytics

CRITICAL - This skill orchestrates a multi-step analysis pipeline. Read each step file in references/steps/ before executing. Do not skip steps or fabricate data. CRITICAL - Step 01 is a mandatory gate. All config values MUST be explicitly confirmed by the user via numbered text replies. data_inventory.json MUST NOT be written until 1.8 Summary Confirmation. Step 01 not confirmed → MUST NOT proceed to Steps 02-06. CRITICAL - Use ae-cli exclusively for all data operations. Read references/adapters/ae-cli.md for command patterns. Use ae-cli analysis adhoc run (unified) for all ad-hoc analysis — no separate builder step. Never guess command names, flags, JSON payloads, project_id, event names, property names, or parameter formats. CRITICAL - The references/config/project_mapping.md file is the sole bridge between business concepts and database fields. {{event.xxx}} and {{prop.xxx}} are business concept placeholders, NOT actual database field names. When switching projects, only modify this file. CRITICAL - SKILL.md and references body MUST NEVER reference references/adapters/. Tool knowledge lives only in the adapter layer and does not pollute methodology.

When to Use

Use puzzle-iaa-analytics for IAA puzzle/casual game post-launch data review:

• Post-launch version review: identify core issues in retention, monetization, and level experience
• Provide data-driven priority recommendations for the next version
• Applicable to pure IAA (ad-monetized) puzzle/casual games

If user intent is raw ad-hoc analysis, single-metric queries, or non-game analytics, do NOT use this skill — use ae-analysis directly.

Global Conventions