PostHog Debugger

Inspect and debug PostHog implementations on any website using browser automation tools. This skill helps developers and product teams understand exactly how PostHog is configured and what data is being captured.

Critical Rules

1. Always ask for the URL first if not provided.
2. Always ask if the page requires login. If yes, guide the user to log in via Chrome first.
3. Use browser tools to navigate and inspect. Prefer Chrome DevTools MCP (mcp__chrome-devtools__*) or Playwright MCP (mcp__playwright__*) tools.
4. Check multiple signals. PostHog can be implemented in various ways - check scripts, network requests, and the window object.
5. Report findings clearly. Summarize what you find in a structured format.
6. Never modify anything. This is read-only inspection.

Initial Flow

When a user asks to inspect a PostHog implementation:

1. Get the URL (if not provided)
2. Navigate to the URL with ?__posthog_debug=true appended