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:

  1. event-definitions-list, properties-list, read-data-schema
  2. query-run for trends, funnels, and paths
  3. query-generate-hogql-from-question to bootstrap custom analysis, then tighten the query manually
  4. list-errors, error-details, error-tracking-issues-list
  5. logs-query for backend or API failures that do not show up cleanly in browser-side error tracking
  6. insights-get-all, insight-create-from-query, insight-query
  7. notebooks-*, dashboard-*, alert-*
  8. Raw HogQL from references/hogql-query-pack.md
Installs
2
GitHub Stars
4
First Seen
Mar 5, 2026