product-analytics · daffy0208 — Claude Code skill: what it does, how to install
A skill that lays out product analytics: picking a North Star metric, mapping a signup funnel, comparing cohorts and marking user actions as events.
MIT 244 installs ★ 39 updated 2025-12-25
npx skills add daffy0208/ai-dev-standards --skill product-analytics -a claude-codeWhat product-analytics does
What you get is a structure, not a library. One North Star metric sits on top, input metrics for acquisition, activation and retention feed it, and business KPIs such as revenue, churn and LTV sit beside it. Sample North Stars are borrowed from real products: weekly active users at Slack, nights booked at Airbnb, listening time at Spotify, GMV at Shopify.
Then it turns practical. Event calls like analytics.track, analytics.page and analytics.identify, a signup funnel broken down step by step, week-over-week cohort comparison, and retention ranges split into healthy and weak curves. Metrics are grouped per stage, from CPC and time to value through DAU/MAU to LTV:CAC. Dashboard layouts are divided between executive, product and marketing views.
The North Star and the KPIs sit on different levels here, so MRR cannot stand in for the value metric — it tracks business health, not whether someone actually got value. Vendors stay as a plain list: Mixpanel, Amplitude and PostHog for events, FullStory and Hotjar for session recording, Optimizely and VWO for A/B tests. Wiring the SDK is your part.
What it helps with
- Pick a North Star metric that reflects customer value
- Instrument key user actions as analytics events
- Locate the step where the signup funnel leaks
- Compare retention across two weekly cohorts
- Set up separate dashboards for product and marketing
Example prompts for the agent
- Map our signup funnel step by step and tell me where we lose the most users.
- Suggest a North Star metric for our product plus the input metrics that drive it.
- Write
analytics.trackcalls for the signup button click and the homepage view.
How to install product-analytics
1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill product-analytics -a claude-code2Manually: put the files in place
~/.claude/skills/product-analytics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/product-analytics/
1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill product-analytics -a codex2Manually: put the files in place
.agents/skills/product-analytics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill product-analytics -a cursor2Manually: put the files in place
.cursor/skills/product-analytics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install daffy0208/ai-dev-standards skills/product-analytics2Manually: put the files in place
.github/skills/product-analytics/SKILL.md1Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill product-analytics -a gemini-cli2Platform CLI
gemini skills install https://github.com/daffy0208/ai-dev-standards --path skills/product-analyticsManually: put the files in place
.devin/skills/product-analytics/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add daffy0208/ai-dev-standards --skill product-analytics -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about product-analytics
How do I install product-analytics in Claude Code?
Run npx skills add daffy0208/ai-dev-standards --skill product-analytics -a claude-code. The skill ends up at ~/.claude/skills/product-analytics/SKILL.md.
What does product-analytics do?
It pulls product analytics into one scheme: a North Star metric, input metrics per stage, funnels, cohorts, retention curves and dashboard layouts.
Which analytics tools does it mention?
Mixpanel, Amplitude and PostHog for events; FullStory, LogRocket and Hotjar for session recording; Optimizely, VWO and Google Optimize for A/B tests. The SDKs themselves are connected separately.
Source text
SKILL.md · MIT
---
name: product-analytics
description: Measure what matters with proper event tracking, funnels, cohorts, and metrics. Use when setting up analytics, tracking features, or understanding behavior.
license: Complete terms in LICENSE.txt
---
# Product Analytics
Measure what matters and make data-driven decisions.
## North Star Metric
**The ONE metric that represents customer value**
```yaml
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
```
## Key Metrics Hierarchy
```
North Star Metric
├── Input Metrics (drive North Star)
│ ├── Acquisition
│ ├── Activation
│ └── Retention
└── KPIs (business health)
├── Revenue
├── Churn
└── LTV
```
## Event Tracking
```typescript
// 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'
})
```
## Funnel Analysis
```yaml
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
```
## Cohort Analysis
```yaml
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!
```
## Retention Curves
```yaml
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!)
```
## Key Metrics to Track
### Acquisition
- Traffic sources (organic, paid, referral)
- Cost per click (CPC)
- Conversion rate (visitor → signup)
### Activation
- Signup → first core action
- Time to value
- Onboarding completion rate
### Retention
- DAU / MAU (stickiness)
- Retention rate D1, D7, D30
- Churn rate
### Revenue
- MRR / ARR
- ARPU (Average Revenue Per User)
- LTV (Lifetime Value)
- LTV:CAC ratio
### Referral
- Viral coefficient
- Referral signups
- NPS (Net Promoter Score)
````
## Tools
```yaml
Event Tracking:
- Mixpanel (best for products)
- Amplitude (good alternative)
- PostHog (open-source)
Session Recording:
- FullStory
- LogRocket
- Hotjar
A/B Testing:
- Optimizely
- VWO
- Google Optimize (free)
````
## Dashboard Design
```yaml
Executive Dashboard:
- North Star Metric (big number)
- Revenue (MRR/ARR)
- Key metric trends (graphs)
Product Dashboard:
- Active users (DAU/WAU/MAU)
- Feature usage
- Retention cohorts
- Funnels
Marketing Dashboard:
- Traffic sources
- Conversion rates
- Cost per acquisition
- ROI by channel
```
## Summary
Great analytics:
- ✅ One North Star Metric
- ✅ Track everything
- ✅ Regular review (weekly)
- ✅ Share insights widely
- ✅ Act on data quickly
© daffy0208 · MIT · daffy0208/ai-dev-standards
Similar skills
All skills for Data and databases →product-analytics by other authors comes first.