posthog-funnel-maplisted

# PostHog funnel map Every analysis goes wrong the same two ways: the agent guesses event names (`signup`, `purchase`) and reports zero, or it judges numbers without knowing the business ("2 % conversion is bad" for a product sold at 300 € a year to parents). The funnel map fixes both, once per project. It is a file the user owns and edits, committed with their code, at `.claude/posthog-funnel-map.md`. If the file exists and is less than 30 days old, read it and stop here unless the user asked to refresh it. ## Tools The PostHog MCP server (`https://mcp.posthog.com/mcp`). Depending on the client, tools are exposed one by one (`execute-sql`, `read-data-schema`…) or through a single `exec` tool that takes `call <tool> <json>`. Same tools, same names. Run `info <tool>` before the first call of a tool you have not used in this session, and follow its `hint` fields instead of guessing a schema. When a tool name here doesn't exist, `search <keyword>`: PostHog renames tools. All calls in this skill are read-only. Check the active project first (the MCP says which one is active). A user with several projects, or a second PostHog connector pointing at an empty project, is a common source of "no data". If the official PostHog plugin is installed (`PostHog/ai-plugin`), its `querying-posthog-data` skill has the HogQL reference: read it before writing non-trivial SQL. ## Step 1: the business profile (a short interview) Ask at most five questions, in one message, and propose a defa