Sign in
Explore
Skills · SkillBackend & APIsAPIsReviewedMakes network callsNeeds secrets

setup-api-key

Fixes or hand-configures an existing ElevenLabs API key, checking that ELEVENLABS_API_KEY is set and valid without reading it into the conversation.

Kind
Skill
Works with
Any agent
Source
ElevenLabs Skills @ 503d4e9fda01
Path
setup-api-key/SKILL.md
Jobs
Debugging
Topics
APIs

Credit

Made by
elevenlabs
Original
github.com/elevenlabs/skills/blob/503d4e9fda0190ab9357142f44e…
License
MIT

Listed by Skill Manifest; not made by us.

InstallInstall it with npx.
npx skills add elevenlabs/skills
Install factsScanned 2 Nov 2026
Adds
  • .claude/skills/setup-api-key/ (the skill folder)
Runs scripts
Yes
  • shell block in the text
Uses the network
Yes
  • downloads npm packages
Needs secrets
Yes
  • ELEVENLABS_API_KEY
Reads environment variables
  • ELEVENLABS_API_KEY
Source revision
503d4e9fda01
Licence
MIT
Last activity
28 Oct 2026
Review
Reviewed

Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.

  • Only the main file is read; other files in the folder are not scanned
# ElevenLabs API Key Setup

For a key the user already has, or one that stopped working. For adding
ElevenLabs to a project from scratch, use the `onboarding` skill.

**A key the user already has (for example from an administrator):** don't
sign in for a new one. Tell them to paste it after `ELEVENLABS_API_KEY=` in
the env file of the app that uses it (`.env.local`, or `.env` in a Python
project), never into this chat, and to tell you when it's done. Then check it
(if `check` finds no key, or ElevenLabs rejects it, and offers to sign in,
ask the user to check the paste instead of signing in):

```bash
npx -y @elevenlabs/cli@latest onboard check
```

**A key that stopped working:** run the same command from the app's folder.
It finds the key the app would use (the shell, the env file, or a `.env` up
the tree), checks it with ElevenLabs without printing it, and prints JSON:
`next` is the step (spelled out in `instruction`; where the list below differs,
follow the list), `run` the exact command, and `say` what to tell the user (tell
them as written). Follow it until the key works; for a rejected key it
signs the user in for a new one. What each `next` means:
…