Agent skill · data analytics · jeremylongshore
deepgram-data-handling
Implement audio data handling best practices for Deepgram integrations.
Why this skill is useful
Provides specific compliance workflows and PII redaction patterns for Deepgram that the AI wouldn't reliably generate on its own.
What it needs
Requires aws-sdk installed locally. Requires deepgram account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Deepgram Data Handling Prerequisites Data classification, consent/legal basis, approved retention/deletion policy, storage boundary, and named data owner. A redaction/logging policy and an incident route for recording or transcript exposure. Examples Process a licensed development fixture through the approved region/storage route, verify its retention/deletion behavior, and record only a correlation ID and policy result. Do not put recordings, transcripts, participant identifiers, or storage URLs into test logs; on accidental exposure, restrict access and follow the data incident procedure. Overview Best practices for handling audio and transcript data with Deepgram. Covers Deepgram's built-in redact parameter for PII, secure audio upload with encryption, transcript storage patterns, data retention policies, and GDPR/HIPAA compliance workflows. Data Privacy Quick Reference Deepgram Feature What It Does Enable ------------------- ------------- -------- redact: ['pci'] Masks credit card numbers in transcript Query param redact: ['ssn'] Masks Social Security numbers Query param redact: ['numbers'] Masks all numeric sequences Query param Data retention Deepgram does NOT store audio or transcripts Default behavior Deepgram's data policy: Audio is processed in real-time and not stored. Transcripts are not retained unless you use Deepgram's optional storage features. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/deepgram-data-handling--666d50