elevenlabs-setup-api-keylisted
Install: claude install-skill trku052-png/social-media-youtube-skills
# 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:
- `run`: run `run`. `wait`: show `say`, then run `run` again right away.
- `ask_user`, or a `fix` that needs the user's shell or secrets: ask them
what `say` says, wait for their answer, then run `run`, unless they said no.
- `write_code`: if the app already reads `ELEVENLABS_API_KEY` (through the
SDK or its own request