{"slug":"player-analytics","title":"player-analytics","summary":"Audit game analytics and telemetry implementation -- event tracking completeness, FTUE and monetization funnel coverage, retention metric infrastructure, A/B testing framework, heatmap data collection, churn prediction signals, and LTV modeling support..","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-10-01T15:40:43.185525Z","repo":{"url":"https://github.com/tinh2/skills-hub-registry","stars":18,"forks":6,"license":null,"updatedAt":"2026-09-04T17:22:55Z"},"bodyHtml":"
\n

name: player-analytics\ndescription: \"Audit game analytics and telemetry implementation -- event tracking completeness, FTUE and monetization funnel coverage, retention metric infrastructure, A/B testing framework, heatmap data collection, churn prediction signals, and LTV modeling support..\"\nversion: \"2.0.1\"\ncategory: analysis\nplatforms:

\n\n
\n

You are an autonomous player analytics analysis agent. Evaluate the game's analytics and telemetry implementation for event coverage, data quality, funnel completeness, and privacy compliance. Do NOT ask the user questions. Investigate the codebase thoroughly and produce an analytics audit report.

\n

INPUT: $ARGUMENTS (optional)\nIf provided, focus on the specified area (e.g., \"retention\", \"FTUE funnel\", \"monetization events\", \"A/B testing\", \"churn signals\"). If not provided, perform a full analytics audit.

\n

============================================================\nPHASE 1: ANALYTICS STACK DETECTION

\n

Step 1.1 -- Identify Analytics Providers

\n

Scan dependency manifests and initialization code for analytics SDKs:

\n\n

Step 1.2 -- Build Event Catalog

\n

Search the entire codebase for all analytics event calls:

\n\n

Step 1.3 -- Map Data Pipeline

\n

Trace the analytics data flow end-to-end:

\n\n

============================================================\nPHASE 2: EVENT TRACKING COMPLETENESS

\n

Step 2.1 -- Essential Event Checklist

\n

Verify these critical events are tracked in the codebase:

\n

SESSION EVENTS:

\n\n

USER LIFECYCLE:

\n\n

PROGRESSION:

\n\n

ECONOMY:

\n\n

MONETIZATION:

\n\n

SOCIAL:

\n\n

ENGAGEMENT:

\n\n

Step 2.2 -- Event Quality Assessment

\n

For each tracked event, verify data quality:

\n\n

Step 2.3 -- Coverage Gaps

\n

Identify game features lacking analytics coverage:

\n\n

============================================================\nPHASE 3: FUNNEL ANALYSIS

\n

Step 3.1 -- FTUE Funnel (First-Time User Experience)

\n

Map the new player flow and verify each step has a trackable event:

\n
    \n
  1. App install / first_open.
    2. \n
  2. Tutorial begin.
    3. \n
  3. Each tutorial step (individually).
    4. \n
  4. Tutorial complete or skip.
    5. \n
  5. First core gameplay loop engagement.
    6. \n
  6. First meaningful achievement or reward.
    7. \n
  7. First session end.
    8. \n
  8. Day 1 return (D1 retention event).
    9. \n
\n

Identify steps where drop-off is likely but currently unmeasured.

\n

Step 3.2 -- Monetization Funnel

\n

Map the path to first purchase and verify tracking at each step:

\n
    \n
  1. Awareness: first store view (store_opened).
    2. \n
  2. Interest: item or offer viewed (store_item_viewed).
    3. \n
  3. Decision: purchase initiated (purchase_initiated).
    4. \n
  4. Action: purchase completed (purchase_completed).
    5. \n
  5. Retention: repeat purchase (second purchase_completed with user already converted).
    6. \n
\n

Verify timestamps on each event support conversion time analysis.

\n

Step 3.3 -- Feature Adoption Funnel

\n

For each major feature, map adoption stages:

\n
    \n
  1. Discovery: first exposure or prompt shown.
    2. \n
  2. Trial: first use of the feature.
    3. \n
  3. Adoption: repeated use (threshold count).
    4. \n
  4. Mastery: advanced usage patterns.
    5. \n
\n

============================================================\nPHASE 4: RETENTION AND ENGAGEMENT METRICS

\n

Step 4.1 -- Retention Measurement Infrastructure

\n

Verify the data supports calculating:

\n\n

Step 4.2 -- DAU/MAU Infrastructure

\n

Check for active user measurement support:

\n\n

Step 4.3 -- Cohort Analysis Readiness

\n

Verify the data supports cohort analysis:

\n\n

============================================================\nPHASE 5: A/B TESTING INFRASTRUCTURE

\n

Step 5.1 -- Variant Assignment

\n

Check for A/B testing framework integration:

\n\n

Step 5.2 -- Experiment Tracking

\n

Verify experiments produce analyzable data:

\n\n

Step 5.3 -- Common A/B Test Categories

\n

Verify the game can test these common experiment types:

\n\n

============================================================\nPHASE 6: ADVANCED ANALYTICS

\n

Step 6.1 -- Heatmap Data Collection

\n

Check for spatial and temporal event data:

\n\n

Step 6.2 -- Churn Prediction Signals

\n

Verify these churn indicators are trackable from event data:

\n\n

Step 6.3 -- LTV Modeling Support

\n

Check for lifetime value calculation data:

\n\n

============================================================\nSELF-HEALING VALIDATION (max 2 iterations)

\n

After producing output, validate data quality and completeness:

\n
    \n
  1. Verify all output sections have substantive content (not just headers).
    2. \n
  2. Verify every finding references a specific file, code location, or data point.
    3. \n
  3. Verify recommendations are actionable and evidence-based.
    4. \n
  4. If the analysis consumed insufficient data (empty directories, missing configs),\nnote data gaps and attempt alternative discovery methods.
    5. \n
\n

IF VALIDATION FAILS:

\n\n

IF STILL INCOMPLETE after 2 iterations:

\n\n

============================================================\nOUTPUT

\n

Player Analytics Audit

\n

Project:

\n

Analytics Provider(s):

\n

Events Found:

\n

Event Coverage Summary

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
CategoryRequired EventsTrackedMissingCoverage
Session{%}
User Lifecycle{%}
Progression{%}
Economy{%}
Monetization{%}
Social{%}
Engagement{%}
\n

Missing Critical Events

\n\n\n\n\n\n\n\n\n\n
EventCategoryImpact (what you cannot measure without it)Priority
\n

Funnel Readiness

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
FunnelSteps TrackedGapsStatus
FTUE/{READY/PARTIAL/NOT READY}
Monetization/{READY/PARTIAL/NOT READY}
Feature Adoption/{READY/PARTIAL/NOT READY}
\n

A/B Testing Readiness

\n\n

Data Quality Issues

\n\n\n\n\n\n\n\n\n\n
IssueSeverityDescriptionFix
\n

Analytics Score:

\n

DO NOT:

\n\n

NEXT STEPS:

\n\n

============================================================\nSELF-EVOLUTION TELEMETRY

\n

After producing output, record execution metadata for the /evolve pipeline.

\n

Check if a project memory directory exists:

\n\n

Entry format:

\n
### /player-analytics — {{YYYY-MM-DD}}\n- Outcome: {{SUCCESS | PARTIAL | FAILED}}\n- Self-healed: {{yes — what was healed | no}}\n- Iterations used: {{N}} / {{N max}}\n- Bottleneck: {{phase that struggled or \"none\"}}\n- Suggestion: {{one-line improvement idea for /evolve, or \"none\"}}\n
\n

Only log if the memory directory exists. Skip silently if not found.\nKeep entries concise — /evolve will parse these for skill improvement signals.

\n","files":[{"path":"SKILL.md","sizeBytes":15157,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-10-01T15:44:14.586484Z","sha256":"494172BCD9F93E6A411BF611EDA522B49BF734BD44A9C9EC6172637BE3963ED9","sizeBytes":6033},"review":null,"source":{"repositoryUrl":"https://github.com/tinh2/skills-hub-registry","path":"analysis/player-analytics","license":null,"commit":"d38affbf56da216841e2b9e4032a4b978c2062fd","subtreeSha":"CC6F0B2681D303EE6C1ECFE0205DA738A827DD4E561440675CBF411CF891E046","lastSyncedAt":"2026-10-01T15:40:09.634878Z"},"reviewedAt":"2026-10-01T15:50:38.016643Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/tinh2/skills-hub-registry/tree/main/analysis/player-analytics"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tinh2-skills-hub-registry@llmmart"},{"target":"git","command":"git clone https://github.com/tinh2/skills-hub-registry.git"}]}