Skip to content

Product
Enterprise
Pricing
Resources

Enterprise
Pricing

Product

Agents
Enterprise
Code Review
Cloud
Tab
CLI
Pricing

Resources

Download
Changelog
Docs
Forum ↗
Status ↗
Future ↗
Marketplace

Company

Careers
Blog
Community
Students
Brand
Anysphere ↗

Legal

Terms of Service
Privacy Policy
Data Use
Security

Connect

X ↗
LinkedIn ↗
YouTube ↗

© 2026 Anysphere, Inc.🛡︎ SOC 2 Certified

configuring-experiment-analytics | Cursor Skill

/

Created by PostHogVerified by CursorView Source

/

configuring-experiment-analytics

Cursor Skill

Configures the analytics side of a PostHog experiment — exposure criteria (default `$feature_flag_called` vs custom exposure events), primary and secondary metrics, the supported metric types (count, sum, ratio with `math` and `math_property`, retention with `retention_window_start` and `start_handling`), multivariate user handling ("Exclude" vs "First seen variant"), and how to read results once the experiment is live. Use when the user adds or edits a primary or secondary metric (e.g. "add a secondary metric tracking 'downloaded_file' per user"), sets up a ratio metric (e.g. "revenue from purchase_completed / pageviews"), sets up a retention metric (e.g. "$pageview → uploaded_file, 7-day window"), configures custom exposure (e.g. "only count users who hit /checkout"), changes multivariate handling, or asks "who is in the analysis?", "how do I measure impact?", "is this winning?", "what's the confidence level?", or "should I ship?".

Access PostHog analytics, feature flags, experiments, error tracking, and insights directly from Cursor

Created by PostHogVerified by CursorView Source

analyzing-experiment-session-replaysAnalyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.

assessing-heatmapsAssesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements. TRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap/click data, or to 'analyze/assess/review the heatmap' for a URL. DO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).

auditing-endpointsAudit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks "what endpoints can I clean up?", "are any of my endpoints broken?", "which materialised versions are still being called?", or wants a one-shot cleanup pass over the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.

auditing-experiments-flagsAudit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.

auditing-warehouse-data-healthAudit the health of a PostHog project's data warehouse — find every broken or degraded pipeline item across sources, sync schemas, materialized views, batch exports, and transformations. Use when the user asks "what's broken in my warehouse?", "give me a health check", "audit my data pipeline", "why are some dashboards stale?", or wants a one-shot triage summary before deciding where to spend time. Produces a prioritized report of issues grouped by severity and type, with recommended next steps.

error-analyzerAnalyze multiple PostHog errors in parallel to identify patterns, root causes, and prioritize fixes based on user impact.

sessionendHook: SessionEnd

pretooluseHook: PreToolUse

posthogllma-cc-ingestManually send a Claude Code session log to PostHog LLM Analytics

posthogllma-cc-setupSet up PostHog LLM Analytics to capture Claude Code sessions

posthogllma-cc-statusCheck if Claude Code sessions are being sent to PostHog LLM Analytics