Agent skill · software engineering · jeremylongshore
deepgram-migration-deep-dive
Deep dive into migrating to Deepgram from other transcription providers.
Why this skill is useful
Adds executable scripts and detailed migration patterns for transitioning to Deepgram from various transcription services, which are not commonly documented.
What it needs
Requires npm, pip installed locally. Requires aws, deepgram, google account access. About 6k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deepgram Migration Deep Dive Prerequisites An inventory of existing audio/transcript flows, data retention/consent obligations, evaluation fixtures, and rollback owner. A staging environment with separate credentials and a compatibility/quality acceptance threshold. Examples Run the old and new transcription flow against approved non-sensitive fixtures, compare aggregate accuracy/latency/error metrics, and route a small reversible staging canary only after acceptance passes. Roll back immediately on quality, consent, or operational regression; do not bulk-migrate or reprocess customer recordings before the observation window closes. Current State !npm list @deepgram/sdk 2>/dev/null grep deepgram echo 'Not installed' !npm list @aws-sdk/client-transcribe 2>/dev/null grep transcribe echo 'AWS Transcribe SDK not found' !pip show google-cloud-speech 2>/dev/null grep Version echo 'Google STT not found' Overview Migrate to Deepgram from AWS Transcribe, Google Cloud Speech-to-Text, Azure Cognitive Services, or OpenAI Whisper. Uses an adapter pattern with a unified interface, parallel running for quality validation, percentage-based traffic shifting, and automated rollback. Feature Mapping AWS Transcribe -> Deepgram AWS Transcribe Deepgram Notes ---------------- ---------- ------- LanguageCode: 'en-US' language: 'en' ISO 639-1 (2-letter) ShowSpeakerLabels: true diarize: true Same feature, different param VocabularyName: 'custom' keywords: ['term:1.5'] Inline boosting, no pre-upload ContentRedactionType: 'PII' redact: ['pci', 'ssn'] Granular PII categories OutputBucketName callback: 'https://...' Callback URL, not S3 Job polling model Sync response or callback No polling needed Google Cloud STT -> Deepgram Google STT Deepgram Notes ------------ ---------- ------- RecognitionConfig.encoding Auto-detected Deepgram auto-detects format RecognitionConfig.sampleRateHertz samplerate (live only) REST auto-detects RecognitionConfig.model: 'latestlong' model: 'nova-3' Direct mapping Sp …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/deepgram-migration-deep-dive