Agent Skills

by posthog

Diagnoses 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 signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.

feature-flags-react-native

by posthog

PostHog feature flags for React Native applications

managing-experiment-lifecycle

by posthog

Guides 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 framework for when to use each action. TRIGGER when: user asks to launch, pause, resume, end, ship, archive, reset, duplicate, or copy an experiment to another project, or to freeze/unfreeze exposure (stop enrolling new users while metrics keep flowing, or reopen enrollment). DO NOT TRIGGER when: user is creating an experiment (use creating-experiments), configuring rollout (use configuring-experiment-rollout), or setting up metrics (use configuring-experiment-analytics).

exploring-autocapture-events

🔥🔥🔥✓ VerifiedFreeAdvanced setup

by posthog

Guides 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, wants to find what users are clicking, needs to build actions from click events, asks about elements_chain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties autocapture sends, or asks how to filter $autocapture events. Only applies to projects using posthog-js autocapture.

feature-flags-android

by posthog

PostHog feature flags for Android applications

error-tracking-svelte

by posthog

PostHog error tracking for Svelte

logs-datadog

by posthog

PostHog logs for Datadog

integration-react-tanstack-router-code-based

by posthog

PostHog integration for React applications using TanStack Router with code-based routing

feature-flags-react

by posthog

PostHog feature flags for React applications

integration-python

by posthog

PostHog integration for any Python application using the Python SDK

feature-flags-ruby

by posthog

PostHog feature flags for Ruby applications

feature-flags-go

by posthog

PostHog feature flags for Go applications

error-tracking-react-native

by posthog

PostHog error tracking for React Native

error-tracking-nuxt

by posthog

PostHog error tracking for Nuxt

integration-react-react-router-7-data

by posthog

PostHog integration for React Router v7 - Data mode applications

error-tracking-node

by posthog

PostHog error tracking for Node.js

integration-react-react-router-7-framework

by posthog

PostHog integration for React Router v7 - Framework mode applications

error-tracking-nextjs

by posthog

PostHog error tracking for Next.js

error-tracking-angular

by posthog

PostHog error tracking for Angular

feature-flags-api

by posthog

PostHog feature flags for API applications

authoring-log-alerts

by posthog

Author 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, back-testing via simulate, and shipping with a notification destination.

exploring-llm-costs

by posthog

Investigate 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?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.

exploring-apm-traces

by posthog

Investigates 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, trace IDs, or span attributes — not AI observability traces or product logs. Uses posthog:query-apm-spans, posthog:apm-trace-get, posthog:apm-services-list, posthog:apm-attributes-list, and posthog:apm-attribute-values-list.