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: "deepgram debug", "deepgram support ticket", "collect deepgram logs", "deepgram diagnostic", "deepgram debug bundle".
What this skill does
# 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
```bash
#!/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
```bash
# 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
```bash
# 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
```typescript
// 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
```bash
# 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.gz` with 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 aRelated in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.