perplexity-debug-bundle

jeremylongshore's avatarfrom jeremylongshore

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

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026
[Debugging]

When & Why to Use This Skill

The Perplexity Debug Bundle is a specialized Claude skill designed to automate the collection of diagnostic information and logs for Perplexity API integrations. It streamlines the troubleshooting process by gathering environment data, SDK versions, and redacted logs into a secure, ready-to-submit support package, ensuring faster incident resolution and more efficient technical support interactions.

Use Cases

  • Troubleshooting persistent API errors by generating a comprehensive diagnostic report of the local environment and network connectivity.
  • Preparing standardized debug evidence for Perplexity support tickets to reduce back-and-forth communication and speed up technical assistance.
  • Auditing local SDK configurations and redacted logs to identify version mismatches or misconfigured environment variables without exposing sensitive credentials.
nameperplexity-debug-bundle
description|
allowed-toolsRead, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Perplexity Debug Bundle

Overview

Collect all necessary diagnostic information for Perplexity support tickets.

Prerequisites

  • Perplexity SDK installed
  • Access to application logs
  • Permission to collect environment info

Instructions

Step 1: Create Debug Bundle Script

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

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

echo "=== Perplexity 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 "PERPLEXITY_API_KEY: ${PERPLEXITY_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"

Step 3: Gather SDK and Logs

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

# Recent logs (redacted)
grep -i "perplexity" ~/.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.perplexity.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

  • perplexity-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 perplexity-debug-bundle.sh
  2. Review for sensitive data
  3. Upload to Perplexity support portal

Resources

Next Steps

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