Skip to main content ホーム クリエイター jeremylongshore claude-code-plugins-plus-skills posthog-debug-bundle
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".
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill posthog-debug-bundleコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
jeremylongshore
jeremylongshore/claude-code-plugins-plus-skills
GitHub リポジトリを開く 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, also compatible with Codex and OpenClaw
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"
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 "Python: $(python3 --version 2>/dev/null || echo 'not found') "
"$BUNDLE_DIR /summary.txt"
echo
"OS: $(uname -srm) "
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- PostHog SDK Versions ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"No npm PostHog packages"
"$BUNDLE_DIR /summary.txt"
"Name|Version"
"$BUNDLE_DIR /summary.txt"
true
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- API Connectivity ---"
"$BUNDLE_DIR /summary.txt"
echo
"US Cloud ingest: "
"$BUNDLE_DIR /summary.txt"
"%{http_code} (%{time_total}s)"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"EU Cloud ingest: "
"$BUNDLE_DIR /summary.txt"
"%{http_code} (%{time_total}s)"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"App API: "
"$BUNDLE_DIR /summary.txt"
"%{http_code} (%{time_total}s)"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Environment Variables (redacted) ---"
"$BUNDLE_DIR /summary.txt"
env
's/=.*/=***REDACTED***/'
"$BUNDLE_DIR /summary.txt"
echo
"No POSTHOG env vars found"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- API Key Types ---"
"$BUNDLE_DIR /summary.txt"
if
"${NEXT_PUBLIC_POSTHOG_KEY:-} "
then
echo
"Project key prefix: $(echo "$NEXT_PUBLIC_POSTHOG_KEY " | head -c 4) _..."
"$BUNDLE_DIR /summary.txt"
fi
if
"${POSTHOG_PERSONAL_API_KEY:-} "
then
echo
"Personal key prefix: $(echo "$POSTHOG_PERSONAL_API_KEY " | head -c 4) _..."
"$BUNDLE_DIR /summary.txt"
fi
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"Bundle complete: $BUNDLE_DIR /"
"$BUNDLE_DIR /summary.txt"
Step 2: Test Event Capture Flow set -euo pipefail
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 "
Step 3: Check Feature Flag Status set -euo pipefail
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)
}'
Step 4: Verify Admin API Access set -euo pipefail
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
Step 5: Package and Review set -euo pipefail
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"
tar -czf "$BUNDLE_DIR .tar.gz" "$BUNDLE_DIR "
echo "Bundle created: $BUNDLE_DIR .tar.gz ($(du -h "$BUNDLE_DIR .tar.gz" | cut -f1) )"
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 /decide failsKey/host mismatch Ensure key matches the 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 configprojects.json — Project list (if personal key available)Test event capture and flag evaluation results
Resources
Next Steps For rate limit issues, see posthog-rate-limits.
