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.

87

1.50x
Quality

92%

Does it follow best practices?

Impact

87%

1.50x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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, actionable skill for API key setup with strong workflow clarity including validation checkpoints and error recovery paths. The safety rules are appropriate and well-defined. Minor verbosity in the user-facing instructions and some repetition (e.g., 'don't paste key into chat') prevent a perfect conciseness score, but overall the skill is effective and clear.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some verbosity that could be tightened. The quoted user-facing instructions in Step 1 are somewhat lengthy, and some points are repeated (e.g., reminding not to paste the key into chat appears multiple times). However, it avoids explaining concepts Claude already knows.

2 / 3

Actionability

The skill provides concrete, specific guidance at every step: exact API endpoint and header for validation, specific URLs for the user to visit, exact .env format, and clear conditional logic for each outcome. The validation call is clearly specified and copy-paste ready.

3 / 3

Workflow Clarity

The workflow is clearly sequenced (Steps 0→1→2) with explicit validation checkpoints at each stage, feedback loops for invalid keys (retry after fixing), and clear branching logic for success/failure cases. The skill handles edge cases like environment vs .env conflicts explicitly.

3 / 3

Progressive Disclosure

For a single-purpose skill under 100 lines with no need for external references, the content is well-organized with clear sections (Workflow steps, Safety Rules). The structure is appropriate for the scope—no content needs to be split into separate files.

3 / 3

Total

11

/

12

Passed

Description

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 well-crafted skill description that clearly defines its purpose, includes explicit trigger conditions via a 'Use when' clause, and uses natural keywords users would employ. It also adds useful behavioral detail about checking existing configuration before running setup, which helps distinguish it from a generic setup skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: guides through setup, checks whether ELEVENLABS_API_KEY is already configured and valid, runs full setup when needed. These are specific, actionable behaviors rather than vague language.

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 covering three trigger scenarios: configuring API key, tools failing due to missing key, user mentioning ElevenLabs access).

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 with a clear niche: specifically about ElevenLabs API key setup. The repeated mention of 'ElevenLabs' and 'API key' makes it very unlikely to conflict with other skills unless there were another ElevenLabs-specific skill.

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.

Validation11 / 11 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.