analytics

Implements product analytics, event tracking, A/B testing, and feature flags in web applications.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/lunaticwithaduck/easytech3d --skill analytics-lunaticwithaduck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analytics
Source: https://github.com/lunaticwithaduck/easytech3d/tree/main/.claude/skills/analytics
Command: npx skills add https://github.com/lunaticwithaduck/easytech3d --skill analytics-lunaticwithaduck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires posthog-js, posthog-node.

What problem does it solve? Teams struggle to instrument web applications with consistent event tracking, choose the right analytics platform, and run statistically sound experiments without creating messy, unreliable data pipelines. ## Core Features & Use Cases - Tool Selection Guidance: Decision trees and comparison tables for PostHog, Mixpanel, GA4, Plausible, LaunchDarkly, and Statsig. - Event Tracking Architecture: Naming conventions, event taxonomies, tracking plan templates, and client vs server-side tracking patterns for React and Next.js. - Experimentation & Feature Flags: A/B testing workflows, experiment sizing guidance, boolean and multivariate flag patterns, and user segmentation with cohorts. - Use Case: A Next.js team needs to measure a signup funnel and test a new CTA. Use this Skill to set up PostHog with proper page view tracking, define funnel events, and gate the new CTA behind a multivariate feature flag. ## Quick Start Set up PostHog analytics in my Next.js app with page view tracking, user identification on login, and a signup conversion funnel.

Frequently Asked Questions about analytics

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

FAQPage Schema
How do I set up PostHog analytics in a Next.js app?▼

Initialize posthog-js in a client provider with capture_pageview disabled, then manually track page_viewed events on pathname changes using usePathname. Call posthog.identify after login and posthog.reset on logout to maintain accurate user identity.

PostHog vs Mixpanel vs GA4 for product analytics?▼

PostHog is an all-in-one open-source option with session replay and feature flags, free to 1M events monthly. Mixpanel offers deeper funnel and retention analysis, while GA4 suits traffic and marketing attribution with Google Ads integration.

Should I track events client-side or server-side?▼

Track UI interactions like clicks and page views on the client, but send business-critical events like subscription_created and invoice_paid from the server. Ad blockers miss 15-30% of client events, so server-side tracking ensures reliable revenue data.

How do I implement feature flags with PostHog?▼

Use posthog.isFeatureEnabled for boolean kill switches and posthog.getFeatureFlag for multivariate variants. Server-side, use posthog-node's isFeatureEnabled with person properties for targeted rollouts by plan or company size.

Why are my analytics events missing or inconsistent?▼

Missing events usually come from ad blockers, unflushed serverless functions, or absent user identification. Call posthog.shutdown before serverless exit, use server-side tracking for critical events, and enforce a strict object_action naming convention.

How do I make event tracking GDPR compliant?▼

Check consent status before capturing events, use anonymous tracking without person profiles for partial consent, and call posthog.opt_out_capturing when denied. Never include PII in event properties and respect the Do Not Track header.