Agent skill · software engineering · jeremylongshore
elevenlabs-prod-checklist
Execute an ElevenLabs production deployment checklist with health checks and rollback. Use when deploying TTS/voice integrations to production, preparing for launch, or implementing go-live procedures for ElevenLabs-powered apps. Trigger with "elevenlabs production", "deploy elevenlabs", "elevenlabs go-live", "elevenlabs launch checklist", or "production TTS".
Why this skill is useful
Adds a comprehensive deployment checklist with executable scripts for health checks and rollback procedures specific to ElevenLabs TTS integrations.
What it needs
Requires curl, jq installed locally. Requires elevenlabs account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ElevenLabs Production Checklist Overview Complete checklist for deploying ElevenLabs TTS/voice integrations to production. Covers API configuration, health checks, circuit breakers, monitoring, and rollback procedures. The deep code for the resilience primitives lives in references/ so this file stays a fast, scannable runbook — drill in when you need the full implementation. Prerequisites Staging environment tested and verified Production API key (separate from dev/staging) Monitoring and alerting infrastructure ready Instructions Step 1: Pre-Deployment Verification Walk the checklist below. Every unchecked box is a launch blocker. Configuration: [ ] Production API key stored in secure vault (not in code) [ ] ELEVENLABSAPIKEY set in deployment platform's secrets [ ] Webhook secret configured (if using webhooks) [ ] Using production model ID (elevenmultilingualv2 or elevenv3) Code Quality: [ ] All tests passing with mocked ElevenLabs SDK [ ] No hardcoded API keys (scan with grep -r "sk" src/) [ ] Error handling covers 400, 401, 404, 429, 5xx responses [ ] Rate limiting implemented matching plan concurrency limit [ ] Text splitting handles inputs > 5,000 characters [ ] Audio output format appropriate for use case Quota Planning: [ ] Estimated monthly character usage fits within plan limit [ ] Usage-based billing enabled (Creator+ plans) if needed [ ] Flash/Turbo models used where latency matters more than quality Step 2: Wire the resilience primitives Production ElevenLabs integrations need three primitives. The full drop-in TypeScript for each is in references/implementation.md — high-level intent: 1. Health check endpoint — reports connectivity, latency, and remaining quota; returns degraded past 90% quota and unhealthy on any API failure, so a load balancer can gate traffic. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/elevenlabs-prod-checklist