How do I install the Posthog Debug Bundle skill?

Run npx skillmds@latest add majiayu000/posthog-debug-bundle in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Posthog Debug Bundle safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Posthog Debug Bundle?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Posthog Debug Bundle free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Posthog Debug Bundle?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Posthog Debug Bundle by majiayu000 — Agent Skill

Name: Posthog Debug Bundle
Rating: 4.5 (4 reviews)
Author: majiayu000

Posthog Debug Bundle

Collect PostHog debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for PostHog problems. Trigger with phrases like "posthog debug", "posthog support bundle", "collect posthog logs", "posthog diagnostic".

majiayu000 Updated Sep 9, 2026 567 repo stars

File contents

PostHog Debug Bundle

Overview

Collect all necessary diagnostic information for PostHog support tickets.

Prerequisites

PostHog SDK installed
Access to application logs
Permission to collect environment info

Instructions

Step 1: Create Debug Bundle Script

#!/bin/bash
# posthog-debug-bundle.sh

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)" >> "$BUNDLE_DIR/summary.txt"

Step 2: Collect Environment Info

# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "POSTHOG_API_KEY: ${POSTHOG_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"

Step 3: Gather SDK and Logs

# SDK version
npm list @posthog/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"

# Recent logs (redacted)
grep -i "posthog" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"

# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"

# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.posthog.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"

Step 4: Package Bundle

tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"

Output

posthog-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
- summary.txt - Environment and SDK info
- logs.txt - Recent redacted logs
- config-redacted.txt - Configuration (secrets removed)

Error Handling

Item	Purpose	Included
Environment versions	Compatibility check	✓
SDK version	Version-specific bugs	✓
Error logs (redacted)	Root cause analysis	✓
Config (redacted)	Configuration issues	✓
Network test	Connectivity issues	✓

Examples

Sensitive Data Handling

ALWAYS REDACT:

API keys and tokens
Passwords and secrets
PII (emails, names, IDs)

Safe to Include:

Error messages
Stack traces (redacted)
SDK/runtime versions

Submit to Support

Create bundle: bash posthog-debug-bundle.sh
Review for sensitive data
Upload to PostHog support portal

Resources

Next Steps

For rate limit issues, see posthog-rate-limits.

---name: posthog-debug-bundledescription: Collect PostHog debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for PostHog problems. Trigger with phrases like "posthog debug", "posthog support bundle", "collect posthog logs", "posthog diagnostic".license: MIT--- # PostHog Debug Bundle ## Overview Collect all necessary diagnostic information for PostHog support tickets. ## Prerequisites - PostHog SDK installed - Access to application logs - Permission to collect environment info ## Instructions ### Step 1: Create Debug Bundle Script ```bash #!/bin/bash # posthog-debug-bundle.sh 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)" >> "$BUNDLE_DIR/summary.txt" ``` ### Step 2: Collect Environment Info ```bash # Environment info echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt" node --version >> "$BUNDLE_DIR/summary.txt" 2>&1 npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1 echo "POSTHOG_API_KEY: ${POSTHOG_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt" ``` ### Step 3: Gather SDK and Logs ```bash # SDK version npm list @posthog/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt" # Recent logs (redacted) grep -i "posthog" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt" # Configuration (redacted - secrets masked) echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt" cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt" # Network connectivity test echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt" echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt" curl -s -o /dev/null -w "%{http_code}" https://api.posthog.com/health >> "$BUNDLE_DIR/summary.txt" echo "" >> "$BUNDLE_DIR/summary.txt" ``` ### Step 4: Package Bundle ```bash tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR" echo "Bundle created: $BUNDLE_DIR.tar.gz" ``` ## Output - `posthog-debug-YYYYMMDD-HHMMSS.tar.gz` archive containing: - `summary.txt` - Environment and SDK info - `logs.txt` - Recent redacted logs - `config-redacted.txt` - Configuration (secrets removed) ## Error Handling | Item | Purpose | Included | |------|---------|----------| | Environment versions | Compatibility check | ✓ | | SDK version | Version-specific bugs | ✓ | | Error logs (redacted) | Root cause analysis | ✓ | | Config (redacted) | Configuration issues | ✓ | | Network test | Connectivity issues | ✓ | ## Examples ### Sensitive Data Handling **ALWAYS REDACT:** - API keys and tokens - Passwords and secrets - PII (emails, names, IDs) **Safe to Include:** - Error messages - Stack traces (redacted) - SDK/runtime versions ### Submit to Support 1. Create bundle: `bash posthog-debug-bundle.sh` 2. Review for sensitive data 3. Upload to PostHog support portal ## Resources - [PostHog Support](https://docs.posthog.com/support) - [PostHog Status](https://status.posthog.com) ## Next Steps For rate limit issues, see `posthog-rate-limits`.

Frequently asked questions