Agent skill · data analytics · jeremylongshore
posthog-debug-bundle
Collect a redacted, reproducible PostHog diagnostic bundle without capturing secrets or raw customer data. Use when an integration failure needs escalation or handoff. Trigger with "PostHog debug bundle", "collect PostHog evidence", or "PostHog support ticket".
Why this skill is useful
Adds an executable script that automates the collection of diagnostic evidence for PostHog, which is not readily available in public documentation.
What it needs
Requires curl, jq installed locally. Requires posthog account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
PostHog Debug Bundle Overview Collect diagnostic evidence for PostHog support tickets. Gathers SDK versions, API connectivity, feature flag status, event flow verification, and redacted configuration. All secrets are automatically redacted. Prerequisites PostHog SDK installed in project Access to environment variables curl and jq available Instructions Tool discipline Use Read to inspect the relevant configuration and implementation before proposing changes. Use Grep to locate initialization, capture, flag, and credential boundaries. Step 1: Run Full Diagnostic Script Step 2: Test Event Capture Flow Only When Approved Step 3: Check Feature Flag Status Step 4: Verify Admin API Access Step 5: Package and Review Checklist Item Collected Purpose ------ ----------- --------- Node/Python versions Yes SDK compatibility PostHog SDK versions Yes Version-specific bugs API connectivity Yes Network/firewall issues Event capture test Yes End-to-end verification Feature flag status Yes Flag evaluation issues Environment vars (redacted) Yes Configuration problems Key type detection Yes Wrong key type errors Error Handling Issue Cause Solution ------- ------- ---------- All connectivity fails Corporate firewall Check proxy settings, try VPN Capture returns non-200 Invalid API key Verify phc key in project settings /flags fails Key/host mismatch Ensure the project token matches the selected host region Personal API 401 Expired key Regenerate in Settings > Personal API Keys Output posthog-debug-YYYYMMDD-HHMMSS.tar.gz archive containing: summary.txt — Runtime, SDK versions, connectivity, redacted config projects.json — Project list (if personal key available) Test event capture and flag evaluation results Examples For delayed server events, record SDK versions, configured region, sanitized option names, connectivity status, queue lifecycle, and a bounded log excerpt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/posthog-debug-bundle--aaa437