agentleFS
Sign inStart free
szlayszlay/roblox-base/.claude/skills/roblox-analytics/SKILL.md

roblox-analytics

Skill1 starsChanged 4 months agoMITView on GitHub

Use when tracking player behavior, economy events, or funnels with AnalyticsService, including event taxonomy, rate limits, and batching.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use AnalyticsService (built-in).

    line 22

≈ “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 Reference

When to Load

Load when tracking player behavior, economy events, or funnels; building custom event instrumentation; or understanding AnalyticsService rate limits and batching.

Quick Reference

Load Full Reference below only when you need specific API signatures or implementation patterns.

Key rules:

  • Use AnalyticsService (built-in). No third-party analytics SDK needed.
  • Three event types: Custom (counters/values), Economy (currency flow), Funnel (step progression)
  • Rate limit: 120 + (20 × CCU) calls per minute. Batch where possible.
  • Max 100 custom events, 10 economy resource types, 10 funnels, 3 custom fields per event.
  • Log events AFTER successful operations, not on attempt (avoids inflated metrics).
  • Custom fields (up to 3) let you slice data without burning event cardinality.
  • Economy events track sources (earned) and sinks (spent) separately.
  • Funnel events must fire steps in order. Skipped steps break the funnel.
  • Events appear on Creator Hub dashboard after ~24 hours. Use "View Events" for real-time validation.
  • Server-side logging preferred for accuracy. Client-side only for UI interaction tracking.
  • Creator Rewards has no AnalyticsService grant event. Use analytics for leading indicators such as session duration, onboarding, and referral-flow milestones; use Creator Dashboard for reward attribution and payout data.

Need more detail? Load references/full.md for the complete reference with code examples, API tables, and edge cases.

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.

Check your setup, free