How to use the Team Live Ops Planner agent skill

What is an agent skill and what does team-live-ops do?

An agent skill is a folder containing a SKILL.md file. The file tells an AI agent when to use the skill and how to work through a task. Claude Code loads the skill and follows its instructions when you ask for the matching kind of work.

The team-live-ops skill is written for planning a season or live event. Its description says it orchestrates the live-ops team: live-ops-designer, economy-designer, analytics-engineer, community-manager and writer. The skill moves through phases, and at each phase transition it asks you to choose among the proposals from the relevant team member before continuing.

The outputs are plans and specs written to files. The skill does not connect to your game or to any metrics system, so it does not pull real player data.

• live-ops-designer: season structure, event cadence, retention mechanics, battle pass
• economy-designer: live economy balance, store rotation, currency pricing, pity timers
• analytics-engineer: success metrics, A/B test design, event tracking, dashboard specs
• community-manager: player-facing announcements and seasonal messaging
• narrative-director: seasonal narrative theme and story arc
• writer: event descriptions, reward item names, announcement copy

How do you install the team-live-ops skill?

Download the ZIP from the skill's page on this directory and unzip it. You can install it in one of two places. For a personal install that works in every project, put the unzipped skill folder under ~/.claude/skills/. For a project-only install, put it under the project's .claude/skills/ folder.

You can also upload the skill through the Claude apps. Open Settings, go to Capabilities, then choose Skills and upload the ZIP there.

The skill's source file is SKILL.md. Its folder name must be team-live-ops so the skill name matches.

• Personal install: ~/.claude/skills/team-live-ops/
• Project install: .claude/skills/team-live-ops/ inside your project
• Claude apps: Settings, then Capabilities, then Skills, then upload the ZIP

How do you trigger the skill with a request?

The skill is user-invocable and takes an argument. The argument is the season name or an event description, with an optional review flag: /team-live-ops [season name or event description] [--review full|lean|solo]. The flag sets how deep review goes; the file says --review overrides the review_mode setting in config.

If you run it with no season name or event description, the skill prints a usage message and stops without spawning any agents or reading any files. Give it a clear name or a one-line description of the event.

Natural requests also work when the agent matches your request to the skill. Name the season or event and say you want it planned, for example: plan the spring battle pass season with a two-week limited-time event.

• Example: /team-live-ops Summer Harvest season --review lean
• Example: /team-live-ops Winter lantern festival event, 10-day limited-time event with a shop
• Example request: Plan the autumn battle pass season for our mobile RPG

What does the pipeline do and where do the files go?

The skill first resolves its config using a helper script. The team.size setting decides which agents are active. At the default, individual, only live-ops-designer and economy-designer are spawned, and other roles are consulted through them. Small adds analytics-engineer and community-manager. Studio adds writer and narrative-director. Before spawning anything, the skill states which agents will run and which will not.

Each agent writes its full output to its own working file under production/live-ops/ in a folder named after the season, so parallel steps do not overwrite each other. The final documents under design/live-ops/seasons/ are compiled from these drafts.

The automation setting controls how decisions pass. In collaborative mode you approve each phase before the next one. In guided mode the pipeline advances on its own unless a phase is blocked. In autonomous mode it runs end to end and logs each phase outcome.

• individual (default): live-ops-designer and economy-designer
• small: adds analytics-engineer and community-manager
• studio: adds writer and narrative-director
• Working drafts: production/live-ops/[season-slug]/
• Final documents: design/live-ops/seasons/

What does the skill need, and what are the safety notes?

The skill needs Claude Code or a compatible SKILL.md agent. It also needs Bash for the config helper, hooks/yaml-helper.sh, which lives in the wider repository, not inside this skill folder. The team member definitions and docs it references, such as .claude/docs and the hooks folder, are also in that wider repository. If you install only the skill folder, the config step and the named agents may not resolve.

The skill runs scripts: yes, through the config helper's resolve_config command. It uses no network access. It writes and edits files in the production and design folders, and it is limited to the tools listed in its header.

Review the planned outputs before using them in a live game. The plans are drafts, and the skill does not check them against real data.

• Runs scripts: yes (config helper only)
• Uses network: no
• Writes files under production/live-ops/ and design/live-ops/seasons/
• Needs the wider repository's hooks and .claude/docs for full behaviour

Tips for getting useful plans

Give the season or event a specific name and purpose. Mention the length, the reward types you have in mind, and any constraints such as an existing currency. Choose the team size that matches the work: individual for a quick plan, studio when you want theme and copy included.

At each decision point, pick the option that fits your game and ignore the rest. Keep the files the skill writes, because they are the record of the plan and the starting point for your own spreadsheets and specs.

• Name the season or event and its purpose
• State the length and any reward or currency constraints
• Use studio team size when you need narrative and copy