Deepgram Prod ChecklistSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-08Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: deepgram-prod-checklist description: 'Execute Deepgram production deployment checklist. Use when preparing for production launch, auditing production readiness, or verifying deployment configurations. Trigger: "deepgram production", "deploy deepgram", "deepgram prod checklist", "deepgram go-live", "production ready deepgram". ' allowed-tools: Read, Write, Edit, Grep, Bash(curl:*) version: 1.13.0 license: MIT author: Jeremy Longshore <[email protected]> tags: - saas - deepgram - deployment - production compatibility: Designed for Claude Code --- # Deepgram Production Checklist ## Prerequisites - A named service/data owner, approved model/provider/data-routing decision, and production rollback plan. - Passing staging evidence for credentials, audio retention/consent, observability, rate limits, quality, and incident escalation. ## Examples Run the final production gate with a non-sensitive canary, verify alert routing and the redacted request receipt, then observe against the stated quality/latency/error threshold. If any gate fails, halt rollout and restore the previous approved configuration rather than extending the canary or disabling controls. ## Overview Comprehensive go-live checklist for Deepgram integrations. Covers singleton client, health checks, Prometheus metrics, alert rules, error handling, and a phased go-live timeline. ## Production Readiness Matrix | Category | Item | Status | |----------|------|--------| | **Auth** | Production API key with scoped permissions | [ ] | | **Auth** | Key stored in secret manager (not env file) | [ ] | | **Auth** | Key rotation schedule (90-day) configured | [ ] | | **Auth** | Fallback key provisioned and tested | [ ] | | **Resilience** | Retry with exponential backoff on 429/5xx | [ ] | | **Resilience** | Circuit breaker for cascade failure prevention | [ ] | | **Resilience** | Request timeout set (30s pre-recorded, 10s TTS) | [ ] | | **Resilience** | Graceful degradation when API unavailable | [ ] | | **Performance** | Singleton client (not creating per-request) | [ ] | | **Performance** | Concurrency limited (50-80% of plan limit) | [ ] | | **Performance** | Audio preprocessed (16kHz mono for best results) | [ ] | | **Performance** | Large files use callback URL (async) | [ ] | | **Monitoring** | Health check endpoint testing Deepgram API | [ ] | | **Monitoring** | Prometheus metrics: latency, error rate, usage | [ ] | | **Monitoring** | Alerts: error rate >5%, latency >10s, circuit open | [ ] | | **Security** | PII redaction enabled if handling sensitive audio | [ ] | | **Security** | Audio URLs validated (HTTPS, no private IPs) | [ ] | | **Security** | Audit logging on all operations | [ ] | ## Instructions ### Step 1: Production Singleton Client ```typescript import { createClient, DeepgramClient } from '@deepgram/sdk'; class ProductionDeepgram { private static client: DeepgramClient | null = null; static getClient(): DeepgramClient { if (!this.client) { const key = process.env.DEEPGRAM_API_KEY; if (!key) throw new Error('DEEPGRAM_API_KEY required for production'); this.client = createClient(key); } return this.client; } // Force re-init (for key rotation) static reset() { this.client = null; } } ``` ### Step 2: Health Check Endpoint ```typescript import express from 'express'; import { createClient } from '@deepgram/sdk'; const app = express(); const deepgram = createClient(process.env.DEEPGRAM_API_KEY!); app.get('/health', async (req, res) => { const start = Date.now(); try { // Test API connectivity by listing projects const { error } = await deepgram.manage.getProjects(); const latency = Date.now() - start; if (error) { return res.status(503).json({ status: 'unhealthy', deepgram: 'error', error: error.message, latency_ms: latency, }); } res.json({ status: 'healthy', deepgram: 'connected', latency_ms: latency, timestamp: new Date().toISOString(), }); } catch (err: any) { res.status(503).json({ status: 'unhealthy', deepgram: 'unreachable', error: err.message, latency_ms: Date.now() - start, }); } }); ``` ### Step 3: Prometheus Metrics ```typescript import { Counter, Histogram, Gauge, Registry } from 'prom-client'; const registry = new Registry(); const transcriptionRequests = new Counter({ name: 'deepgram_requests_total', help: 'Total Deepgram API requests', labelNames: ['method', 'model', 'status'], registers: [registry], }); const transcriptionLatency = new Histogram({ name: 'deepgram_latency_seconds', help: 'Deepgram API request latency', labelNames: ['method', 'model'], buckets: [0.5, 1, 2, 5, 10, 30], registers: [registry], }); const audioProcessed = new Counter({ name: 'deepgram_audio_seconds_total', help: 'Total audio seconds processed', labelNames: ['model'], registers: [registry], }); const activeConnections = new Gauge({ name: 'deepgram_active_connections', help: 'Active WebSocket connections', registers: [registry], }); // Instrumented transcription async function instrumentedTranscribe(url: string, model = 'nova-3') { const timer = transcriptionLatency.startTimer({ method: 'prerecorded', model }); try { const { result, error } = await deepgram.listen.prerecorded.transcribeUrl( { url }, { model, smart_format: true } ); timer(); transcriptionRequests.inc({ method: 'prerecorded', model, status: error ? 'error' : 'ok' }); if (result?.metadata?.duration) { audioProcessed.inc({ model }, result.metadata.duration); } if (error) throw error; return result; } catch (err) { timer(); transcriptionRequests.inc({ method: 'prerecorded', model, status: 'error' }); throw err; } } // Expose metrics endpoint app.get('/metrics', async (req, res) => { res.set('Content-Type', registry.contentType); res.send(await
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__deepgram-prod-checklist.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Deepgram Prod Checklist skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Deepgram Prod Checklist safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Deepgram Prod Checklist access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Deepgram Prod Checklist work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.