By name: analytics-interpretation description: Use when interpreting product analytics, retention, funnel, cohort, LTV, ARPU, payback, or App Store metric changes.
Analytics Interpretation
Purpose
Use when interpreting product analytics, diagnosing weak metrics, comparing cohorts, evaluating retention, sanity-checking LTV, ARPU, ARPPU, payback, App Store funnel data, or deciding whether to invest, iterate, pivot, or sunset.
Routing
Use this skill only when the request matches the frontmatter description. If a narrower framework, platform, testing, debugging, or workflow skill clearly owns the request, use the narrower skill instead.
Before assuming project-specific setup, look for the expected docs, scripts, folders, tools, or memory files in the repository. If the required setup is missing and the workflow cannot proceed without it, ask the user for the location or permission to create it.
Workflow
- Read the relevant sections of
references/full-guidance.mdbefore acting. - Load any additional reference files listed below that match the task.
- Apply the smallest workflow path that satisfies the request.
- Verify with the appropriate build, test, lint, review, screenshot, or source check before reporting completion.
References
references/full-guidance.md- complete workflow, examples, checklists, and detailed rules moved from the original entrypoint.