deepgram-debug-bundle
Collect Deepgram debug evidence for support and troubleshooting. Use when preparing support tickets, investigating issues, or collecting diagnostic information for Deepgram problems. Trigger with phrases like "deepgram debug", "deepgram support", "collect deepgram logs", "deepgram diagnostic", "deepgram debug bundle".
Install
mkdir -p .claude/skills/deepgram-debug-bundle && curl -L -o skill.zip "https://mcp.directory/api/skills/download/7110" && unzip -o skill.zip -d .claude/skills/deepgram-debug-bundle && rm skill.zipInstalls to .claude/skills/deepgram-debug-bundle
About this skill
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
ffprobeavailable 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"
# System info
{
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"
Step 2: API Connectivity Tests
# Test REST API
{
echo "=== REST API Test ==="
echo "Timestamp: $(date -u +%Y-%m-%dT%H:%M:%SZ)"
echo ""
echo "--- Project listing ---"
curl -s -w "\nHTTP: %{http_code} | Time: %{time_total}s\n" \
'https://api.deepgram.com/v1/projects' \
-H "Authorization: Token $DEEPGRAM_API_KEY" 2>&1 | \
sed "s/$DEEPGRAM_API_KEY/REDACTED/g"
echo ""
echo "--- Transcription test (Bueller sample) ---"
curl -s -w "\nHTTP: %{http_code} | Time: %{time_total}s\n" \
-X POST 'https://api.deepgram.com/v1/listen?model=nova-3&smart_format=true' \
-H "Authorization: Token $DEEPGRAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://static.deepgram.com/examples/Bueller-Life-moves-702702706.wav"}' 2>&1 | \
sed "s/$DEEPGRAM_API_KEY/REDACTED/g"
echo ""
echo "--- WebSocket handshake test ---"
curl -s -w "\nHTTP: %{http_code}\n" -o /dev/null \
'https://api.deepgram.com/v1/listen' \
-H "Authorization: Token $DEEPGRAM_API_KEY" \
-H "Upgrade: websocket" 2>&1 | \
sed "s/$DEEPGRAM_API_KEY/REDACTED/g"
} > "$BUNDLE_DIR/connectivity.txt"
Step 3: Audio Analysis
# Analyze problem audio file (if provided)
analyze_audio() {
local file="$1"
local outfile="$BUNDLE_DIR/audio-analysis.txt"
{
echo "=== Audio Analysis: $(basename "$file") ==="
echo "File size: $(stat -f%z "$file" 2>/dev/null || stat -c%s "$file" 2>/dev/null)"
echo ""
if command -v ffprobe &>/dev/null; then
echo "--- FFprobe Output ---"
ffprobe -v quiet -print_format json -show_format -show_streams "$file"
echo ""
echo "--- Key Properties ---"
local codec=$(ffprobe -v quiet -show_entries stream=codec_name -of csv=p=0 "$file")
local rate=$(ffprobe -v quiet -show_entries stream=sample_rate -of csv=p=0 "$file")
local channels=$(ffprobe -v quiet -show_entries stream=channels -of csv=p=0 "$file")
local duration=$(ffprobe -v quiet -show_entries format=duration -of csv=p=0 "$file")
local bitdepth=$(ffprobe -v quiet -show_entries stream=bits_per_sample -of csv=p=0 "$file")
echo "Codec: $codec"
echo "Sample rate: $rate Hz"
echo "Channels: $channels"
echo "Bit depth: $bitdepth"
echo "Duration: ${duration}s"
echo ""
# Check for common issues
echo "--- Compatibility Check ---"
[[ "$rate" -lt 8000 ]] && echo "WARNING: Sample rate below 8kHz minimum"
[[ "$rate" -gt 48000 ]] && echo "WARNING: Sample rate above 48kHz — consider downsampling"
[[ "$channels" -gt 2 ]] && echo "WARNING: >2 channels — Deepgram supports mono/stereo"
else
echo "ffprobe not available — install ffmpeg for audio analysis"
echo ""
echo "--- File header (hex) ---"
xxd -l 16 "$file"
fi
} > "$outfile"
}
Step 4: Request/Response Logger
// Wrap Deepgram client to capture full request/response for debugging
import { createClient } from '@deepgram/sdk';
import { writeFileSync } from 'fs';
async function captureDebugRequest(audioSource: string | Buffer) {
const client = createClient(process.env.DEEPGRAM_API_KEY!);
const startTime = Date.now();
try {
const isUrl = typeof audioSource === 'string';
const method = isUrl ? 'transcribeUrl' : 'transcribeFile';
const source = isUrl ? { url: audioSource } : audioSource;
const options = { model: 'nova-3' as const, smart_format: true };
const { result, error } = isUrl
? await client.listen.prerecorded.transcribeUrl(source as any, options)
: await client.listen.prerecorded.transcribeFile(source as any, options);
const elapsed = Date.now() - startTime;
const debugLog = {
timestamp: new Date().toISOString(),
method,
options,
elapsed_ms: elapsed,
success: !error,
error: error ? { message: error.message, status: (error as any).status } : null,
result_summary: result ? {
request_id: result.metadata?.request_id,
duration: result.metadata?.duration,
model: result.metadata?.model_info,
transcript_length: result.results?.channels[0]?.alternatives[0]?.transcript?.length,
confidence: result.results?.channels[0]?.alternatives[0]?.confidence,
} : null,
};
writeFileSync('debug-request.json', JSON.stringify(debugLog, null, 2));
console.log('Debug log written to debug-request.json');
return debugLog;
} catch (err: any) {
const debugLog = {
timestamp: new Date().toISOString(),
elapsed_ms: Date.now() - startTime,
error: { message: err.message, stack: err.stack },
};
writeFileSync('debug-request.json', JSON.stringify(debugLog, null, 2));
throw err;
}
}
Step 5: Package and Sanitize Bundle
# Package everything (API keys already redacted in Step 2)
{
echo "=== Deepgram Debug Bundle ==="
echo "Created: $(date -u +%Y-%m-%dT%H:%M:%SZ)"
echo ""
echo "Issue Description: [DESCRIBE YOUR ISSUE HERE]"
echo ""
echo "Files:"
echo " environment.txt - System and SDK versions"
echo " connectivity.txt - API connectivity test results"
echo " audio-analysis.txt - Audio file properties (if provided)"
echo " debug-request.json - Request/response capture (if run)"
echo ""
echo "Attach this bundle to your support ticket at:"
echo " https://developers.deepgram.com/support"
} > "$BUNDLE_DIR/README.txt"
# Final sanitization pass — remove any leaked keys
find "$BUNDLE_DIR" -type f -exec sed -i "s/$DEEPGRAM_API_KEY/REDACTED/g" {} +
tar czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"
Step 6: Support Ticket Template
Subject: [Issue Type] — Brief Description
Environment:
- SDK: @deepgram/sdk v3.x.x
- Runtime: Node.js 20.x / Python 3.12
- OS: Ubuntu 22.04
Request ID: (from result.metadata.request_id)
Model: nova-3
Timestamp: 2026-03-22T12:00:00Z
Issue:
[Describe what you expected vs what happened]
Steps to Reproduce:
1. [Step 1]
2. [Step 2]
3. [Observe error]
Attachments:
- deepgram-debug-YYYYMMDD-HHMMSS.tar.gz
- Sample audio file (if shareable)
Output
deepgram-debug-YYYYMMDD-HHMMSS.tar.gzwith sanitized diagnostics- Environment and connectivity test results
- Audio file analysis with compatibility warnings
- Request/response debug capture
- Support ticket template
Error Handling
| Issue | Cause | Resolution |
|---|---|---|
ffprobe not found | ffmpeg not installed | apt install ffmpeg or brew install ffmpeg |
| Connectivity test 401 | Key not exported | export DEEPGRAM_API_KEY=your-key |
| Empty audio analysis | File path wrong | Verify file exists and is readable |
| Tar fails | Permissions issue | Check write permissions in current directory |
Resources
More by jeremylongshore
View all skills by jeremylongshore →You might also like
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
drawio-diagrams-enhanced
jgtolentino
Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.
ui-ux-pro-max
nextlevelbuilder
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
nano-banana-pro
garg-aayush
Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
Related MCP Servers
Browse all serversControl any ROS1 or ROS2 robot with natural language using ROS MCP Server—AI-powered, code-free, real-time monitoring an
Connect MongoDB databases to chat interfaces. Manage AWS with MongoDB, explore Atlas cost, and inspect collections secur
Easily integrate and debug Sentry APIs with sentry-mcp, a flexible MCP middleware for cloud and self-hosted setups.
Empower AI agents for efficient API automation in Postman for API testing. Streamline workflows and boost productivity w
Unlock AI-powered automation for Postman for API testing. Streamline workflows, code sync, and team collaboration with f
Integrate DuckDuckGo web search into your site with our MCP server, supporting features like Google custom search and ro
Stay ahead of the MCP ecosystem
Get weekly updates on new skills and servers.