LiveOps Event Calendar Skill

The first LiveOps calendar I ever built was a spreadsheet of events that sounded fun. Tournaments, sales, themed weekends.

It moved nothing. None of it was tied to a retention leak I could name.

I've watched the same pattern from other teams since. Four events ship in a quarter. D30 moves by half a percent. Wrong segment. Wrong lifecycle moment. Right execution.

It took a few years to flip the order. Diagnose the leak. Pick the segment. Pick the lifecycle moment. Pick the objective. Calendar last.

I encoded that into a Skill. Works on Claude, ChatGPT, and Gemini.

Inputs: • Genre and core loop • Segments by spend • D1, D7, D30 (exact numbers) • Recent events • 4-week capacity

Outputs: • Diagnosis of the retention leak • Primary segment for the calendar • 4-week event table with defence notes • Defence checks tied back to the diagnosis • Honest note on what the calendar does not solve

Refuses to produce a calendar without retention data. Refuses "general engagement" as an objective.

Comment LIVEOPS and I'll DM you the GitHub link.

What's a LiveOps decision you wish someone had pushed back on before you shipped it?

Hashtags

#LiveOps #MobileGaming #GameProduction #AITools #PlayerRetention

Related Posts

• 2026-05-12 Bias for Action.md