posthog_querylisted

# PostHog Query > Unofficial, agentstack-authored. Not affiliated with or endorsed by PostHog. Use this skill when someone asks a product question in plain language ("are people dropping off at checkout?", "is the new onboarding sticking?") and you need to translate it into a concrete PostHog insight rather than guessing. ## Workflow 1. Restate the question as a measurable outcome. Pin down the **metric** (count, unique users, conversion rate, retention), the **population** (all users, a cohort, a single platform), and the **time window** before touching any tool. 2. Pick the right insight type for the shape of the question: - **Trends** — "how many / how often" over time, with optional breakdowns. - **Funnels** — "where do people drop off" across an ordered sequence of steps. - **Retention** — "do people come back" after a first action. - **Paths** — "what do people actually do" when the journey is unknown. 3. Map the question to **real events and properties**. List the project's events first (do not assume `signup` exists) and choose the closest match. Prefer unique-user math over raw event counts unless volume is the point. 4. Set an explicit date range and interval. Default to a window that captures at least one full cycle of the behavior (e.g. 30 days for weekly habits); never leave it implicit. 5. Add breakdowns or a cohort filter only when they answer the question. One clear breakdown beats three noisy ones. 6. Sanity-check the resu