Agent skill · operations · jeremylongshore
elevenlabs-ci-integration
Configure CI/CD pipelines for ElevenLabs with mocked unit tests and gated integration tests. Use when setting up GitHub Actions for TTS projects, configuring CI test strategies, or automating ElevenLabs integration validation without burning character quota on every PR. Trigger with "elevenlabs CI", "elevenlabs GitHub Actions", "elevenlabs automated tests", "CI elevenlabs", "elevenlabs pipeline".
Why this skill is useful
Adds a two-tier CI/CD pipeline configuration specifically for ElevenLabs, including mocked unit tests and integration tests that optimize API usage.
What it needs
Requires gh installed locally. Requires elevenlabs account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ElevenLabs CI Integration Overview Set up CI/CD pipelines that test ElevenLabs integrations without burning character quota on every PR. Uses a two-tier strategy: mocked unit tests on every push (no API key, zero quota), and gated integration tests that hit the real API only on main or a manual dispatch, behind a quota guard. The full workflow YAML and secret setup live in references/implementation.md; the complete test code lives in references/examples.md. This file walks the strategy end to end, then drills into either reference for copy-paste source. Prerequisites GitHub repository with Actions enabled ElevenLabs API key for integration tests (use a test/dev key, not production) npm/pnpm project with vitest configured Instructions Step 1: Add the two-tier workflow Create .github/workflows/elevenlabs-tests.yml with two jobs. unit-tests runs on every push/PR with a mock key. integration-tests runs only on main or workflowdispatch, needs: unit-tests, and checks remaining quota before spending any: Copy the complete, runnable workflow from references/implementation.md. Step 2: Store the API key as a repository secret Step 3: Write mocked unit tests Mock the entire SDK so unit tests never call the API or spend quota. Minimal skeleton: Full mock (streaming, voices, user/subscription) and assertions: references/examples.md. Step 4: Write gated integration tests Skip integration tests unless ELEVENLABSINTEGRATION is set, and keep them cheap — Flash model, short text, low bitrate: Full smoke suite: references/examples.md. Step 5: Wire the package scripts Add test, test:integration, and test:ci scripts so CI and local runs share one entry point. See references/examples.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/elevenlabs-ci-integration