onboarding
Adds ElevenLabs to a project from scratch: browser sign-in, API key creation, SDK install and a test request, driven by the ElevenLabs CLI.
- Kind
- Skill
- Works with
- Any agent
- Source
- ElevenLabs Skills @ 503d4e9fda01
- Path
- onboarding/SKILL.md
- License
- MIT
- Jobs
- Implementation, Automation
InstallInstall it with npx.
npx skills add elevenlabs/skills
# ElevenLabs Onboarding The ElevenLabs CLI runs the whole setup and tells you each step. From the folder of the app that will use the key (in a monorepo, that app's folder), run: ```bash npx -y @elevenlabs/cli@latest onboard init ``` Every `onboard` command prints JSON. Act on it, and keep going until `next` is `done`: - `next`: what to do now, spelled out in `instruction`. - `run`: the exact next command. Run it as given. - `say`: what to tell the user. Tell them as written. - `details`: facts for the next step, such as how the app loads the key and the SDK install command. - `rules`: rules for the whole setup. Follow them. What each `next` means: - `run`: run `run`. - `wait`: the approval page is open. Show `say` (it has the link), then run `run` again right away, without ending your turn. Whenever you give the user the link, copy it whole, exactly as printed: a shortened link doesn't work. - `ask_what_to_build`: tell the user `say`, which asks what they want to build or whether to just add the SDK, and wait for their answer before writing any code. Ask it even if they said earlier, and don't pick a product for them. Once they answer, run `run`. …