posthog-debug
Installation
SKILL.md
PostHog Debug
Run a full PostHog analysis using MCP-native tools first, then drop to HogQL only where structured insights are insufficient.
Do not ask clarifying questions when required defaults are present. Start with source discovery, then choose the right analysis mode, then run comparisons with evidence.
Tool Priority
Per the official PostHog MCP docs, prefer these tools in this order when available:
event-definitions-list,properties-list,read-data-schemaquery-runfor trends, funnels, and pathsquery-generate-hogql-from-questionto bootstrap custom analysis, then tighten the query manuallylist-errors,error-details,error-tracking-issues-listlogs-queryfor backend or API failures that do not show up cleanly in browser-side error trackinginsights-get-all,insight-create-from-query,insight-querynotebooks-*,dashboard-*,alert-*- Raw HogQL from
references/hogql-query-pack.md