VerifiedPlugin
Documentation
share
A Claude Code plugin that saves and shares your coding sessions to GitHub repositories in readable markdown format.
@posthogData
Plugin
posthog
:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Plugin Signal95/100Strong
maintained100
capable100
documented75
adopted97
Install
$ npx -y skills add posthog/posthog --agent claude-code
Run the curl in your terminal, the rest in Claude Code.
Stats
37,596
Stars
3,162
Forks
Active
Maintenance
Python
Language
just now
Last commit
6y ago
Created
Repo: posthog/posthog
In this plugin
- skills
- analyzing-expensive-users
- creating-online-evaluations
- exploring-ai-failures
- exploring-llm-clusters
- exploring-llm-costs
- exploring-llm-evaluations
- exploring-llm-traces
- feature-usage-feed
- downloading-batch-export-files
- building-canvases
- building-html-canvases
- building-react-quill-canvases
- querying-canvas-data
- validating-and-publishing-canvases
- setting-up-support-slack-locally
- building-a-dashboard
- setting-up-data-catalog
- modeling-activation-metrics
- modeling-conversion-metrics
- modeling-dimension-tables
- modeling-product-usage-metrics
- modeling-revenue-metrics
- modeling-warehouse-foundations
- auditing-warehouse-view-health
- canvas-templates
- onboarding-videos
- quill-code
- storybook-stories
- test-electron-app
- mcp-servers
- subagent-orchestration
- dynamic-workflows
- auditing-endpoints
- consuming-endpoints-from-client-code
- copying-endpoints-across-projects
- creating-an-endpoint
- diagnosing-endpoint-performance
- exploring-endpoint-execution-logs
- managing-endpoint-versions
- diagnosing-ci-and-merge-bottlenecks
- investigating-ci-failures
- turning-engineering-analytics-into-insights
- authoring-error-tracking-alerts
- diagnosing-stacktrace-symbolication
- grouping-noisy-errors
- investigating-error-issue
- suppressing-noisy-errors
- triaging-error-issues
- analyzing-experiment-session-replays
- configuring-experiment-analytics
- configuring-experiment-rollout
- creating-experiments
- diagnosing-experiment-results
- finding-experiments
- managing-experiment-lifecycle
- scanning-experiments-with-replay-vision
- cleaning-up-stale-feature-flags
- copying-flags-across-projects
- finding-deleted-feature-flags
- diagnosing-sdk-health
- resolving-ingestion-warnings
- authoring-log-alerts
- investigating-logs
- testing-mcp-tools-locally
- debugging-mcp-analytics
- exploring-mcp-intent-clusters
- exploring-mcp-sessions
- exploring-mcp-tool-quality
- exploring-mcp-tool-usage
- improving-mcp-tools
- investigating-metric-anomalies
- auditing-experiments-flags
- checking-deploy-timing
- managing-subscriptions
- querying-posthog-data
- writing-simplified-technical-english
- choosing-trend-or-slope-view
- exploring-autocapture-events
- formatting-insight-axes
- investigate-metric
- managing-reminders
- debugging-local-replay
- diagnosing-missing-recordings
- finding-replay-for-issue
- finding-sessions-to-watch
- investigating-replay
- creating-replay-vision-scanners
- exploring-replay-vision-observations
- review-hog-authoring
- review-hog-blind-spots-general
- review-hog-perspective-contracts-security
- review-hog-perspective-logic-correctness
- review-hog-perspective-performance-reliability
- review-hog-validation-criteria
- authoring-scouts
- debugging-signals-pipeline
- exploring-scouts
- inbox-exploration
- signals-scout-ai-observability
- signals-scout-anomaly-detection
- signals-scout-apm
- signals-scout-conversations
- signals-scout-csp-violations
- signals-scout-customer-analytics-billing-and-usage
- signals-scout-customer-analytics
- signals-scout-data-pipelines
- signals-scout-data-warehouse
- signals-scout-error-tracking
- signals-scout-experiments
- signals-scout-feature-flags
- signals-scout-general
- signals-scout-health-checks
- signals-scout-inbox-validation
- signals-scout-insight-alerts
- signals-scout-logs
- signals-scout-mcp-tool-calls
- signals-scout-observability-gaps
- signals-scout-product-analytics
- signals-scout-replay-vision
- signals-scout-revenue-analytics
- signals-scout-session-replay
- signals-scout-skills-store
- signals-scout-surveys
- signals-scout-tasks
- signals-scout-web-analytics
- signals-scout-web-vitals
- signals
- working-with-scouts
- skills-store
- working-with-skills
- managing-streamlit-apps
- writing-streamlit-apps
- creating-ai-subscription
- debugging-surveys
- working-with-task-comments
- exploring-apm-traces
- planning-voice-agent-user-interviews
- triaging-visual-review-runs
- auditing-warehouse-source-health
- diagnosing-failed-warehouse-syncs
- setting-up-a-custom-rest-source
- setting-up-a-data-warehouse-source
- suggesting-data-imports
- tuning-incremental-sync-config
- assessing-heatmaps
- exploring-live-traffic
- filtering-bot-traffic
- managing-path-cleaning-rules
- suggesting-path-cleaning-rules
- building-workflows
- designing-email-templates
- clickhouse-autoresearch-campaign
- check-posthog-loading
- simulate-new-user
- simulate-returning-user
- verify-posthog-instrumentation
- agents
- MCP
- commands
What's inside
Skills
156/analyzing-expensive-usersAnalyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend./creating-online-evaluationsAuthor continuously-running online evaluations in PostHog AI observability, grounded in real failure modes you've identified. Use when the user wants evaluations that automatically score new generations or whole traces going forward — "create an eval to catch X", "continuously/exploring-ai-failuresFind where an AI/LLM application is failing in production and surface the failure patterns, working from real traces. Use when someone wants to understand what's going wrong with an AI feature, find and categorize failure modes, triage errors, or investigate quality issues/exploring-llm-clustersInvestigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters./exploring-llm-costsInvestigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?",/exploring-llm-evaluationsInvestigate AI observability evaluations — `hog` (deterministic code-based), `llm_judge` (LLM-prompt-based), and `sentiment` (user-message sentiment). Find existing evaluations, inspect their configuration, run them against specific generations, query individual results, and
Show all 156 skillsShow fewer
/exploring-llm-tracesABSOLUTE MUST to debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/<id> or /ai-observability/sessions/<id>), asks to debug a trace, figure out what went wrong, check if an agent used a/feature-usage-feedSet up an LLM-judge evaluation that extracts canonical use cases for a PostHog feature at scale and streams the results to a Slack channel as a live feed. Use when someone wants to understand how users are actually using a specific AI/LLM-powered feature in production — what/downloading-batch-export-filesExport PostHog events, persons, or sessions on demand and download the resulting files. Use when the user asks to download/export raw PostHog data, create a one-off file export, fetch a Parquet or JSONLines export, or use the file_download_batch_exports API. Covers starting the/building-canvasesCreate or edit a PostHog canvas — a sandboxed browser application (data board, document, form, small tool, graphics experiment) stored in PostHog and rendered by the desktop/web app. Use when a task asks to build, generate, update, or fix a canvas, or when a canvas id is given/building-html-canvasesAuthor a PostHog canvas with semantic HTML, CSS, and direct browser APIs — documents, articles, generative graphics, 2D canvas and WebGL experiences, and focused experiments where React components add no useful structure. Use after building-canvases has routed a canvas request/building-react-quill-canvasesAuthor the React + Quill implementation of a PostHog canvas: the single-component contract, the allowed imports, Quill (PostHog's design system) component and composition rules, theme-aware design tokens, loading skeletons, and the in-canvas date picker. Use after/querying-canvas-dataGet PostHog data into a canvas correctly: the host-injected `ph` SDK (loadInsight, query, capture, openExternal, navigate), the data hierarchy (saved insights first, typed query nodes second, inline HogQL last), per-insight-type result shapes, date-range wiring, and event/validating-and-publishing-canvasesValidate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, waiting out the queued build, and recovering from/setting-up-support-slack-locallyConnect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Use when the user wants to test the conversations Slack integration locally, hits "Support Slack OAuth client ID is not/building-a-dashboardBuild a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics/charts together on one page, assemble a dashboard for a/setting-up-data-catalogPopulates and maintains a project's data catalog (semantic layer): canonical metrics, trust marks (certifications) on warehouse tables/views, and reviewed table relationships. Use when asked to set up / seed / bootstrap the data catalog or semantic layer, to catalog a project's/modeling-activation-metricsBuild reusable activation models — an activation-rate metric and a per-user/per-account activated flag — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to define, model, or measure activation, the "aha moment", onboarding/modeling-conversion-metricsBuild reusable conversion models — funnel/step conversion rates, drop-off, and time-to-convert — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute a conversion rate, funnel, step completion, drop-off,/modeling-dimension-tablesBuild reusable dimension / lookup tables for a star schema — country/region, timezone, currency, date, plan/product, and other descriptive attributes — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model dimension tables,/modeling-product-usage-metricsBuild reusable product-usage and engagement models — retention, stickiness, and lifecycle — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute whether users come back (retention / churn), how frequently/modeling-revenue-metricsBuild reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute recurring/modeling-warehouse-foundationsShared foundations for building reusable data models in PostHog, on either of two stacks: PostHog-native data-warehouse views / materialized views (HogQL, via the view-* MCP tools), or an external dbt project (sources.yml + staging/marts + schema tests) run against your own or/auditing-warehouse-view-healthAudit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks "which of my views are broken?", "why is this materialized view/canvas-templatesHow PostHog "canvas" dashboards work end-to-end — the two rendering tiers (json-render vs freeform React-in-iframe), the agent system prompts that steer each, and the RIGHT way to fetch PostHog data (typed query nodes through ph.query, not hand-rolled HogQL). Use when changing/onboarding-videosAdd, replace, and optimize the looping demo videos in the onboarding "welcome" bento grid (packages/ui/src/features/onboarding). Covers the ffmpeg compression workflow (the scripts/optimize-onboarding-videos.mjs wrapper), the faststart + right-size best practices that keep/quill-codeEdit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design/storybook-storiesWrite Storybook stories for PostHog UI components. Covers the provider stack stories run inside, the key gotcha that tRPC/useHostTRPC queries never resolve in Storybook (so data-fetching components render empty), and the pure-presentational split that makes a component/test-electron-appDrive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, snapshot the accessibility tree to verify changes, click/type/navigate, and screenshot the actual desktop app only when/mcp-serversInstall, configure, authenticate, and troubleshoot MCP (Model Context Protocol) servers for this agent. Use when the user asks to add/install/remove an MCP server, connect a tool like Linear/Sentry/Supabase/GitHub via MCP, set up mcp.json, or when MCP tools are failing or need/subagent-orchestrationHow and when to delegate work to subagents via the `subagent` tool (Explore, Plan, General). Use when a task involves codebase recon, implementation planning, or actual code changes that would benefit from an isolated context window instead of doing it all inline./dynamic-workflowsHow to write JavaScript workflow scripts for the `workflow` tool - fanning work out across many isolated subagents with agent(), parallel(), and pipeline(), then synthesizing one result. Use when a task decomposes into several independent investigations or changes (codebase/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/consuming-endpoints-from-client-codeWire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api/openapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling/copying-endpoints-across-projectsCopy a PostHog endpoint (a saved HogQL/insight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production,/creating-an-endpointCreate a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says "create an/diagnosing-endpoint-performanceDiagnose why a PostHog endpoint is slow or expensive and propose a concrete fix — bump the cache TTL, enable materialisation, restructure variables, or rewrite the query. Use when the user says "this endpoint is slow", "my endpoint times out", "we're hitting the cost cap on this/exploring-endpoint-execution-logsExplore and diagnose a PostHog endpoint's execution logs — error messages, failed runs, cache misses, slow runs, or unexpected row counts during endpoint invocations. Use when the user says "my endpoint is failing", "show me the logs for endpoint X", "what error did endpoint Y/managing-endpoint-versionsWork safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before/diagnosing-ci-and-merge-bottlenecksDiagnoses CI and pull-request pipeline health for a GitHub repo using the engineering analytics MCP tools — pull-requests (PR list with CI status), workflow-health (per-workflow CI trends), and pr-lifecycle (a single PR's timeline). Use when asked whether CI is getting faster or/investigating-ci-failuresInvestigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Use for "who broke master", "why did this test fail in CI", "is this failure my PR's fault or everyone's", "is this test flaky or actually broken", "when did this/turning-engineering-analytics-into-insightsConverts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains what data the product reads so it can be queried directly with SQL. The engineering analytics dashboard and MCP tools run curated HogQL privately over per-team/authoring-error-tracking-alertsAuthor error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection,/diagnosing-stacktrace-symbolicationHelp users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM). The PostHog symbol-set lookup flow is universal across platforms; build-tool and/grouping-noisy-errorsConsolidate PostHog error tracking issues that are the same actual error reported under different fingerprints. Use when the user asks "why do I have so many TypeError issues that look the same?", "merge these duplicates", "stop splitting this error into new issues", or wants to/investigating-error-issueInvestigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (`/error_tracking/<id>`) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release,/suppressing-noisy-errorsCreate PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks "stop capturing this error", "drop browser extension errors", "ignore ResizeObserver loops", "suppress bot-driven errors", or wants to reduce ingestion cost/triaging-error-issuesTriage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new/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/configuring-experiment-analyticsConfigures the analytics side of a PostHog experiment — exposure criteria (server-resolved default exposure event vs custom exposure events), primary and secondary metrics, the supported metric types (count, sum, ratio with `math` and `math_property`, retention with/configuring-experiment-rolloutConfigures the rollout shape of a PostHog experiment — the variant split (50/50, 80/20, A/B/C ratios), the overall rollout percentage that gates how many users enter the experiment, and the disambiguation when a percentage like "roll out to 25%" could mean either. Use when the/creating-experimentsGuides agents through the 3-step experiment creation flow: defining the hypothesis, configuring rollout, and setting up analytics. Delegates rollout decisions to configuring-experiment-rollout and metric setup to configuring-experiment-analytics.\nTRIGGER when: user asks to/diagnosing-experiment-resultsDiagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty / 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A/A, Bayesian vs/finding-experimentsResolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File/managing-experiment-lifecycleGuides experiment state transitions: launching, pausing, resuming, freezing/unfreezing exposure, ending, shipping variants, archiving, resetting, duplicating, and copying to another project. Covers preconditions, implications for variant assignment and analysis, and the decision/scanning-experiments-with-replay-visionProvisions a Replay Vision scanner scoped to one experiment's exposed sessions: derives the recordings filter from the experiment's exposure criteria (with session-linkability checks and honest fallbacks), templates a prompt that stays comparable across variants, sizes credit/cleaning-up-stale-feature-flagsIdentify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal/copying-flags-across-projectsCopy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace./finding-deleted-feature-flagsFind feature flags that were soft-deleted in the active project within a recent time window. Use when the user asks "what flags were deleted in the last N days", "show me recently deleted feature flags", "who deleted flag X", "audit recent flag deletions", or anything similar./diagnosing-sdk-healthDiagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, "SDK health", "SDK doctor" (the former name), or when events or features seem/resolving-ingestion-warningsDiagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or/authoring-log-alertsAuthor useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting,/investigating-logsInvestigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying. Use when the user asks to "check the logs", asks whether a service, deploy, release, or change is working or/testing-mcp-tools-locallySet up the local dev environment, seed data, and API keys to test the staff-only managed migrations MCP tools (managed-migrations-support-list, managed-migrations-support-get) end to end. Use when testing batch import support tooling, debugging MCP tool responses or discovery/debugging-mcp-analyticsDebug, support, and build PostHog MCP Analytics — product analytics for MCP servers (the `@posthog/mcp` and `posthog.mcp` SDKs plus the mcp_analytics product). Use when MCP analytics data looks wrong or missing ("events aren't showing", "intent clusters are empty", "sessions are/exploring-mcp-intent-clustersExplore PostHog MCP intent clusters — agent goals grouped by semantic similarity, with each cluster's tool distribution and error rates, plus the tool-centric pivot (capture rate per intent, discovery rate against the advertised catalog, description fit, tool overlaps). Use when/exploring-mcp-sessionsInvestigate individual PostHog MCP sessions — the sequence of tool calls a single agent made in one run, what it was trying to do, and where it went wrong. Use when the user asks "what did this MCP session do?", "show me the tool calls for session X", "what was the agent's/exploring-mcp-tool-qualityInvestigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow. Use when the user asks "which MCP tool has the highest error rate?", "what's the slowest tool?", "which tools fail most often?", "how reliable is tool X?", wants/exploring-mcp-tool-usageStarting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it. Use when the user asks "how is my MCP doing?", "what should I look at?", "explore my tool calls", "who uses my MCP tools?", "what are agents doing/improving-mcp-toolsRun an improve-my-MCP campaign: an autoresearch-style loop that measures the MCP agent experience with the eval harness, picks the highest-impact tool problem from production data, makes one bounded fix, and keeps it only if before/after scores improve. Use when asked to/investigating-metric-anomaliesInvestigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence. Use when asked why a metric looks wrong (ingestion lag rising, error rate spiking, latency degrading, queue/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./checking-deploy-timingDetermine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask "when was X deployed", "is my change live in the US/EU yet", "has my PR/managing-subscriptionsManage PostHog subscriptions — scheduled email, Slack, or webhook deliveries of insight or dashboard snapshots, optionally with an AI-written summary attached to each delivery. Use when the user wants to subscribe to an insight or dashboard, get an AI summary attached to those/querying-posthog-dataRequired reading before writing any HogQL/SQL or calling execute-sql against PostHog. Use whenever the user wants to search, find, or do complex aggregations PostHog entities (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse, persons,/writing-simplified-technical-englishWrite English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any/choosing-trend-or-slope-viewClarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — "how much did X change from A to B", "before vs after", "start vs end", "week/exploring-autocapture-eventsGuides exploration of $autocapture events captured by posthog-js to understand user interactions, find CSS selectors (especially data-attr attributes), evaluate selector uniqueness, query matching clicks ad-hoc, and create actions. Use when the user asks about autocapture data,/formatting-insight-axesPick the right y-axis unit when creating or updating a TrendsQuery insight via `posthog:insight-create` or `posthog:insight-update`. Use when the agent is about to add a `formula` purely to convert units (e.g. dividing seconds by 60 to display minutes), when a `math_property` is/investigate-metricDiagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel,/managing-remindersCreate and manage PostHog reminders — private, human-paced nudges that fire as in-app notifications on a schedule, optionally linked to a PostHog resource. Use when the user says "remind me to…", wants a one-off or recurring nudge (daily/weekly/monthly/yearly, a cron schedule,/debugging-local-replayDebugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local/diagnosing-missing-recordingsDiagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic/finding-replay-for-issueFinds the most informative session recording linked to an error tracking issue. Use when a user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred. Ranks linked sessions by recency, activity score, and journey/finding-sessions-to-watchGuides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start/investigating-replayInvestigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors/creating-replay-vision-scannersGuides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating observation volume and checking the org's monthly quota/exploring-replay-vision-observationsGuides agents through pulling a Replay Vision scanner's observations, reading the findings, and acting on them — summarizing patterns across sessions, drilling into individual recordings, and turning real, corroborated issues into PostHog tasks, insights, or an/review-hog-authoringHow to author custom ReviewHog skills — the review perspectives, blind-spot checks, and validation criteria that drive ReviewHog's automated PR reviews. Use when a user wants a new review perspective (a specialist lens on their PRs), a custom blind-spot sweep, or their own/review-hog-blind-spots-generalThe general blind-spot check for ReviewHog — the final sweep that runs after every enabled review perspective has reviewed a chunk. Hunts for real, high-value issues that ALL of the perspectives missed, conditioned on what they actually found; returns an empty list over padding./review-hog-perspective-contracts-securityThe Contracts & Security review perspective for ReviewHog. Verifies that changed code is safe and maintains compatibility — API contracts and breaking changes, injection / authz / data exposure, input validation, and schema / interface alignment. Reports security and contract/review-hog-perspective-logic-correctnessThe Logic & Correctness review perspective for ReviewHog. Verifies that changed code does what it is supposed to do — business logic, edge cases, data transformations, and query / data-access correctness. Reports correctness issues only; security and performance are separate/review-hog-perspective-performance-reliabilityThe Performance & Reliability review perspective for ReviewHog. Verifies that changed code will perform and hold up in production — resource efficiency, error handling and recovery, scalability, and operational readiness. Reports performance and reliability issues only./review-hog-validation-criteriaThe validation criteria for ReviewHog — the bar for deciding whether a flagged PR issue is worth keeping. Keeps real, user-affecting correctness / security / data-loss / contract / performance problems; drops overengineering, speculation, paranoia, never-gonna-happen edge cases,/authoring-scoutsHow to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak/debugging-signals-pipelineDebug the signals pipeline locally end-to-end. Covers emitting test signals from fixtures, monitoring Temporal workflows via the REST API, reading sandbox agent logs from object storage, inspecting Docker sandbox containers, and diagnosing common failures (stale ClickHouse/exploring-scoutsHow to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers/inbox-explorationExplore PostHog's Inbox and act on what it surfaces — the place where signal reports cluster into actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?", asks about/signals-scout-ai-observabilitySignals scout for PostHog AI observability. Watches LLM traces for cost, latency, error, volume, and eval-performance regressions, sliced by the dimensions it discovers over time, and files each validated regression as a report in the inbox./signals-scout-anomaly-detectionSignals scout that watches a project's most-viewed dashboards and insights for recent anomalies — bursts, drops, flat-lines, and trend breaks scored against each insight's own seasonality-matched baseline. Files each anomaly as a finished 1:1 inbox report on the report channel/signals-scout-apmSignals scout for PostHog distributed tracing (APM / OpenTelemetry spans). Watches RED metrics per (service, operation) — error rate, p95 latency, request volume — for regressions, new error signatures, and traffic cliffs, and files each validated regression as a report in the/signals-scout-conversationsSignals scout for the PostHog Conversations (support inbox) product. Watches the `$conversation_*` ticket-lifecycle events for support-delivery regressions — SLA breach-rate steps, first-response latency blowouts, backlog inflow-vs-resolution imbalance, and channel / assignment/signals-scout-csp-violationsSignals scout for Content Security Policy violation reports. Watches `$csp_violation` events for blocked-URL clusters, per-directive bursts, post-deploy regressions, and suspicious third-party domains, and files each validated cluster as a report in the inbox./signals-scout-customer-analytics-billing-and-usageSignals scout for per-account product-mix shifts. Watches each staked account's usage and forecasted MRR at the product grain for one product dropping or spiking against its own same-weekday trailing baseline while the account total holds — the shape account-level monitoring is/signals-scout-customer-analyticsSignals scout for PostHog Customer analytics (Accounts). Watches per-account engagement for churn-risk shapes — engagement cliffs, dormancy, champion departure — and the expansion inverse, weighted by commercial ownership, and files each validated risk as a report in the inbox./signals-scout-data-pipelinesSignals scout for PostHog data pipelines — CDP destinations and transformations, batch exports, and hog flows. Watches for delivery failures, degraded functions, and stalled exports against each pipeline's baseline, and files each validated delivery contradiction as a report in/signals-scout-data-warehouseFocused Signals scout for PostHog projects importing external data into the warehouse. Watches the import side — external data sources, per-table sync schemas, webhook push channels, and materialized views — for the moments an import quietly stops keeping its promise: a source/signals-scout-error-trackingSignals scout for PostHog error tracking. Watches `$exception` bursts, stuck loops, multi-fingerprint clusters, and status regressions, and files each validated issue as a report in the inbox./signals-scout-experimentsSignals scout for PostHog A/B experiments. Watches running experiments for validity threats (sample ratio mismatch, contamination, exposure stalls, mid-run flag mutations) and lifecycle drift (zombies, decided-but-running), and files each validated validity threat as a report in/signals-scout-feature-flagsSignals scout for PostHog feature flags. Watches the flag roster and the `$feature_flag_called` stream for evaluation cliffs, ghost flags, response-distribution shifts, and flag debt, and files each validated contradiction as a report in the inbox./signals-scout-generalCross-product Signals scout. Looks for cross-product correlations and explores the surfaces the per-product specialist scouts don't cover./signals-scout-health-checksSignals scout over PostHog's own health checks. Reads the project's active health issues, bundles them by kind, weights by blast radius, and files the ones genuinely worth acting on as reports in the inbox./signals-scout-inbox-validationFollow-up Signals scout for the inbox itself. After a deployment soak window, re-measures the problems behind recently resolved reports and files a report when a fix didn't hold, plus a gated escalation check on dismissed reports./signals-scout-insight-alertsSignals scout over a project's own configured insight alerts. Reads each alert's recent firing history and files a report for the firings a human likely missed — especially ones the standard notification path stayed silent on./signals-scout-logsSignals scout for PostHog logs. Watches for emerging and rate-shifted message patterns (window-over-window deltas), volume bursts, severity-distribution shifts, service silence, and trace-correlated bursts./signals-scout-mcp-tool-callsSignals scout for PostHog MCP tool calls. Watches $mcp_tool_call telemetry for tools that need improvement — high, broad-reach failure rates, retry/hammering that betrays a confusing schema, slow or context-bloating responses — groups problem tools by $mcp_tool_category (the/signals-scout-observability-gapsSignals scout for observability gaps — significant event volumes with no insight, dashboard, or alert coverage. Files a report recommending new insights, dashboards, or alerts as the team's product evolves./signals-scout-product-analyticsSignals scout for core product-analytics flows — funnels, retention, lifecycle, stickiness, and paths. Watches the team's saved flows for a derived-rate regression (conversion or retention sliding) while entrants hold, and files it as a report in the inbox./signals-scout-replay-visionSignals scout for PostHog Replay Vision scanners. Watches that enabled scanners keep observing (throughput / quota cliffs) and that what they see in aggregate gets surfaced (score shifts, recurring themes across sessions), and files each validated finding as a report in the/signals-scout-revenue-analyticsSignals scout for PostHog revenue analytics. Watches for upstream failures (Stripe sync stalls, capture regressions), config drift, and goal-miss escalations, and files each validated finding as a report in the inbox./signals-scout-session-replaySignals scout for PostHog session replay. Watches that sessions keep recording (capture cliffs) and that friction inside recordings — rage/dead-click clusters, error-after-interaction cohorts — gets surfaced, and files each validated cliff or cluster as a report in the inbox./signals-scout-skills-storeSkill-hygiene scout for the team's PostHog skills store, read entirely via the MCP skill tools. Watches recently-changed skills — plus a slow rotation over the most-used, highest-leverage ones — for statically-verifiable authoring violations: vague descriptions, bloated bodies,/signals-scout-surveysSignals scout for PostHog surveys. Watches active surveys for score regressions, response-volume drops, abandonment spikes, and targeting drift, and aggregates open-text responses into recurring themes — filing each as a report in the inbox./signals-scout-tasksSignals scout for PostHog Tasks, the agent work items a project runs. Two lenses: delivery health (runs failing, clustered by repository and error class, and retry storms) every run, and on a slower rotation demand (recurring asks across human-authored tasks that point at a/signals-scout-web-analyticsSignals scout for PostHog web traffic. Watches per-channel session volume, attribution breakage, and landing-page health (bounce / 404 steps) against the site's own baseline, and files each validated divergence as a report in the inbox. Per-page web vitals have their own/signals-scout-web-vitalsFocused Signals scout for PostHog projects capturing Core Web Vitals (`$web_vitals`). Watches each page's p75 LCP / INP / CLS / FCP against the absolute Google thresholds (good / needs-improvement / poor) and against its own history: pages standing in the poor band, pages/signalsHow to query the document_embeddings table for raw signal data using HogQL. Use when you need to perform semantic search over signals, fetch every signal that contributed to a specific report, or list signal types. For browsing the curated report layer (the Inbox) — listing/working-with-scoutsHow to get real jobs done with PostHog Signals scouts — the scheduled agents that watch a project and write reports into the Signals inbox — and how to steer and customize the fleet over time. Use when a user wants to delegate a watching job ("have a scout keep an eye on X",/skills-storeDiscover and use shared team skills stored in PostHog. Use when the user asks to list, browse, load, or manage "shared skills", "team skills", or references the "skills store" / "skill store"./working-with-skillsBest practices for agents managing PostHog skills via the MCP `skill-*` tools — how to discover, read, create, update, and refactor skills efficiently, especially large skills with many bundled files. Use whenever you are about to call any `skill-*` tool, asked to author or edit/managing-streamlit-appsCreate, deploy, and operate Streamlit apps in PostHog via the streamlit-apps MCP tools — create an app, set its source, start and stop its sandbox, poll status, list versions, delete, and share the app with humans via its PostHog URL. Use when asked to "create a streamlit app",/writing-streamlit-appsWrite Streamlit app source code that runs well in a PostHog sandbox — the posthog_apps.query() bridge for reading PostHog data, the packages baked into the sandbox image, caching and session state across Streamlit reruns, layout and chart patterns, and single-file app.py/creating-ai-subscriptionCreate a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather/debugging-surveysDebug, support, and build PostHog Surveys across the backend and all five SDKs (web/posthog-js, iOS, Android, Flutter, React Native). Use whenever a Surveys support ticket is pasted ("survey not showing", "fewer responses than expected", "responses disappeared", "survey shows on/working-with-task-commentsRead and use comments attached to the current PostHog task, its artifacts, and its canvases through the PostHog MCP exec dispatcher. Use when the user mentions task comments, artifact or canvas comments, annotations, selected-text feedback, replies, unresolved comments, or asks/exploring-apm-tracesInvestigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP. Use when the user asks about service traces, slow HTTP/database spans, error spans, error-rate trends or spikes, latency distributions, trace IDs, or span attributes — not AI/planning-voice-agent-user-interviewsPlan a round of user interviews conducted by PostHog''s AI voice agent (a "robo interviewer") — the automated voice-agent interview product. Captures a UserInterviewTopic (who to target, what to ask, framing context, question list) and calls user-interview-topics-create. ONLY/triaging-visual-review-runsInspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", asks why a PR is blocked or what changed visually,/auditing-warehouse-source-healthAudit the health of a PostHog project's data warehouse sources and syncs — find every broken or degraded source connection, sync schema, and webhook channel. Use when the user asks "why are my imports failing?", "what's broken with my sources?", "why is my warehouse data/diagnosing-failed-warehouse-syncsDiagnose why a data warehouse sync is failing and recommend the right recovery action. Use when the user asks "why isn't my Stripe/Postgres/Hubspot sync working?", "this table has been stuck for hours", "the data in the warehouse looks wrong", or wants to troubleshoot a specific/setting-up-a-custom-rest-sourceConnect an arbitrary REST API to the PostHog data warehouse as a Custom source by authoring a JSON manifest, with no per-source code. Use when the user points at an API that has no built-in PostHog connector — "import data from this REST API", "sync my internal API", "connect/setting-up-a-data-warehouse-sourceGuide the user through connecting a new data warehouse source — Postgres, MySQL, Stripe, Hubspot, MongoDB, Salesforce, BigQuery, Snowflake, and so on. Use when the user wants to "connect Stripe", "import data from Postgres", "add a new data source", "sync my warehouse tables",/suggesting-data-importsUse when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, ad spend, production database tables, or other data PostHog does not collect natively — or wants to join or correlate PostHog product events with that external business data. Also/tuning-incremental-sync-configChange the sync configuration of an existing data warehouse schema — switch sync_type, pick a different incremental_field, set primary_key_columns, choose cdc_table_mode, or change sync_frequency. Use when the user asks "switch my orders table from full refresh to incremental",/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/exploring-live-trafficInspects PostHog Web analytics Live tab data — current users online, last-30-minutes pageviews, top pages, referrers, devices, browsers, countries, bot traffic, and the per-minute bot/users charts. Use when the user asks "who is on my site right now?", "what is happening live?",/filtering-bot-trafficIdentify, measure, and exclude bot / crawler / AI-agent traffic in PostHog web and product analytics using the traffic classification surface (the isLikelyBot / getTrafficType HogQL functions and the $virt_* virtual properties). Use when the user asks to "exclude bots", "filter/managing-path-cleaning-rulesInspects URL paths and proposes, tests, orders, and applies project-level path cleaning rules so dynamic segments (numeric IDs, UUIDs, slugs, dates) collapse into readable aliases. Use when the user says "clean the paths", "normalize URLs", "group similar pages", "too many/suggesting-path-cleaning-rulesRuns and reasons about the automated AI health check that suggests path-cleaning rules for web-analytics teams. Use when asked to generate path-cleaning suggestions for a team or cohort, to run the suggestion check, to review/apply AI-suggested rules, to inspect/building-workflowsBuild, edit, test, enable, and monitor PostHog workflows over MCP. Author the action/edge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow,/designing-email-templatesAuthor, save, and edit email templates in the PostHog workflows library — compose email design JSON with Liquid personalization and create and round-trip-edit templates over MCP. Use when asked to design, build, update, or fix an email template for workflows, broadcasts, or/clickhouse-autoresearch-campaignRun a ClickHouse query optimization campaign on one git branch using pi-autoresearch, dynamic lanes and hypotheses, baseline result capture, correctness checks, and stagnation-aware lane/campaign review./check-posthog-loadingInspect how the PostHog JavaScript SDK is loaded across a list of URLs. Use to confirm consistent installation across pages, find pages missing the snippet, detect mismatched API keys or hosts between pages, and verify the load method (head snippet vs deferred vs array.js)./simulate-new-userSend synthetic first-time-visitor traffic to a URL and confirm that PostHog $pageview events fire. Use when a customer wants to verify that anonymous visitor tracking works, after deploying instrumentation changes, or when debugging "events not arriving" reports./simulate-returning-userSend synthetic single-session multi-page traffic to a URL and confirm PostHog $pageview events fire across page views. Use when verifying that cookies persist correctly, that the same distinct_id is reused across navigations, or when debugging session-stitching issues./verify-posthog-instrumentationUse this skill to verify that PostHog instrumentation is firing correctly on a website. Drives a real browser at one or more URLs, observes which PostHog events actually arrive, and reports a pass/fail summary. Use after installing the PostHog SDK on a site, after a deploy that
Agents
11access-controlPostHog access control system implementation expert - use when adding access controls to new products, debugging access control issues, or questions about RBAC patternsactivity-log-expertUse this agent proactively when working with PostHog's comprehensive activity logging system, including implementing activity logging for new entities, debugging logging issues, optimizing performance, creating activity describers, extending audit trail functionality, or anycode-reviewerUse this agent when you need expert code review of recently written or modified code. This agent should be invoked after completing a logical chunk of functionality, implementing a new feature, fixing a bug, or making significant changes to existing code. The agent focuses onpipeline-composition-doctorIngestion pipeline composition convention checker. Use when assembling pipelines, choosing concurrency modes, composing subpipelines, adding branching, retries, or grouping — covers builder chain order, cardinality, and composition patterns. Examples: <example> Context:pipeline-result-doctorIngestion pipeline result handling convention checker. Use when working with result constructors (ok/dlq/drop/redirect), side effects, or ingestion warnings. Examples: <example> Context: Developer wants to check their error handling. user: "Check if my result handling followspipeline-step-doctorIngestion pipeline step convention checker. Use when writing, reviewing, or refactoring individual pipeline steps — covers factory pattern, type extension, config injection, and naming conventions. Examples: <example> Context: Developer wrote a new processing step. user: "Review
Show all 11 agentsShow fewer
pipeline-testing-doctorIngestion pipeline testing convention checker. Use when writing, reviewing, or debugging tests for pipeline steps or pipelines — covers test helpers, assertion patterns, fake timers, and doc-test style. Examples: <example> Context: Developer wants tests reviewed. user: "Reviewprompt-engineerUse this agent when you need to create, refine, or optimize prompts for LLMs. This includes designing new prompts from scratch, debugging problematic prompts, improving prompt reliability and consistency, establishing prompt patterns for specific domains, or converting vagueresource-duplicationResource duplication expert - use when configuring a resource to be copied between projects.systematic-debuggerUse this agent when you need to diagnose and fix bugs, errors, or unexpected behavior in code. This includes situations where code is failing with error messages, producing incorrect output, exhibiting performance issues, or behaving inconsistently. The agent excels attest-writerUse this agent when you need to write comprehensive test suites for existing code or when implementing test-driven development. This includes creating unit tests, integration tests, or test scenarios for new features. The agent excels at identifying edge cases, writing clear
Badges
6
README
1PostHog is the open source platform for building self-driving products
PostHog provides every tool you need to build a successful product, and captures all the context agents need to proactively diagnose problems, uncover opportunities, and ship fixes:
- Self-driving mode: Turn signals in your product data (errors, rage clicks, failed queries, and more) into researched reports and pull requests you review and merge.
- Product analytics: Autocapture or manually instrument event-based analytics to understand user behavior and analyze data with visualization or SQL.
- Web analytics: Monitor web traffic and user sessions with a GA-like dashboard. Easily monitor conversion, web vitals, and revenue.
- Session replays: Watch real user sessions of interactions with your website or mobile app to diagnose issues and understand user behavior.
- Feature flags: Safely roll out features to select users or cohorts with feature flags.
- Experiments: Test changes and measure their statistical impact on goal metrics. Set up experiments with no-code too.
- Error tracking: Track errors, get alerts, and resolve issues to improve your product.
- Logs: Ingest, search, and analyze log data alongside the rest of your product data.
- Surveys: Ask anything with our collection of no-code survey templates, or build custom surveys with our survey builder.
- Data warehouse: Sync data from external tools like Stripe, Hubspot, your data warehouse, and more. Query it alongside your product data.
- Data pipelines: Run custom filters and transformations on your incoming data. Send it to 25+ tools or any webhook in real time or batch export large amounts to your warehouse.
- AI observability: Capture traces, generations, latency, and cost for your LLM-powered app.
- Workflows: Create workflows that automate actions or send messages to your users.
You can steer it all from Slack, web, desktop (PostHog Desktop), or your own editor via the MCP.
Best of all, all of this is free to use with a generous monthly free tier for each tool. Get started by signing up for PostHog Cloud US or PostHog Cloud EU.
Table of Contents
- PostHog is the open source platform for building self-driving products
- Table of Contents
- Getting started with PostHog
- PostHog Cloud (Recommended)
- Self-hosting the open-source hobby deploy (Advanced)
- Setting up PostHog
- Learning more about PostHog
- Contributing
- Open-source vs. paid
- We’re hiring!
Getting started with PostHog
PostHog Cloud (Recommended)
The fastest and most reliable way to get started with PostHog is signing up for free to PostHog Cloud or PostHog Cloud EU. Your first 1 million events, 5k recordings, 1M flag requests, 100k exceptions, and 1500 survey responses are free every month, after which you pay based on usage.
Self-hosting the open-source hobby deploy (Advanced)
If you want to self-host PostHog, you can deploy a hobby instance in one line on Linux with Docker (recommended 4GB memory):
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/posthog/posthog/HEAD/bin/deploy-hobby)"
Open source deployments should scale to approximately 100k events per month, after which we recommend migrating to a PostHog Cloud.
We do not provide customer support or offer guarantees for open source deployments. See our self-hosting docs, troubleshooting guide, and disclaimer for more info.
Setting up PostHog
Once you've got a PostHog instance, you can set it up by installing our JavaScript web snippet, one of our SDKs, or by using our API. You can also connect the MCP to bring PostHog into Claude Code, Cursor, or any MCP-compatible agent.
We have SDKs and libraries for popular languages and frameworks like:
| Frontend | Mobile | Backend |
|---|---|---|
| JavaScript | React Native | Python |
| Next.js | Android | Node |
| React | iOS | PHP |
| Vue | Flutter | Ruby |
Beyond this, we have docs and guides for Go, .NET/C#, Django, Angular, WordPress, Webflow, and more.
Once you've installed PostHog, see our product docs for more information on how to set up product analytics, web analytics, session replays, feature flags, experiments, error tracking, surveys, data warehouse, and more.
Learning more about PostHog
Our code isn't the only thing that's open source 😳. We also open source our company handbook which details our strategy, ways of working, and processes.
Curious about how to make the most of PostHog? We wrote a guide to winning with PostHog which walks you through the basics of measuring activation, tracking retention, and capturing revenue.
Contributing
We <3 contributions big and small:
- Vote on features or get early access to beta functionality in our roadmap
- Open a PR (see our instructions on developing PostHog locally)
- Submit a feature request or bug report
For an overview of the codebase structure, see monorepo layout and products.
Open-source vs. paid
This repo is available under the MIT expat license, except for the ee directory (which has its license here) if applicable.
Need absolutely 💯% FOSS? Check out our posthog-foss repository, which is purged of all proprietary code and features.
The pricing for our paid plan is completely transparent and available on our pricing page.
We're hiring!
Hey! If you're reading this, you've proven yourself as a dedicated README reader.
You might also make a great addition to our team. We're growing fast and would love for you to join us.
File tree
1684posthog/posthogView on GitHub
.agents/
owners.yaml
security.md
skills/
adding-inbox-sources/
SKILL.md
adding-ingestion-warnings/
SKILL.md
adding-mcp-store-servers/
SKILL.md
adding-personhog-rpc/
references/
database-indexes.md
proto-conventions.md
SKILL.md
adding-product-alerting/
references/
adopting-platform-alerting.md
architecture.md
extending-platform-alerting.md
frontend-alerting.md
SKILL.md
adding-project-secret-api-key-auth/
SKILL.md
adopting-generated-api-types/
references/
migration-patterns.md
type-compatibility.md
SKILL.md
analyzing-experiment-query-performance/
SKILL.md
analyzing-insights-across-teams/
SKILL.md
auditing-llm-gateway-parity/
SKILL.md
auditing-warehouse-source-coverage/
scripts/
dump_source_inventory.py
SKILL.md
authoring-ci-workflows/
SKILL.md
autoresolving-pr-conflicts/
references/
loop-setup.md
scripts/
autoresolve-marker.sh
regen-artifacts.sh
SKILL.md
building-product-empty-states/
SKILL.md
clickhouse-migrations/
SKILL.md
debugging-ci-failures/
SKILL.md
debugging-local-task-agent-runs/
SKILL.md
depot-container-builds/
SKILL.md
UPSTREAM.md
depot-github-runners/
SKILL.md
UPSTREAM.md
django-migrations/
SKILL.md
django-startup-time/
SKILL.md
documenting-warehouse-sources/
SKILL.md
establishing-code-ownership/
SKILL.md
extending-personhog-test-harness/
SKILL.md
finding-llm-gateway-migration-candidates/
SKILL.md
fixing-flaky-tests/
SKILL.md
gating-production-deploys/
SKILL.md
generating-clickhouse-query-performance-reports/
references/
hogql-deep-dive.md
materialization-analysis.md
query-patterns.md
SKILL.md
hogli/
SKILL.md
implementing-agent-modes/
SKILL.md
implementing-mcp-tools/
SKILL.md
implementing-mcp-ui-apps/
SKILL.md
implementing-warehouse-sources/
references/
oauth-app-deployment.md
SKILL.md
improving-drf-endpoints/
references/
common-anti-patterns.md
quick-reference-table.md
serializer-fields.md
viewset-annotations.md
SKILL.md
ingestion-pipeline-doctor-nodejs/
SKILL.md
instrumenting-first-party-metrics/
SKILL.md
isolating-product-facade-contracts/
SKILL.md
manage-dashboard-widgets/
references/
architecture.md
availability-and-gating.md
checklist-new-widget-type.md
composition.md
config-and-codegen.md
layout-and-ux.md
list-widget-patterns.md
live-widgets.md
managing-existing-widgets.md
mcp.md
permissions-and-sharing.md
skill-maintenance.md
widget-intake.md
SKILL.md
managing-github-actions-secrets/
SKILL.md
merging-prs/
SKILL.md
migrating-llm-gateway-callers/
references/
migration-examples.md
SKILL.md
modifying-taxonomic-filter/
references/
architecture.md
call-sites-and-blast-radius.md
common-pitfalls.md
refreshing-product-reality.md
testing-patterns.md
SKILL.md
monitoring-capture-service/
references/
investigation-playbooks.md
SKILL.md
monitoring-ingestion-pipeline/
references/
investigation-playbooks.md
SKILL.md
optimizing-clickhouse-and-hogql-queries/
references/
investigation-playbook.md
learnings.md
SKILL.md
owners.yaml
playwright-test/
SKILL.md
porting-code-prs/
SKILL.md
posthog-desktop/
SKILL.md
qa-frontend/
references/
browser-mcp-patterns.md
cleanup.md
evidence-and-output.md
expected-behavior.md
file-classification.md
pr-comment-template.md
route-finding.md
safety-rules.md
stack-and-login.md
test-case-design.md
scripts/
annotate-evidence.py
cursor-overlay.js
SKILL.md
qa-team/
references/
incident-patterns.md
personas.md
scripts/
build_launch_scripts.js
claim_persona.sh
SKILL.md
query-clickhouse-via-metabase/
SKILL.md
querying-local-postgres/
SKILL.md
querying-tophog/
SKILL.md
react-doctor/
SKILL.md
reviewing-personhog-protocol/
references/
personhog-invariants.md
SKILL.md
run-posthog/
SKILL.md
running-ci-preflight/
SKILL.md
scene-menu-bar/
SKILL.md
security-audit/
SKILL.md
sending-notifications/
SKILL.md
setting-feature-flags-in-storybook/
SKILL.md
setting-up-devbox/
SKILL.md
setup-web-tests/
SKILL.md
stacking-prs/
SKILL.md
survey-sdk-audit/
SKILL.md
triaging-web-analytics-support/
references/
diagnostic-playbooks.md
loading-audit.md
ticket-queries.md
SKILL.md
using-kea-disposables/
SKILL.md
visualizing-change-over-time/
SKILL.md
warehouse-source-new-version/
SKILL.md
writing-clickhouse-queries/
SKILL.md
writing-code-comments/
SKILL.md
writing-evals/
references/
authoring-reference.md
running-evals.md
SKILL.md
writing-kea-logics/
references/
anti-patterns.md
connecting-logics.md
forms.md
keyed-logics.md
loading-data.md
persisting-state.md
polling.md
reacting-to-changes.md
routing.md
state-decision.md
testing.md
SKILL.md
writing-pr-descriptions/
references/
examples.md
SKILL.md
writing-skills/
SKILL.md
writing-tests/
references/
mistakes-we-make.md
SKILL.md
writing-user-facing-copy/
SKILL.md
.claude/
agents/
access-control.md
activity-log-expert.md
code-reviewer.md
ingestion/
pipeline-composition-doctor.md
pipeline-result-doctor.md
pipeline-step-doctor.md
pipeline-testing-doctor.md
prompt-engineer.md
resource-duplication.md
systematic-debugger.md
test-writer.md
commands/
conventions.md
hooks/
install-tool-versions.sh
setup-cloud.sh
setup-code-signing.sh
setup-flox.sh
rules/
clickhouse-migrations.md
django-migrations.md
drf-endpoints.md
generated-api-types.md
kea-disposables.md
product-isolation.md
proto-changes.md
semantic-line-breaks.md
storybook-feature-flags.md
tach-boundaries.md
temporal-workflow-versioning.md
writing-tests.md
settings.json
skills
.codex/
config.toml
environments/
environment.toml
run-with-dotenv.py
with-flox
.config/
.markdownlint-cli2.jsonc
.cursor/
environment.json
rules/
django-python.mdc
react-typescript.mdc
rust.mdc
.cursorignore
.cursorrules
.dagster_home/
.gitkeep
dagster.yaml
workspace.yaml
.depot/
actions/
pnpm-install/
action.yml
setup-python-cached/
action.yml
setup-sqlx-cli/
action.yml
workflows/
ci-backend-update-test-timing.yml
ci-backend.yml
.dockerignore
.editorconfig
.env.development
.env.example
.env.local.example
.env.services
.envrc
.flox/
.gitignore
env/
env.json
direnv-setup.sh
manifest.toml
on-activate.sh
.git-blame-ignore-revs
.gitattributes
.github/
.pinact.yaml
actionlint.yaml
actions/
build-n-cache-image/
action.yml
commit-snapshots/
action.yml
desktop-build-agent-release/
action.yml
desktop-restore-turbo-cache/
action.yml
docker-meta/
action.yml
get-pr-labels/
action.yml
paths-filter/
__tests__/
csv-escape.test.ts
filter.test.ts
git.test.ts
shell-escape.test.ts
.eslintignore
.eslintrc.json
.gitattributes
.prettierignore
.prettierrc.json
action.yml
dist/
index.js
jest.config.js
LICENSE
package-lock.json
package.json
README.md
src/
file.ts
filter.ts
git.ts
list-format/
csv-escape.ts
shell-escape.ts
main.ts
tsconfig.json
pnpm-install/
action.yml
rust-compute-affected/
action.yml
setup-emsdk/
action.yml
setup-protoc/
action.yml
setup-python-cached/
... 1600 moreShowing a partial view of a very large repo.
More Flows by @posthog.
@posthogVerifiedPlugin
Development
posthog
Official PostHog plugin for AI clients. Access PostHog products directly from your AI coding tool.
131 skills
@posthogFAQ
posthog is a Claude Code plugin with 156 hand-picked skills for data work, indexed on Flowy. Install it with the command on its page. It includes analyzing-expensive-users, creating-online-evaluations, exploring-ai-failures. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is posthog?
- :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
- How do I install posthog?
- Run these in Claude Code: npx -y skills add posthog/posthog --agent claude-code. Then prompt normally.
- Does posthog auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is posthog free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.