CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

81

1.41x
Quality

92%

Does it follow best practices?

Impact

85%

1.41x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable single-purpose skill with clear sequencing and validation checkpoints. Its main weakness is redundancy: the validation request and key-handling rules are repeated across steps where consolidation would reduce token load.

Suggestions

Define the validation HTTP request once (e.g., in Step 0) and reference it from Step 2 instead of repeating the GET https://api.elevenlabs.io/v1/user block verbatim.

State the key-handling/redaction rule once in Safety Rules and reference it from the workflow steps rather than restating it in Step 0, the Step 1 quote, and Step 2.

Consider trimming the Step 1 quoted block (e.g., the account-creation aside and repeated 'do not paste the key' lines) once the safety rule is centralized.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the validation HTTP request is repeated verbatim in Step 0 and Step 2, and the key-handling/redaction rule is restated across Step 0, the Step 1 quote, Step 2, and Safety Rules — it could be tightened, so it does not meet the 'every token earns its place' bar.

2 / 3

Actionability

Provides fully executable guidance: concrete HTTP requests with method, URL, and headers (GET https://api.elevenlabs.io/v1/user with xi-api-key header), specific URLs, and an exact .env line, all copy-paste ready.

3 / 3

Workflow Clarity

Steps 0, 1, and 2 are clearly sequenced with explicit validation checkpoints and failure feedback loops (e.g., Step 2 asks the user to replace the .env value and retry on validation failure).

3 / 3

Progressive Disclosure

No bundle files exist and the skill is self-contained; content is organized into well-signaled sections (Workflow with Steps 0/1/2 and Safety Rules), which per the simple-skills note merits a 3 for a single-purpose skill with no need for external references.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description written in third person that clearly states what the skill does and when to use it, with concrete actions and natural trigger terms. It is distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'setting up an ElevenLabs API key', 'checks whether ELEVENLABS_API_KEY is already configured and valid', 'only runs full setup when needed' — matching the anchor for several specific concrete actions rather than just naming the domain.

3 / 3

Completeness

Explicitly answers both 'what' ('Guides users through setting up an ElevenLabs API key for ElevenLabs MCP tools') and 'when' ('Use when the user needs to configure...') with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural user phrasing such as 'configure an ElevenLabs API key', 'ElevenLabs tools fail due to missing API key', and 'needing access to ElevenLabs', giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The skill occupies a clear ElevenLabs-specific niche with triggers tied to ElevenLabs tool failures and API-key configuration, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
elevenlabs/skills
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.