← Browse

@tabooharmony/roblox-analytics

A

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

skillclaude

Install

agr install @tabooharmony/roblox-analytics --target claude

Writes 1 file into .claude/skills/, pinned to git-d4c08139.

  • .claude/skills/roblox-analytics/SKILL.md

Document


name: roblox-analytics description: "Use when tracking player behavior, economy events, or funnels with AnalyticsService, including event taxonomy, rate limits, and batching." last_reviewed: 2026-07-26 sources:


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, 5 unique currency 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 steps do not need to fire in order. If a later step is logged without earlier ones, the skipped intermediate steps are automatically back-filled as completed.
  • 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.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-d4c08139cf752026-07-31