From elevenlabs
Configure ElevenLabs API key. Use when setting up ELEVENLABS_API_KEY or ElevenLabs tools fail due to missing credentials.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elevenlabs:accessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide the user through obtaining and configuring an ElevenLabs API key.
Guide the user through obtaining and configuring an ElevenLabs API key.
Before asking the user for a key, check for an existing ELEVENLABS_API_KEY:
ELEVENLABS_API_KEY exists in the current environment..env for ELEVENLABS_API_KEY=<value>.GET https://api.elevenlabs.io/v1/user
Header: xi-api-key: <existing-api-key>
Tell the user:
To set up ElevenLabs, open the API keys page: https://elevenlabs.io/app/settings/api-keys
(Need an account? Create one at https://elevenlabs.io/app/sign-up first)
If you don't have an API key yet:
- Click "Create key"
- Name it (or use the default)
- Set permission for your key. If you provide a key with "User" permission set to "Read" this skill will automatically verify if your key works
- Click "Create key" to confirm
- Copy the key immediately - it's only shown once!
Paste your API key here when ready.
Then wait for the user's next message which should contain the API key.
Once the user provides the API key:
Validate the key by making a request:
GET https://api.elevenlabs.io/v1/user
Header: xi-api-key: <the-api-key>
If validation fails:
If validation succeeds, save the API key in a .env file:
ELEVENLABS_API_KEY=<the-api-key>
.env already has ELEVENLABS_API_KEY=..., replace that lineELEVENLABS_API_KEYConfirm success:
Done! Your key is stored as an environment variable in .env Keep the key safe! Don't share it with anyone!
npx claudepluginhub cameri/claude-skills --plugin elevenlabsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.