roblox-analytics-liveops — Claude Code skill: what it does
roblox-analytics-liveops — a skill for Claude Code sets up game analytics, funnels, economy, and live ops for Roblox. Runs when instrumenting gameplay, economy tuning, or setting up A/B tests.
MIT 1,200 installs ★ 131 updated 2026-11-03
npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a claude-codeWhat roblox-analytics-liveops does
The skill provides Lua templates for AnalyticsService, ConfigService, and BadgeService to handle server-side tracking and live configurations in Roblox. It logs currency sinks and sources, tutorial progression steps, player segments, and custom boss metrics safely inside pcall blocks. Remote balancing values update dynamically without game republishing via ConfigService.
The implementation requires fallback values for missing configurations and relies on Open Cloud APIs for backend notifications and experiment targeting. Live-ops components cover streak counters, timed events with UTC checks, and player support feedback prompts.
What it helps with
- track economy flows and onboarding funnels on the server
- configure A/B experiments and live feature flags via ConfigService
- award achievement badges securely via BadgeService
- send re-engagement notifications through Open Cloud
- implement daily streaks and seasonal shop rotations
Example prompts for the agent
- Add economy logging for a shop purchase using AnalyticsService
- Fetch live configurations from ConfigService with fallback values
- Implement server-side badge awards for player progression
How to install roblox-analytics-liveops
1Skills CLI (Vercel)
npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a claude-code2Manually: put the files in place
~/.claude/skills/roblox-analytics-liveops/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/roblox-analytics-liveops/
1Skills CLI (Vercel)
npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a codex2Manually: put the files in place
.agents/skills/roblox-analytics-liveops/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a cursor2Manually: put the files in place
.cursor/skills/roblox-analytics-liveops/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install EL4CTEO/roblox-skills skills/roblox-analytics-liveops2Manually: put the files in place
.github/skills/roblox-analytics-liveops/SKILL.md1Skills CLI (Vercel)
npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a gemini-cli2Platform CLI
gemini skills install https://github.com/EL4CTEO/roblox-skills --path skills/roblox-analytics-liveopsManually: put the files in place
.devin/skills/roblox-analytics-liveops/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about roblox-analytics-liveops
How to install roblox-analytics-liveops in Claude Code?
Run npx skills add EL4CTEO/roblox-skills --skill roblox-analytics-liveops -a claude-code followed by ~/.claude/skills/roblox-analytics-liveops/SKILL.md.
What does roblox-analytics-liveops do?
It generates Lua code and patterns for Roblox analytics, server-side economy events, player segments, live-ops configurations, and notification systems.
What is required to use this skill?
A Roblox project using Luau with server-side access to Creator Hub dashboards and Open Cloud services.
Source text
SKILL.md · MIT
---
name: roblox-analytics-liveops
description: Analytics and live ops - AnalyticsService economy/funnel/onboarding/progression/custom events, player segments, experience configs via ConfigService, A/B experiments, badges, experience notifications, timed events, daily rewards, season passes. Use when instrumenting a game, tuning economy or onboarding, running A/B tests or feature flags, or planning live events and re-engagement.
---
# Analytics and live operations
## Analytics events (server-side, `AnalyticsService`)
Standard events feed the Creator Hub dashboards automatically (economy, funnels, progression,
custom). The `Fire*` methods are deprecated; use the `Log*` family.
```luau
--!strict
local AnalyticsService = game:GetService("AnalyticsService")
local Analytics = {}
-- Currency sources and sinks → Economy dashboard.
function Analytics.coinsEarned(player: Player, amount: number, balance: number, source: string)
AnalyticsService:LogEconomyEvent(
player,
Enum.AnalyticsEconomyFlowType.Source,
"Coins", -- currency type
amount,
balance, -- ending balance
Enum.AnalyticsEconomyTransactionType.Gameplay.Name, -- or a custom string like "QuestReward"
source -- item SKU / source id
)
end
function Analytics.itemBought(player: Player, price: number, balance: number, itemSku: string)
AnalyticsService:LogEconomyEvent(
player,
Enum.AnalyticsEconomyFlowType.Sink,
"Coins",
price,
balance,
Enum.AnalyticsEconomyTransactionType.Shop.Name,
itemSku
)
end
-- First-session tutorial funnel (steps must be sequential, 1-based).
function Analytics.onboarding(player: Player, step: number, stepName: string)
AnalyticsService:LogOnboardingFunnelStepEvent(player, step, stepName)
end
-- Recurring funnels (e.g. shop purchase flow); share a session id per attempt.
function Analytics.shopFunnel(player: Player, sessionId: string, step: number, stepName: string)
AnalyticsService:LogFunnelStepEvent(player, "ShopPurchase", sessionId, step, stepName)
end
-- Level progression.
function Analytics.levelStarted(player: Player, level: number)
AnalyticsService:LogProgressionStartEvent(player, "MainPath", level, `Level{level}`)
end
function Analytics.levelCompleted(player: Player, level: number)
AnalyticsService:LogProgressionCompleteEvent(player, "MainPath", level, `Level{level}`)
end
-- Anything else: numeric custom events, sliced by up to 3 custom fields.
function Analytics.bossKilled(player: Player, bossId: string, seconds: number)
AnalyticsService:LogCustomEvent(player, "BossKillTime", seconds, {
[Enum.AnalyticsCustomFieldKeys.CustomField01.Name] = bossId,
})
end
return Analytics
```
Guidelines:
- Log from the **server** (trustworthy, and required by these APIs). Keep event names and custom-field
values low-cardinality (IDs of categories, not free text or user IDs).
- Economy events need accurate `endingBalance`; log every source and sink or the dashboard misleads.
- Design funnels before building features (onboarding steps, shop flow, first purchase).
- `AnalyticsService:GetPlayerSegmentsAsync(player)` returns segment info (payer status, account age in
your game, ...) at runtime to tailor onboarding and offers — `pcall` it.
## Experience configs (live values without republishing)
Create configs in Creator Hub (or Open Cloud) — balance numbers, feature flags, event toggles — and read them
on the server with `ConfigService`. Published changes arrive in running servers.
```luau
--!strict
local ConfigService = game:GetService("ConfigService")
local ok, snapshot = pcall(function()
return ConfigService:GetConfigAsync()
end)
local function get(key: string, default: any): any
if not ok then
return default
end
local value = snapshot:GetValue(key)
return if value == nil then default else value
end
local bossHealth = get("bossHealth", 500)
print("boss health", bossHealth)
if ok then
snapshot.UpdateAvailable:Connect(function()
snapshot:Refresh() -- apply newly published values at a safe moment (e.g. between rounds)
print("new boss health", get("bossHealth", 500))
end)
end
```
- Always code a default: configs may fail to load.
- **Experiments / targeted configs** evaluate per player: use `ConfigService:GetConfigForPlayerAsync(player)`
(`GetConfigAsync` ignores targeting). Experiments run 14–60 days, up to two variants plus control; pick a
goal metric and respect the minimum detectable effect. Manage via Creator Hub or the Open Cloud
experimentation API (`roblox-open-cloud`). **Early Harm Detection** shows near-real-time playtime, payer
conversion, and ARPU (every 5 min) for the first 24 h — stop a harmful variant early.
- Studio testing: `ConfigService:SetTestingValue(key, value)` / `ClearTestingValue`.
## Badges
`BadgeService:AwardBadgeAsync(userId, badgeId)` (server, `pcall`; skip if `UserHasBadgeAsync` or
`CheckUserBadgesAsync` already says owned). `AwardBadge`/`UserHasBadge` are deprecated. Badges are
great onboarding and progression milestones and show on players' profiles.
## Experience notifications (re-engagement)
1. Ask players to opt in at a meaningful moment: `ExperienceNotificationService:CanPromptOptInAsync()` then
`PromptOptIn()` (client).
2. Create notification strings in Creator Hub; send from your backend via Open Cloud
`POST /cloud/v2/users/{userId}/notifications` (e.g. "your crops are ready", "event starts now").
Notifications are rate-limited and moderated; send ones players value.
## Live-ops patterns
- **Timed events**: schedule with UTC timestamps in a config (`eventStart`, `eventEnd`); compare with
`os.time()` on the server; broadcast state via attributes; clients show countdowns from
`workspace:GetServerTimeNow()`.
- **Season pass / rotating shops**: rotation seed = `math.floor(os.time() / 86400)` for daily shops; store
claimed rewards per season id in player data.
- **Daily rewards/streaks**: store `lastClaimDay` (UTC day number) and streak count; grant on the server.
- Ship content behind config flags, validate with a small rollout/experiment, then roll out to 100%.
- Watch Creator Hub dashboards: retention (D1/D7/D30), session length, conversion, ARPPU, funnels, and
performance (crash rate, FPS, memory) after every release. Discovery impressions/plays use a new
measurement pipeline from Oct 12, 2026 (higher counts, slightly lower play-through rate) — don't read the
jump as a real change.
- **Before launch**: invite up to 10 friends or group members as early testers from the publish flow.
- **Player Support** (early access, age-checked 13+): add an in-game "report a problem" button that calls
`SocialService:PromptFeedbackSubmissionAsync({ FeedbackType = Enum.FeedbackType.PlayerSupport })`
(client, `pcall`); reports arrive with device info and screenshots in Creator Hub → Audience → Player Support.
## Related skills
`roblox-monetization` (offers, pricing), `roblox-data-stores` (streaks, season data),
`roblox-open-cloud` (configs/experiments/notifications APIs), `roblox-game-systems`.
© EL4CTEO · MIT · EL4CTEO/roblox-skills