calesthio/openmontage

setup-api-key

Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools.

First seen Apr 4, 2026

Installation

$ npx skills add calesthio/openmontage --skill setup-api-key

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from calesthio/openmontage · top by installs.

npx skills add calesthio/openmontage

Browse all from calesthio/openmontage

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 56.6K
License LICENSE
Default branch main
Open issues 96
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
CompatibilityRequires internet access to elevenlabs.io and api.elevenlabs.io.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,868 B
  • docs SUMMARY.md 375 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 645 installs

SKILL.md

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 ELEVENLABSAPIKEY:

  1. Check whether ELEVENLABSAPIKEY exists in the current environment.
  2. If it's not in the environment, check .env for ELEVENLABSAPIKEY=<value>.
  3. If an existing key is found, validate it:

`` GET https://api.elevenlabs.io/v1/user Header: xi-api-key: <existing-api-key> ``

  1. 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

  1. 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:

  1. Validate the key by making a request:

`` GET https://api.elevenlabs.io/v1/user Header: xi-api-key: <the-api-key> ``

  1. 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

  1. If validation succeeds, save the API key in a .env file:

`` ELEVENLABSAPIKEY=<the-api-key> ` - If .env already has ELEVENLABSAPIKEY=..., replace that line - Otherwise add a new line for ELEVENLABSAPIKEY`

  1. Confirm success:

> Done! Your key is stored as an environment variable in .env > Keep the key safe! Don't share it with anyone!