posthog-debug-bundle

Collect PostHog debug evidence for support tickets and troubleshooting. Gathers SDK versions, API connectivity, event flow status, flag definitions, and redacted configuration into a support-ready archive. Trigger: "posthog debug", "posthog support bundle", "collect posthog logs", "posthog diagnostic", "posthog not working debug".

仓库: jeremylongshore/tons-of-skills-marketplace
最近来源活动: 2026年8月19日 12:13
检测到的 SKILL.md 语言: 英语
星标: 2,677
分支: 392

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

返回搜索返回安装

name	posthog-debug-bundle
description	Collect PostHog debug evidence for support tickets and troubleshooting. Gathers SDK versions, API connectivity, event flow status, flag definitions, and redacted configuration into a support-ready archive. Trigger: "posthog debug", "posthog support bundle", "collect posthog logs", "posthog diagnostic", "posthog not working debug".
allowed-tools	Read, Bash(grep:), Bash(curl:), Bash(tar:*), Grep
version	1.12.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
tags	["saas","posthog","debugging"]
compatibility	Designed for Claude Code

PostHog Debug Bundle

Current State

!node --version 2>/dev/null || echo 'N/A' !npm list posthog-js posthog-node 2>/dev/null | grep posthog || echo 'No PostHog SDK found'

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

Step 1: Run Full Diagnostic Script

#!/bin/bash
set -euo pipefail

BUNDLE_DIR="posthog-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"

echo "=== PostHog Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ)" >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"

# --- Environment ---
echo "--- Runtime Environment ---" >> "$BUNDLE_DIR/summary.txt"
echo "Node: $(node --version 2>/dev/null || echo 'not found')" >> "$BUNDLE_DIR/summary.txt"
echo "npm: $(npm --version 2>/dev/null || echo 'not found')" >> "$BUNDLE_DIR/summary.txt"
echo  >> 
  >> 
  >> 


  >> 
npm list posthog-js posthog-node 2>/dev/null >>  ||   >> 
pip3 show posthog 2>/dev/null | grep -E  >>  || 
  >> 


  >> 
 -n  >> 
curl -s -o /dev/null -w  https://us.i.posthog.com/healthz >>  2>&1
  >> 
 -n  >> 
curl -s -o /dev/null -w  https://eu.i.posthog.com/healthz >>  2>&1
  >> 
 -n  >> 
curl -s -o /dev/null -w  https://app.posthog.com/api/ >>  2>&1
  >> 


  >> 
  >> 
 | grep -i posthog | sed  >>  2>/dev/null ||   >> 
  >> 


  >> 
 [ -n  ]; 
    >> 

 [ -n  ]; 
    >> 


  >> 
  >>

set -euo pipefail
# Send a test event and verify it was accepted
RESPONSE=$(curl -s -w "\n%{http_code}" -X POST 'https://us.i.posthog.com/capture/' \
  -H 'Content-Type: application/json' \
  -d "{
    \"api_key\": \"${NEXT_PUBLIC_POSTHOG_KEY}\",
    \"event\": \"debug_bundle_test\",
    \"distinct_id\": \"debug-$(date +%s)\",
    \"properties\": {\"test\": true}
  }")

HTTP_CODE=$(echo "$RESPONSE" | tail -1)
BODY=$(echo "$RESPONSE" | head -1)

echo "Capture test: HTTP $HTTP_CODE"
echo "Response: $BODY"

# Expected: HTTP 200, Response: {"status": 1}

set -euo pipefail
# Evaluate flags via the /decide endpoint
curl -s -X POST 'https://us.i.posthog.com/decide/?v=3' \
  -H 'Content-Type: application/json' \
  -d "{
    \"api_key\": \"${NEXT_PUBLIC_POSTHOG_KEY}\",
    \"distinct_id\": \"debug-test\"
  }" | jq '{
    featureFlags: .featureFlags,
    errorsWhileComputingFlags: .errorsWhileComputingFlags,
    sessionRecording: (.sessionRecording != false)
  }'

set -euo pipefail
# Test personal API key (if available)
if [ -n "${POSTHOG_PERSONAL_API_KEY:-}" ]; then
  curl -s "https://app.posthog.com/api/projects/" \
    -H "Authorization: Bearer $POSTHOG_PERSONAL_API_KEY" | \
    jq '[.[] | {id, name, created_at}]' > "$BUNDLE_DIR/projects.json" 2>/dev/null || \
    echo "Personal API key failed" >> "$BUNDLE_DIR/summary.txt"
fi

set -euo pipefail
# Review for any accidentally included secrets
grep -rn "phc_\|phx_\|Bearer " "$BUNDLE_DIR/" | grep -v REDACTED | grep -v "prefix:" && \
  echo "WARNING: Potential secret found — review before sharing" || \
  echo "No secrets detected in bundle"

# Package
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz ($(du -h "$BUNDLE_DIR.tar.gz" | cut -f1))"

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

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
`/decide` fails	Key/host mismatch	Ensure key matches the host region
Personal API 401	Expired key	Regenerate in Settings > Personal API Keys