| name | deepgram-debug-bundle |
| description | Collect Deepgram debug evidence for support and troubleshooting.
Use when preparing support tickets, investigating issues,
or collecting diagnostic information for Deepgram problems.
Trigger: "deepgram debug", "deepgram support ticket", "collect deepgram logs",
"deepgram diagnostic", "deepgram debug bundle".
|
| allowed-tools | Read, Grep, Bash(curl:*), Bash(ffprobe:*), Bash(npm:*), Bash(tar:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| compatible-with | claude-code, codex, openclaw |
| tags | ["saas","deepgram","debugging","support"] |
Deepgram Debug Bundle
Current State
!node --version 2>/dev/null || echo 'Node.js not installed'
!npm list @deepgram/sdk 2>/dev/null | grep deepgram || echo '@deepgram/sdk not found'
!python3 --version 2>/dev/null || echo 'Python not installed'
Overview
Collect comprehensive debug information for Deepgram support tickets. Generates a sanitized bundle with environment info, API connectivity tests, audio analysis, request/response logs, and a minimal reproduction script. All API keys are automatically redacted.
Prerequisites
- Deepgram API key configured
ffprobe available for audio analysis (part of ffmpeg)- Sample audio that reproduces the issue
Instructions
Step 1: Environment Collection Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="deepgram-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"
{
echo "=== System ==="
uname -a
echo ""
echo "=== Node.js ==="
node --version 2>/dev/null || echo "Not installed"
echo ""
echo "=== @deepgram/sdk ==="
npm list @deepgram/sdk 2>/dev/null || echo "Not installed"
echo ""
echo "=== Python ==="
python3 --version 2>/dev/null || echo "Not installed"
pip show deepgram-sdk 2>/dev/null || echo "Not installed"
} > "$BUNDLE_DIR/environment.txt"
