groq-debug-bundle

jeremylongshore's avatarfrom jeremylongshore

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

⭐920stars🔀111forks📁View on GitHub🕐Updated Jan 9, 2026
[Debugging]

When & Why to Use This Skill

The Groq Debug Bundle skill is a specialized diagnostic tool designed to automate the collection of technical evidence for troubleshooting Groq SDK and API issues. It streamlines the support process by gathering environment configurations, SDK versions, and network health status into a secure, redacted package, helping developers resolve persistent technical hurdles and prepare high-quality support tickets efficiently.

Use Cases

  • Support Ticket Preparation: Automatically generate a comprehensive diagnostic bundle (tar.gz) containing all necessary logs and environment data to accelerate Groq support response times.
  • Environment Compatibility Audits: Quickly verify Node.js versions, npm configurations, and @groq/sdk installations to identify version-specific bugs or environment mismatches.
  • Secure Incident Analysis: Collect and redact sensitive application logs and configuration files, ensuring that error traces can be shared with team members without exposing API keys or PII.
  • Network & Connectivity Troubleshooting: Run automated health checks against Groq API endpoints to determine if issues are caused by local network configurations or service-side outages.
namegroq-debug-bundle
description|
allowed-toolsRead, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Groq Debug Bundle

Overview

Collect all necessary diagnostic information for Groq support tickets.

Prerequisites

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

Instructions

Step 1: Create Debug Bundle Script

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

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

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

Step 3: Gather SDK and Logs

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

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

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

Resources

Next Steps

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