Skip to main content Inicio Creadores jeremylongshore tons-of-skills-marketplace assemblyai-debug-bundle
assemblyai-debug-bundle Collect AssemblyAI debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for AssemblyAI problems.
Trigger with phrases like "assemblyai debug", "assemblyai support bundle",
"collect assemblyai logs", "assemblyai diagnostic".
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill assemblyai-debug-bundleEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
name assemblyai-debug-bundle description Collect AssemblyAI debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for AssemblyAI problems.
Trigger with phrases like "assemblyai debug", "assemblyai support bundle",
"collect assemblyai logs", "assemblyai diagnostic".
allowed-tools Read, Bash(grep:*), Bash(curl:*), Bash(tar:*), Grep version 1.5.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","ai","speech-to-text","assemblyai","transcription"] compatibility Designed for Claude Code
AssemblyAI Debug Bundle
Overview
Collect all diagnostic information needed to resolve AssemblyAI issues — SDK version, transcript status, API connectivity, and configuration — packaged for support tickets.
Prerequisites
assemblyai package installedAccess to application logs
Failed transcript ID (if applicable)
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="assemblyai-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
echo "=== AssemblyAI Debug Bundle ===" > "$BUNDLE_DIR /summary.txt"
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ) " >> "$BUNDLE_DIR /summary.txt"
echo "" >> "$BUNDLE_DIR /summary.txt"
echo "--- Runtime ---" >> "$BUNDLE_DIR /summary.txt"
node --version >> "$BUNDLE_DIR /summary.txt" 2>&1 || echo "Node.js not found" >> "$BUNDLE_DIR /summary.txt"
echo "Platform: $(uname -s) $(uname -m) " >> "$BUNDLE_DIR /summary.txt"
echo "ASSEMBLYAI_API_KEY: ${ASSEMBLYAI_API_KEY:+[SET (${#ASSEMBLYAI_API_KEY} chars)]} " >> "$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- SDK Version ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"assemblyai not in node_modules"
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- API Connectivity ---"
"$BUNDLE_DIR /summary.txt"
"%{http_code}"
"Authorization: ${ASSEMBLYAI_API_KEY:-none} "
echo
"FAILED"
echo
"GET /v2/transcript: HTTP $HTTP_CODE "
"$BUNDLE_DIR /summary.txt"
"%{http_code}"
echo
"FAILED"
echo
"GET /v2: HTTP $STATUS_CODE "
"$BUNDLE_DIR /summary.txt"
echo
""
"$BUNDLE_DIR /summary.txt"
echo
"--- Service Status ---"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR /summary.txt"
echo
"Could not fetch status"
"$BUNDLE_DIR /summary.txt"
"$BUNDLE_DIR .tar.gz"
"$BUNDLE_DIR "
rm
"$BUNDLE_DIR "
echo
""
echo
"Bundle created: $BUNDLE_DIR .tar.gz"
echo
"Review for sensitive data before sharing with support."
Step 2: Programmatic Transcript Diagnostics import { AssemblyAI } from 'assemblyai' ;
const client = new AssemblyAI ({
apiKey : process.env .ASSEMBLYAI_API_KEY !,
});
async function diagnoseTranscript (transcriptId : string const transcript = await client.transcripts .get (transcriptId);
const report = {
id : transcript.id ,
status : transcript.status ,
error : transcript.error ?? null ,
audio_url : transcript.audio_url ,
audio_duration : transcript.audio_duration ,
language_code : transcript.language_code ,
speech_model : transcript.speech_model ,
created : transcript.created ,
completed : transcript.completed ,
features : {
speaker_labels : !!transcript.utterances ?.length ,
sentiment_analysis : !!transcript.sentiment_analysis_results ?.length ,
entity_detection : !!transcript.entities ?.length ,
auto_highlights : !!transcript.auto_highlights_result ?.results ?.length ,
content_safety : !!transcript.content_safety_labels ?.results ?.length ,
redact_pii : transcript.text ?.includes ('####' ) || transcript.text ?.includes ('[' ),
summarization : !!transcript.summary ,
},
word_count : transcript.words ?.length ?? 0 ,
words_per_minute : transcript.audio_duration
? ((transcript.words ?.length ?? 0 ) / (transcript.audio_duration / 60 )).toFixed (1 )
: 'N/A' ,
};
console .log (JSON .stringify (report, null , 2 ));
return report;
}
Step 3: Check Recent Failed Transcripts async function findFailedTranscripts (limit = 50 ) {
const page = await client.transcripts .list ({ limit });
const failed = page.transcripts .filter (t =>status === 'error' );
console .log (`Found ${failed.length} failed transcripts out of ${page.transcripts.length} :` );
for (const t of failed) {
console .log (` ${t.id} | ${t.created} | ${t.error} ` );
}
return failed;
}
What to Include in a Support Ticket
Transcript ID (e.g., 6wij2z3g66-...)
Error message (exact text)
SDK version (npm list assemblyai)
Node.js version
Timestamp of the failure (UTC)
Your API key
Raw audio containing PII
Customer data
Audio file format and duration
Which features were enabled (speaker_labels, etc.)
Whether the issue is intermittent or consistent
Output
assemblyai-debug-YYYYMMDD-HHMMSS.tar.gz archive with:
summary.txt — Runtime, SDK version, API connectivity, service status
Programmatic transcript diagnosis report
List of recently failed transcripts
Error Handling Item Purpose Check SDK version Version-specific bugs npm list assemblyaiAPI connectivity Network/firewall curl api.assemblyai.comService status Outage check status.assemblyai.com Transcript status Job-specific error client.transcripts.get(id)Audio URL Accessibility curl -I <audio_url>
Resources
Next Steps For rate limit issues, see assemblyai-rate-limits.
