agentleFS
AshExplainedAshExplained/roblox-skills/roblox-analytics-instrumentation/SKILL.md

roblox-analytics-instrumentation

Skill5 starsChanged 5 months agoMITView on GitHub

Plan Roblox analytics instrumentation and event logging. Use for retention funnels, first-action timing, tutorial drop-off, economy events, monetization conversion, session milestones, progression analytics, A/B test planning, and live game KPI review.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use stable event names and versioned payloads.

    line 38
  2. Distinctive:

    Avoid sending personally sensitive or noisy data.

    line 40
  3. Distinctive:

    Keep high-frequency events sampled or aggregated.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.