Skip to content

Team Live Ops Planner

Plans a game season or live event by coordinating a set of simulated game-design, economy, analytics and writing roles

Stars
32,965
Licence
MIT
Files
1 file

What it does

Once installed, when you ask the agent to plan a game season or live event, it follows a structured pipeline: it sets up a team-style workflow where one role covers season structure and retention, another covers in-game economy and pricing, and others cover success metrics, player announcements, narrative theme and copy. It asks you to pick among proposals at each stage and writes its outputs to files. It does not run code itself beyond reading a config helper, and the amount of team involvement depends on a team size setting.

Great for

  • Game designers planning a seasonal battle pass or live event
  • Live-ops teams wanting a checklist-driven planning process for a season
  • Indie developers who want structured event and economy planning prompts

Skip it if

  • Anyone expecting real analytics or live game data: the skill only writes plans and specs, it does not connect to your game or metrics systems
  • Non-game projects, since it is tuned to game live operations and economy terms

Try asking

  • “/team-live-ops Winter Frost season --review lean”
  • “/team-live-ops A two-week double-XP spring event for our mobile puzzle game”
  • “Plan the battle pass structure and currency pricing for our summer season”
Step-by-step guide: how to use Team Live Ops PlannerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 1 original files, the MIT licence and an attribution note.

    team-live-ops.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip team-live-ops.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip team-live-ops.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give a specific season name or event description, since the skill stops with a usage message if no argument is provided.
  • Choose a team size and review depth up front (individual, small or studio; lean, full or solo) to control how many sub-agents run and token use.
  • Review each proposal at the decision prompts, since outputs are drafts that need game-specific balancing and real data checks.

What's inside

  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.