Agent skill · software engineering · jeremylongshore
elevenlabs-local-dev-loop
Use when setting up a local ElevenLabs dev environment for a TTS/voice project and you need SDK mocking, hot reload, quota-aware iteration, and audio-output testing that does not burn character quota during development. Trigger with "elevenlabs dev setup", "elevenlabs local development", "elevenlabs dev environment", "develop with elevenlabs", "test elevenlabs locally".
Why this skill is useful
Adds a complete local development setup with scripts for mocking the ElevenLabs SDK, hot reloading, and quota management that the AI cannot generate from existing knowledge.
What it needs
Requires node 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 Local Dev Loop Overview Set up a fast, cost-effective local development workflow for ElevenLabs audio projects. The loop centers on three moves — mock the SDK so unit tests never burn character quota, gate real API calls behind an explicit ELEVENLABSINTEGRATION=1 flag, and select a cheaper model in dev while keeping the high-quality model for production — with tsx watch hot reload and a quota checker to round out the cycle. Follow the high-level flow below to scaffold the project, then drill into references/implementation.md for the full code of every step and references/examples.md for worked end-to-end runs. Prerequisites Before starting, confirm your environment is ready: The elevenlabs-install-auth setup is complete, so the SDK (@elevenlabs/elevenlabs-js) is installed and ELEVENLABSAPIKEY is available in .env.local. Node.js 18+ with npm or pnpm. vitest installed as the test runner (recommended) — it powers the mock layer and the integration-test guard. Instructions Work through the six steps in order. Each is summarized here; the full code for every step lives in references/implementation.md. 1. Project structure — lay out src/elevenlabs/ (client, config, tts), tests/mocks/ and tests/fixtures/sample.mp3, a git-ignored output/, and .env.local / .env.example. Full tree in the reference. 2. Environment configuration — write an environment-aware config.ts that picks the model and output format by NODEENV. This is the essential skeleton: 3. Mock the SDK — write tests/mocks/elevenlabs.ts that returns the sample.mp3 fixture from textToSpeech.convert/stream and stubs voices.getAll and user.get, so unit tests cost nothing. 4. Development scripts — add dev (tsx watch), test, test:watch, test:integration, generate, and quota scripts to package.json. 5. Quota-aware development — add src/check-quota.ts that reads user.subscription and exits non-zero when fewer than 1000 characters remain, so a low balance fails fast. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/elevenlabs-local-dev-loop