What problem does it solve?
PostHog's system.insights table only returns rows for the current project, so agents analyzing insights across teams or fleet-wide dashboard usage would incorrectly report the data as inaccessible. This Skill documents the synced production Postgres replicas in the dogfood data warehouse that make cross-team entity metadata queryable.
Core Features & Use Cases
- Synced table reference: Maps insights, dashboards, and teams to their US (
postgres.posthog_dashboarditem, etc.) and EU (eu_postgres_*) warehouse table names.
- Column-verification workflow: Guides checking
system.information_schema.columns before querying, since synced schemas drift with the Django models.
- Data handling rules: Enforces that customer team names and insight titles never appear on public surfaces like PRs, commits, or issues.
- Use Case: An engineer asks which teams created the most insights in the last 30 days; the agent queries
postgres.posthog_dashboarditem grouped by team_id instead of stopping at the project-scoped system.insights.
Quick Start
Ask the agent to analyze insight usage across all PostHog teams using the synced Postgres warehouse tables in the dogfood project.
