product-analytics
Product analytics - event taxonomy, funnel analysis, A/B testing, retention metrikleri.
Profile →npx skills add vibeeval/vibecosystem --skill product-analytics --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Implements a product analytics framework covering event taxonomy, schemas, tracking plans, funnel and cohort analyses, A/B testing constructs, adoption metrics, and provider-agnostic tracking utilities. It includes example SQL queries, TypeScript interfaces, and pseudocode for a cross-provider analytics setup. It prescribes event naming, event schema, categories, and a tracking plan template; defines an AARRR funnel, cohort retention methods, and an adoption funnel with metrics and queries. It also provides a simple sample size calculator and a statistical significance helper for AB tests, plus a DAU/MAU engagement ratio and retention curves. It contains a broad collection of ready-to-use code blocks and schemas intended to guide implementation with the claude-code tool.
How it works
The skill documents a concrete set of structures and procedures:
- Event taxonomy design: naming convention (<object>_<action>) and a TypeScript AnalyticsEvent interface with fields like event_name, timestamp, user_id, session_id, properties, context. EventContext includes app_version, platform, locale, timezone, and optional fields such as page_url, referrer, utm, device.
- Event categories and a tracking plan template: defines categories (Identity, Navigation, Interaction, Transaction, Feature, System) and a trackingPlan object with per-event description, properties schema, triggers, and owner.
- AARRR funnel definitions and example metrics per stage, plus a SQL funnel query that derives acquisitions, activations, retention, and conversions.
- Cohort analysis: weekly retention cohort SQL and a TypeScript CohortData interface plus a buildCohortTable helper.
- A/B testing framework: Experiment and Variant interfaces, and a Sample Size Calculator function with a practical example, plus a Statistical Significance Check function for converting p-values and lift estimates.
- Feature adoption metrics: Adoption funnel diagram, FeatureAdoption interface, and a Feature Adoption SQL query to compute tried, adopted, and power_users and median days to adopt.
- User segmentation: RFM segmentation SQL and Behavioral Segments table guiding how segments map to actions.
- Mixpanel/Amplitude/PostHog event schema: a provider-agnostic tracker interface, a basic Analytics class, and a PostHogProvider implementation with track/identify/page/group/reset methods.
- DAU/MAU tracking: an Engagement Ratio SQL query computing stickiness over 30 days.
- Retention curves and benchmarks: Day-based retention SQL and a table of benchmarks by product type.
- LTV calculations: Simple LTV TS function and a cohort-based LTV SQL example.
- The skill is designed to be used with the claude-code tool (declared tools: claude-code), and the content is structured to guide implementation rather than to execute automatically within this description.
When to use it
Use this skill when you need a comprehensive product analytics blueprint covering event taxonomy, funnel and cohort analyses, AB testing scaffolding, feature adoption tracking, and provider-agnostic analytics integration. It is suitable for teams building or evaluating analytics pipelines using a single repository (vibeeval/vibecosystem) and aiming to standardize event schemas and metrics across platforms.
What it can touch
Declared tools: claude-code. The skill includes code blocks for TypeScript interfaces, SQL queries, and functions that would be implemented or invoked via code tooling compatible with claude-code. Specific touchpoints include event schemas, tracking plan definitions, analytics provider interfaces, and various analytical queries and helpers.
Caveats
License: MIT. The material provides examples and templates; outcomes are not guaranteed to be achieved by mere adoption of the templates. It does not specify runtime environments beyond code samples, and some placeholders (e.g., session management, env values) imply integration work is required. No explicit runtime or platform constraints are stated beyond the TypeScript/SQL samples.
# Product Analytics ## Event Taxonomy Design ### Event Naming Convention ``` <object>_<action> Ornekler: user_signed_up page_viewed button_clicked feature_activated subscription_started payment_completed item_added_to_cart search_performed ``` ### Event Schema (TypeScript) ```typescript interface AnalyticsEvent { event_name: string; timestamp: string; // ISO 8601 user_id: string; anonymous_id?: string; // pre-auth tracking session_id: string; properties: Record<string, unknown>; context: EventContext; } interface EventContext { app_version: string; platform: "web" | "ios" | "android"; locale: string; timezone: string; page_url?: string; referrer?: string; utm?: UTMParams; device?: DeviceInfo; } interface UTMParams { source?: string; medium?: string; campaign?: string; term?: string; content?: string; } ``` ### Event Categories | Kategori | Ornek Eventler | Amac | |----------|---------------|------| | Identity | user_signed_up, user_logged_in | Kim? | | Navigation | page_viewed, tab_switched | Nerede? | | Interaction | button_clicked, form_submitted | Ne yapti? | | Transaction | purchase_completed, subscription_started | Para akisi | | Feature | feature_activated, feature_used | Deg
- Event Taxonomy Design
- Event Naming Convention
- Event Schema (TypeScript)
- Event Categories
- Tracking Plan Template
- AARRR Funnel (Pirate Metrics)
- Funnel Tanimlari
- Funnel Analysis Query
- Cohort Analysis
- Retention Cohort Query
- Cohort Visualization Data
- A/B Testing Framework
- Experiment Design
- Sample Size Calculator
What does the product-analytics skill do?
Product analytics - event taxonomy, funnel analysis, A/B testing, retention metrikleri.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill product-analytics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.