posthog-debugger

Inspect PostHog configuration and network traffic in browser.

58|5|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/PostHog/skills --skill posthog-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: posthog-debugger
Source: https://github.com/PostHog/skills/tree/main/skills/team/customer-success/posthog-debugger
Command: npx skills add https://github.com/PostHog/skills --skill posthog-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and product teams understand exactly how PostHog is configured on a page and what data is captured, by inspecting the global posthog object, network requests, and loaded scripts.

Core Features & Use Cases

  • Full implementation audit: Verify version, API host, tokens, autocapture, session recording, persistence, and load order.
  • Feature flag inspection: Identify loaded flags and their values to confirm feature rollout.
  • Session & identity analysis: Retrieve distinct IDs, session IDs, and device identifiers to ensure correct tracking.
  • Network & script analysis: Inspect network requests to PostHog endpoints and detect loaded PostHog scripts.
  • Issue detection & reporting: Surface configuration issues and common misconfigurations with clear summaries.
  • Script loading analysis: Determine how PostHog is loaded (CDN, self-hosted, or bundled) and detect multiple instances.

Quick Start

Navigate to your target URL with the PostHog debug flag enabled and let Claude run a live inspection to enumerate PostHog configuration and traffic.

Frequently Asked Questions about posthog-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug PostHog implementation issues on my website?

To debug PostHog implementation, inspect the global posthog object, network requests, and loaded scripts on your page. This process audits version, API host, tokens, autocapture, and session recording settings to surface configuration issues.

How can I verify PostHog feature flags and session data in the browser?

Verify PostHog feature flags and session data by inspecting the browser's PostHog window object. This retrieves loaded flag values, distinct IDs, session IDs, and device identifiers to ensure correct tracking and rollout.

Do I need Playwright or Chrome DevTools to inspect PostHog network traffic?

Yes, you need either Chrome DevTools MCP or Playwright MCP to inspect PostHog network traffic. These browser-based tools read the PostHog window, network requests, and console logs to validate data collection.

What is the best way to audit PostHog script loading and detect multiple instances?

The best way to audit PostHog script loading is to analyze network requests and loaded scripts on the page. This detects whether PostHog is loaded via CDN, self-hosted, or bundled, and identifies multiple instances.

Why is PostHog not capturing events correctly on my web page?

PostHog may not capture events correctly due to configuration issues like incorrect load order or disabled autocapture. Inspecting the global posthog object, network traffic, and console logs surfaces these common misconfigurations.