mcpField
R
roblox-analytics-instrumentation

roblox-analytics-instrumentation

github.com/ashexplainedData & databases3893 installsUpdated 17w ago
Repository

About roblox-analytics-instrumentation

Roblox Analytics Instrumentation is a skill for planning measurement in Roblox games, from core-loop events to retention funnels. It produces KPI goals, event payloads, funnel questions, ownership, and a validation plan.

Key features

  1. 01Core-loop and economy event planning
  2. 02Tutorial, quest, and social event coverage
  3. 03Retention and onboarding funnel checks
  4. 04Versioned payload and data-quality guidance
  5. 05Server/client event ownership
  6. 06Implementation validation plan

Use cases

  1. 01Measuring first-session onboarding
  2. 02Reviewing tutorial completion and abandonment
  3. 03Tracking economy and purchase behavior
  4. 04Checking return hooks and mobile friction

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ashexplained/roblox-skills --skill roblox-analytics-instrumentation

After installing, type/roblox-analytics-instrumentationin Claude Code to confirm it loaded.

Details

From the project README

Roblox Analytics Instrumentation

Goal

Measure whether the game is fun, understandable, and profitable. Instrument the core loop before optimizing it.

Core Events

Track:

  • Session start, spawn complete, and first playable action.
  • Tutorial step shown, completed, skipped, or abandoned.
  • Core loop start, success, fail, and reward claim.
  • Currency earned, spent, purchased, and sunk.
  • Upgrade viewed, purchased, unaffordable, and equipped.
  • Quest accepted, progressed, completed, abandoned, and claimed.
  • Social invite, party join, group join, trade started, trade completed.
  • Shop opened, product viewed, purchase attempted, purchase completed.
  • Death, retry, teleport, zone unlock, level up, prestige, and churn-risk exits.

Funnel Checks

Prioritize:

  • First action within 10-30 seconds.
  • First reward within the first loop.
  • First upgrade or meaningful progress in session one.
  • Day 1, Day 3, and Day 7 return hooks.
  • Mobile-specific control or UI friction.

Event Design

  • Use stable event names and versioned payloads.
  • Include player segment, platform, session age, current zone, level, and economy state when useful.
  • Avoid sending personally sensitive or noisy data.
  • Log server-authoritative economy and purchase events from the server.
  • Keep high-frequency events sampled or aggregated.

Output

Return:

  • KPI goals.
  • Event list and payload fields.
  • Funnel questions each event answers.
  • Server/client ownership.
  • Validation plan after implementation.

Next

Act on what the data shows: tune with roblox-economy-balancing or roblox-retention-monetization, and schedule the follow-up work with roblox-liveops-roadmap.

Comments

Markdown supported