elevenlabs-sound-effects
Produce, direct, generate, QA, and integrate non-speech audio with ElevenLabs Text to Sound Effects / Sound Effects API. Use when an agent needs custom SFX, foley, ambience, loops, stingers, impacts, UI sounds, musical one-shots, trailer braams, or sound-design layers for video, ads, social edits, games, apps, podcasts, audiobooks, or interactive media using ElevenLabs.
Profile →npx skills add calesthio/generative-media-skills --skill elevenlabs-sound-effects --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides an agent to produce, direct, generate, QA, and integrate non-speech audio using ElevenLabs text-to-sound-effects tools. Applies to foley, ambience, UI sounds, loops, stingers, and short musical elements for various media formats; directs asset custody, QA, and integration within a project.
How it works
- Translates a production need into a sound-design brief (name function, capture placement, determine one-shot/loop/ambience).
- Chooses generation settings before API call: set duration, loop, prompt_influence, and output_format; default model is eleven_text_to_sound_v2.
- Generates in small batches with variation (3-6 candidates), varying one axis at a time (material, distance, room, etc.).
- Edits and integrates: trim silence/tails, normalize loudness, test loop seams, layer with foley when needed, keep dry and processed versions.
- Records custody metadata: prompt, settings, model_id, output format, date, source endpoint, license notes, usage rights.
- API lifecycle: ensures API key presence, checks plan/licensing, creates deterministic output path, and handles REST or Python SDK usage examples.
When to use it
Use for assets described as acoustic events, textures, short sequences, loopable beds, or one-shots (foley, ambience, cinematic design, UI sounds, social accents, or short musical components).
What it can touch
The skill references actions via the ElevenLabs Sound Effects API and CLI-like examples, including the endpoint POST https://api.elevenlabs.io/v1/sound-generation and parameters such as text, duration_seconds, prompt_influence, model_id, loop, and output_format; it also shows how to save and inspect outputs and how to structure asset manifests.
Caveats
- Includes guidance on commercial use and prophylactic checks per ElevenLabs terms and policies.
- Pricing and generation limits are noted as volatile and should be reconciled with current plans before batch work.
- Rights and usage constraints are outlined, including restrictions on standalone libraries and impersonation concerns.
# ElevenLabs sound effects Use this skill to turn a production need into a usable sound asset: a clear sound-design brief, an ElevenLabs prompt, API settings, custody metadata, and QA notes that make the audio easy to place in an edit, game, app, or ad. The subject is non-speech audio. Use a text-to-speech or voice skill for narration, dialogue, synthetic voices, dubbing, or voice cloning. Use a m
What does the elevenlabs-sound-effects skill do?
Produce, direct, generate, QA, and integrate non-speech audio with ElevenLabs Text to Sound Effects / Sound Effects API. Use when an agent needs custom SFX, foley, ambience, loops, stingers, impacts, UI sounds, musical one-shots, trailer braams, or sound-design layers for video, ads, social edits, games, apps, podcasts, audiobooks, or interactive media using ElevenLabs.
How do I install it?
Run `npx skills add calesthio/generative-media-skills --skill elevenlabs-sound-effects --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From calesthio/generative-media-skills, a repository with 112 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.