home / skills / jeremylongshore / claude-code-plugins-plus-skills / perplexity-debug-bundle

perplexity-debug-bundle skill

safe

/plugins/saas-packs/perplexity-pack/skills/perplexity-debug-bundle

This skill helps you collect comprehensive perplexity diagnostic data to faster submit support tickets and diagnose issues.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill perplexity-debug-bundle

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.3 KB

---
name: perplexity-debug-bundle
description: |
  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".
allowed-tools: Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# 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
```bash
#!/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
```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 "PERPLEXITY_API_KEY: ${PERPLEXITY_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"
```

### Step 3: Gather SDK and Logs
```bash
# 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
```bash
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
- [Perplexity Support](https://docs.perplexity.com/support)
- [Perplexity Status](https://status.perplexity.com)

## Next Steps
For rate limit issues, see `perplexity-rate-limits`.

Overview

This skill collects a complete Perplexity debug bundle to accelerate support ticket resolution and troubleshooting. It automates environment inspection, SDK and log collection, basic network checks, and packages results into a redacted archive ready for support. Use it to produce consistent diagnostic artifacts that reduce back-and-forth with support teams.

How this skill works

The script gathers runtime environment details, installed Perplexity SDK version, recent application logs, and a simple API health check. It redacts secrets from local configuration files, compiles a summary with timestamps, and packages everything into a timestamped tarball. The resulting archive contains summary.txt, logs.txt, and config-redacted.txt for secure submission.

When to use it

You hit persistent or reproducible errors from the Perplexity SDK or API.
Preparing a support ticket to give Perplexity engineers full context quickly.
After a production incident where Perplexity calls fail or behave unexpectedly.
Before opening an escalated support case to avoid repetitive information requests.
When you need a repeatable, auditable snapshot of environment and logs for debugging.

Best practices

Ensure Perplexity SDK and tools are installed and accessible on the machine running the script.
Run the bundle script with an account that has access to logs and necessary config files, but avoid running as root unless required.
Always review the generated bundle and verify secrets are redacted before sharing.
Limit collected logs to recent entries to reduce size and surface the most relevant errors.
Include a short reproduction note and timestamps in your support ticket to correlate with the bundle.

Example use cases

Developer troubleshooting local integration failures — generate bundle and attach to the ticket.
SRE investigating intermittent API errors in staging — collect environment, SDK version, and recent logs.
Customer support intake — request a bundle from the user to triage issues without repeated back-and-forth.
Post-incident review — archive the bundle with incident notes for later root-cause analysis.
Automated diagnostics — integrate the script into a runbook to quickly collect data during incidents.

FAQ

What does the bundle include?

A timestamped tar.gz with summary.txt (environment and SDK info), logs.txt (recent redacted logs), and config-redacted.txt (configuration with secrets masked).

How are secrets handled?

The script masks config values by replacing values with ***REDACTED*** and advises manual review before sharing to ensure PII and credentials are removed.