product-analytics

daffy0208/ai-dev-standards · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/daffy0208/ai-dev-standards --skill product-analytics
0 commentsdiscussion
summary

Measure what matters and make data-driven decisions.

skill.md

Product Analytics

Measure what matters and make data-driven decisions.

North Star Metric

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

Key Metrics Hierarchy

North Star Metric
  ├── Input Metrics (drive North Star)
  │   ├── Acquisition
  │   ├── Activation
  │   └── Retention
  └── KPIs (business health)
      ├── Revenue
      ├── Churn
      └── LTV

Event Tracking

// 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

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

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

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

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
how to use product-analytics

How to use product-analytics on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add product-analytics
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/daffy0208/ai-dev-standards --skill product-analytics

The skills CLI fetches product-analytics from GitHub repository daffy0208/ai-dev-standards and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/product-analytics

Reload or restart Cursor to activate product-analytics. Access the skill through slash commands (e.g., /product-analytics) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.771 reviews
  • Chaitanya Patil· Dec 20, 2024

    product-analytics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hiroshi Brown· Dec 20, 2024

    product-analytics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chen Liu· Dec 16, 2024

    Keeps context tight: product-analytics is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aanya Ndlovu· Dec 4, 2024

    product-analytics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Kabir Smith· Dec 4, 2024

    product-analytics reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kwame Brown· Nov 23, 2024

    product-analytics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chen Chen· Nov 23, 2024

    I recommend product-analytics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Piyush G· Nov 11, 2024

    product-analytics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Carlos Tandon· Nov 11, 2024

    product-analytics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chen Lopez· Nov 7, 2024

    We added product-analytics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 71

1 / 8