Setup API Key
Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools. Use when the user needs to configure an ElevenLabs API key, when ElevenLabs tools fail due to missing API key, or when the user mentions needing access to ElevenLabs. First checks whether ELEVENLABS_API_KEY is already configured and valid, and only runs full setup when needed.
$ npx promptcreek add setup-api-keyAuto-detects your installed agents and installs the skill to each one.
What This Skill Does
This skill guides users through obtaining and configuring an ElevenLabs API key, ensuring proper authentication for accessing ElevenLabs services. It validates the key and provides helpful instructions, making it suitable for onboarding new users and troubleshooting API key issues.
When to Use
- Onboard new users to ElevenLabs services.
- Troubleshoot API key configuration issues.
- Validate existing API keys for functionality.
- Guide users through creating an API key.
- Check for existing API keys in the environment.
- Rotate or replace existing API keys.
Key Features
Installation
$ npx promptcreek add setup-api-keyAuto-detects your installed agents (Claude Code, Cursor, Codex, etc.) and installs the skill to each one.
View Full Skill Content
ElevenLabs API Key Setup
Guide the user through obtaining and configuring an ElevenLabs API key.
Workflow
Step 0: Check for an existing API key first
Before asking the user for a key, check for an existing ELEVENLABS_API_KEY:
- Check whether
ELEVENLABS_API_KEYexists in the current environment. - If it's not in the environment, check
.envforELEVENLABS_API_KEY=. - If an existing key is found, validate it:
GET https://api.elevenlabs.io/v1/user
Header: xi-api-key: <existing-api-key>
- If existing key validation succeeds:
- Tell the user ElevenLabs is already configured and working
- Skip the setup flow
- Ask whether they want to replace/rotate the key; if not, stop
- If existing key validation fails:
- Tell the user the existing key appears invalid or expired
- Continue to Step 1
Step 1: Request the 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:
> 1. Click "Create key"
> 2. Name it (or use the default)
> 3. 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
> 4. Click "Create key" to confirm
> 5. 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.
Step 2: Validate and configure
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:
- Tell the user the API key appears to be invalid
- Ask them to try again
- Remind them of the URL: https://elevenlabs.io/app/settings/api-keys
- If it fails a second time, display an error and exit
- If validation succeeds, save the API key in a
.envfile:
ELEVENLABS_API_KEY=<the-api-key>
- If .env already has ELEVENLABS_API_KEY=..., replace that line
- Otherwise add a new line for ELEVENLABS_API_KEY
- Confirm success:
> Done! Your key is stored as an environment variable in .env
> Keep the key safe! Don't share it with anyone!
Supported Agents
Attribution
Details
- License
- MIT
- Source
- admin
- Published
- 3/18/2026
Tags
Related Skills
Agent Protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
Agent Workflow Designer
Agent Workflow Designer
CTO Advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.