Explains how to query PostHog data, defaulting to typed runners for supported product analytics. Read it before you write HogQL/SQL. Also read it before you call execute-sql against PostHog. Use it to find or aggregate PostHog entities. These entities include insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, warehouse data, and persons. Use it for trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, and LLM traces. Before you calculate a governed business or telemetry measure, check system.information_schema.metrics for an approved definition. Examples include MRR, activation, billable usage, active organizations, and failure rates. Use the approved definition before you derive a measure from raw events or use a typed domain tool. It also covers HogQL differences, system table schemas, functions, query examples, and schema discovery.
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. Also use before you investigate an error, bug, metric change, or support ticket in code, to find research the Inbox already did. Covers listing, filtering, drilling into, and acting on reports, plus pointers to the deeper `signals` skill when raw signals or semantic search are needed. For a personal, ranked top N of reports, use `prioritizing-my-inbox`.
Build a personal, ranked shortlist of the PostHog Inbox reports the current user is most likely to care about right now. Combines the user's activity summary (what they work on and keep an eye on), the inbox ranking model's open, action and fix probabilities and lifts, suggested-reviewer routing, ownership, pull request state and recency, then returns the top N (25 by default) ordered from most to least relevant. Use when the user says "let's look at my inbox", "what's in my inbox for me?", "my top 10 inbox reports", "what should I look at today?", or asks to re-rank, focus, or filter that list. For browsing, filtering, drilling into, or acting on a single report, use `inbox-exploration`.