groq-debug-bundle
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".
npx skills add majiayu000/claude-skill-registry --skill groq-debug-bundle-helixdevelopment-helixagent --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ```bash #!/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 ```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 "GROQ_API_KEY: ${GROQ_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt" ``` ### Step 3: Gather SDK and Logs ```bash # 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-reda
- Overview
- Prerequisites
- Instructions
- Step 1: Create Debug Bundle Script
- Step 2: Collect Environment Info
- Step 3: Gather SDK and Logs
- Step 4: Package Bundle
- Output
- Error Handling
- Examples
- Sensitive Data Handling
- Submit to Support
- Resources
- Next Steps
groq-debug-bundle.sh
mkdir -p "$BUNDLE_DIR"
echo "=== Groq Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"
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"
SDK versionWhat does the groq-debug-bundle skill do?
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".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill groq-debug-bundle-helixdevelopment-helixagent --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.