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.
95
92%
Does it follow best practices?
Impact
100%
1.53xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly defines a narrow, specific task (ElevenLabs API key setup), provides explicit trigger conditions via a 'Use when...' clause with multiple scenarios, and includes natural keywords users would say. The additional detail about checking existing configuration adds useful behavioral context without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: guides through setup, checks whether ELEVENLABS_API_KEY is already configured and valid, and runs full setup when needed. These are specific, actionable behaviors. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides through setting up an ElevenLabs API key, checks if already configured) and 'when' (explicit 'Use when...' clause with three distinct trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'ElevenLabs API key', 'ElevenLabs MCP tools', 'configure', 'missing API key', 'access to ElevenLabs', and 'ELEVENLABS_API_KEY'. These cover the natural ways a user would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to ElevenLabs API key configuration specifically. The mention of 'ELEVENLABS_API_KEY', 'ElevenLabs MCP tools', and the specific setup workflow make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured setup skill with clear validation checkpoints, concrete API calls, and good error recovery paths. The workflow is particularly strong with its pre-check for existing keys before running the full setup flow. Minor verbosity around service account IP restrictions and some user-facing instructions could be tightened.
Suggestions
Remove or minimize the service account keys/IP allowlist paragraph, as it's tangential to the core setup flow and adds complexity for an edge case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity, such as the detailed explanation about service account keys and IP restrictions which is tangential to the core setup flow. The quoted user instructions are somewhat wordy but largely justified since they're user-facing guidance. | 2 / 3 |
Actionability | Provides concrete API endpoints, specific headers, exact URLs for the user to visit, and clear .env file configuration syntax. Each step has specific, executable guidance rather than vague descriptions. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints at Step 0 (check existing key) and Step 2 (validate new key), clear error recovery paths (retry on failure, exit after second failure), and a logical sequence from checking existing config through to confirmation. | 3 / 3 |
Progressive Disclosure | For a single-purpose skill under 50 lines of core content with no need for external references, the content is well-organized with clear section headers and a logical step-by-step structure. No bundle files are needed for this straightforward setup guide. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- elevenlabs/skills
- Commit
1d16870
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.