querying-posthog-data
Querying data in PostHog
The guidelines contain the same instructions as posthog:execute-sql. If you've already read posthog:execute-sql, you don't need to read them again.
When to use this skill
Finding a specific PostHog entity
When the user wants to find a specific entity created in PostHog (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse items, etc.), or when a list/search tool returns too many results to narrow down:
- Read the appropriate schema reference under Data Schema to understand the entity's table and columns.
- Use
posthog:execute-sqlto query the system table and find the matching entity (typically returning its ID). - Use the dedicated read tool for that entity type (e.g.
posthog:insight-get,posthog:dashboard-get) to retrieve the full entity by ID.
Don't try to reconstruct the entity from SQL — execute-sql is for discovery, the read tool is for retrieval.
Querying analytics data
When the user wants analytics data (trends, funnels, retention, paths, sessions, LLM traces, web analytics, errors, logs, etc.) and the existing insight schemas don't fit the request:
More from posthog/skills
posthog-debugger
Debug and inspect PostHog implementations on any website. Use this skill when a user wants to understand how PostHog is implemented on a page, troubleshoot tracking issues, verify configuration, check what events are being sent, or audit a PostHog setup. Works with Chrome DevTools MCP and Playwright MCP to inspect live websites.
106integration-nextjs-app-router
PostHog integration for Next.js App Router applications
100instrument-product-analytics
>-
90feature-flags-nextjs
PostHog feature flags for Next.js applications
88instrument-feature-flags
>-
86error-tracking-nextjs
PostHog error tracking for Next.js
85