nicepkg/product-analytics
Measure what matters with proper event tracking, funnels, cohorts, and metrics. Use when setting up analytics, tracking features, or understanding behavior.
npx skills add https://github.com/nicepkg/ai-workflow --skill product-analytics
Measure what matters and make data-driven decisions.
The ONE metric that represents customer value
Examples:
Slack: Weekly Active Users
Airbnb: Nights Booked
Spotify: Time Listening
Shopify: GMV
Your North Star should: ✅ Represent customer value
✅ Correlate with revenue
✅ Be measurable frequently
✅ Rally the team
North Star Metric
├── Input Metrics (drive North Star)
│ ├── Acquisition
│ ├── Activation
│ └── Retention
└── KPIs (business health)
├── Revenue
├── Churn
└── LTV
// Track user actions
analytics.track('Button Clicked', {
button_name: 'signup',
page: 'homepage',
user_id: '123'
})
// Track page views
analytics.page('Homepage', {
referrer: document.referrer,
path: window.location.pathname
})
// Identify users
analytics.identify('user-123', {
email: '[email protected]',
plan: 'pro',
created_at: '2024-01-15'
})
Sign-up Funnel:
1. Land on homepage: 10,000 (100%)
2. Click signup: 2,000 (20%)
3. Fill form: 1,000 (10%)
4. Verify email: 800 (8%)
5. Complete onboarding: 400 (4%)
Insights:
- Biggest drop: Homepage to signup (80% lost)
- Fix: Clarify value prop, add social proof
Week 1 Cohort (Jan 1-7):
- D1: 80% active
- D7: 40% active
- D30: 20% active
Week 2 Cohort (Jan 8-14):
- D1: 85% active (+5%)
- D7: 50% active (+10%)
- D30: 30% active (+10%)
Insight: Onboarding changes improved retention!
Good Retention:
- D1: 60-80%
- D7: 40-60%
- D30: 30-50%
- Flattening curve (good!)
Bad Retention:
- D1: 40%
- D7: 10%
- D30: 2%
- Steep drop-off (bad!)
## Tools
Event Tracking:
Session Recording:
A/B Testing:
## Dashboard Design
Executive Dashboard:
Product Dashboard:
Marketing Dashboard:
## Summary
Great analytics:
- ✅ One North Star Metric
- ✅ Track everything
- ✅ Regular review (weekly)
- ✅ Share insights widely
- ✅ Act on data quickly
Take nicepkg/product-analytics from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.