analytics-design

Design Mixpanel-aware tracking plans or critiques for web analytics instrumentation.

1|Updated Jul 31, 2023
One-click install
npx skills add https://github.com/austintheriot/dotfiles --skill analytics-design-austintheriot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analytics-design
Source: https://github.com/austintheriot/dotfiles/tree/main/.claude/skills/analytics-design
Command: npx skills add https://github.com/austintheriot/dotfiles --skill analytics-design-austintheriot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns ambiguous product analytics ideas into a clear, privacy-aware tracking plan (or it stress-tests an existing plan) so you can reliably measure funnels, retention, experiments, and NSM impact—especially through a Mixpanel-ready lens.

Core Features & Use Cases

  • Event taxonomy & instrumentation design: Define what to track (events) and what each event should include (properties), including super properties and PII/cardinality boundaries.
  • Funnel, retention, and A/B test specifications: Specify funnel steps and windows, retention cohort and re-entry logic, and A/B instrumentation requirements like exposure tracking and primary metrics.
  • Identity and server-side correctness: Plan when to identify users, how to handle anonymous-to-authenticated transitions, when to fire critical events server-side, and how to reset on logout.
  • Critique mode for proposed plans: Review an existing analytics plan for identity correctness, taxonomy consistency, exposure vs assignment issues, privacy risks, funnel/retention completeness, and cost/volume implications.

Quick Start

Ask the skill whether you are designing instrumentation from scratch or reviewing a proposed plan, then provide the user flow and success outcome so it can produce a tracking plan or critique.

Frequently Asked Questions about analytics-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a Mixpanel tracking plan for new product features?

Design a product analytics tracking plan by defining event taxonomy, properties, and privacy boundaries. Specify funnel steps, retention cohorts, and identity strategy for anonymous-to-authenticated user transitions to produce a structured instrumentation document.

What is event taxonomy and why does it matter for product analytics?

Event taxonomy is the structured classification of tracking events and their properties in product analytics. It ensures reliable funnel definition, accurate retention modeling, and controlled data volume by setting clear PII and cardinality boundaries.

How do I specify A/B testing instrumentation for exposure tracking?

Specify A/B test instrumentation by defining exposure tracking events and primary success metrics. Distinguish between user exposure and assignment, verify identity correctness, and map the experiment directly to your North Star Metric impact.

Can I critique an existing analytics plan for identity and privacy issues?

Yes, you can critique an existing analytics plan. Review the plan for identity correctness, taxonomy consistency, exposure versus assignment issues, privacy compliance risks, funnel completeness, and overall data cost or volume implications.

When should I fire analytics events server-side instead of client-side?

Fire analytics events server-side for critical conversions requiring high data reliability. Server-side tracking prevents ad-blocker data loss, ensuring accurate identity strategy execution and strict privacy compliance boundaries.

What are the limitations of using a category-level analytics design approach?

A category-level analytics design approach outputs structured documentation but does not write instrumentation code. Developers must manually translate the specified event taxonomy, identity rules, and funnels into actual application tracking logic.