Build a game's own dashboard

Every game needs different numbers. A mobile game cares whether players come back, which mode they pick and whether the paywall turns into purchases; a puzzle game, how long a puzzle takes and how often hints are used; a platformer or shooter, where players die and whether frames hold up in a fight. Glitchless doesn't guess: you add the collectors this game needs, and design its dashboard from them: its own pages, in its own words. The developer then sees it in Glitchless, and you can read the same data back over MCP to debug.

Before this skill, the game should already send data (the glitchless-setup skill). If it doesn't, do that first.

1. Find out what they want to know

Write down three to eight questions, in the developer's words. Ask if they haven't said; read the game to suggest some (menus, modes, shops, level lists, settings, anything with a counter). Good questions are about decisions: "Do players finish the tutorial?", "Which mode do they play?", "Does the paywall convert?", "Which stage is too hard?", "Does it stutter on phones?". Leave out what nobody would act on.

2. Pick a collector for each question