posthog
197 Skills avec une documentation substantielle et des sources vérifiées. Ouvrez une fiche pour lire les instructions originales et vérifier le paquet et son installation.
posthogdiagnosing-ci-and-merge-bottlenecks
Diagnoses 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 slower, which GitHub Actions workflow is the slow or flaky long-pole, how long PRs take from open to merge, how an author's merge time compares to the cohort, which open PRs have failing or pending CI, or where a specifi
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogdiagnosing-endpoint-performance
Diagnose 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 one", or asks "should I materialise this?". Focuses on a single named endpoint, not a project-wide audit.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogdiagnosing-stacktrace-symbolication
Help 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 artifact details live in per-platform references (JavaScript is fleshed out, others come as we encounter them). Use when stack frames stay minified or obfuscated after symbols are uploaded, PostHog symbol sets show lastused bu
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogexploring-autocapture-events
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 elementschain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties autoc
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogexploring-live-traffic
Inspects 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?", "what bots are crawling me?", asks about the "live tab" / "live dashboard", wants live numbers (last 30 min), or wants help filtering or drilling into the live view. Also covers building product-analytics insights that m
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogexploring-llm-clusters
Investigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogexploring-llm-evaluations
Investigate AI observability evaluations — hog (deterministic code-based), llmjudge (LLM-prompt-based), and sentiment (user-message sentiment). Find existing evaluations, inspect their configuration, run them against specific generations, query individual results, and set up scheduled reports on an evaluation. Use when the user asks to debug why an evaluation is failing, surface common failure modes, compare results across filters, dry-run a Hog evaluator, prototype a new LLM-judge prompt, inspe
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogexploring-llm-traces
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/ or /ai-observability/sessions/ ), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against events.properties.$aiinput / $aioutputchoices returns empty — message
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogexploring-scouts
How 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 surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, r
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogfeature-usage-feed
Set 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 they're investigating, what questions they're trying to answer, and what patterns surface — without manually reading hundreds of traces. Assumes the feature emits $aigeneration and $aievaluation events with $sessionid linkag
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogfinding-deleted-feature-flags
Find 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. Handles the non-obvious gotcha that system.featureflags exposes the deleted boolean but does not expose a deletion timestamp — the actual deleted-at time lives in the per-flag activity log and must be cross-referenced.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogfinding-experiments
Resolves 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 engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a rela
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogfinding-replay-for-issue
Finds 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 completeness, then summarizes the pre-error context. Replaces blind session picking from potentially hundreds of linked recordings.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogfinding-sessions-to-watch
Guides 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 in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogformatting-insight-axes
Pick the right y-axis unit when creating or updating an insight via posthog:insight-create or posthog:insight-update — both TrendsQuery (trendsFilter.aggregationAxisFormat) and SQL insights (DataVisualizationNode, chartSettings.yAxis[].settings.formatting). 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 mathproperty or SQL column is a duration, currency, ratio, or large count, or whenever the user mentions "format the
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginbox-exploration
Explore 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 a specific report by ID or title, wants to act on / fix / implement a report (turn it into a PR), wants to resolve, dismiss, or snooze a report, or wants to see which signal sources are configured. Covers listing, filter
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginstrument-error-tracking
- Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginstrument-feature-flags
- Add PostHog feature flags to gate new functionality. Use after implementing features or reviewing PRs to ensure safe rollouts with feature flag controls. Also handles initial PostHog SDK setup if not yet installed.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginstrument-integration
- Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginstrument-logs
- Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginstrument-product-analytics
- Add PostHog product analytics events to track user behavior. Use after implementing new features or reviewing PRs to ensure meaningful user actions are captured. Also handles initial PostHog SDK setup if not yet installed.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthogintegration-nextjs-app-router
PostHog integration for Next.js App Router applications
- Installations / 1h
- 1
- GitHub Stars
- 74
- Mis à jour
- 15 oct.
posthoginvestigate-metric
Diagnose 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, retention, stickiness, or lifecycle metric.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.
posthoginvestigating-error-issue
Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (/errortracking/ ) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.
- Installations / 1h
- 1
- GitHub Stars
- 72
- Mis à jour
- 7 oct.