CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-api-key

Fix or hand-configure an existing ElevenLabs API key. Use when a key stopped working (401 or invalid_api_key), when an administrator issued the key, when the user's role cannot create keys, or when the user already has a key and needs it in the right place. Checks whether ELEVENLABS_API_KEY is configured and valid, without reading it into the conversation. Not for first-time setup or adding ElevenLabs to a project (use onboarding).

1.43x
Quality

93%

Does it follow best practices?

Impact

96%

1.43x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

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

An exceptionally tight, fully executable skill: exact commands, a complete decision table for the CLI's guided steps, hard security rules (never read or accept keys in chat), and validation checkpoints with error recovery. The only structural improvement is promoting the two entry flows to their own headers for faster scanning.

Suggestions

Promote 'A key the user already has' and 'A key that stopped working' to `##` headers so the two entry flows are scannable at a glance instead of bold paragraphs.

DimensionReasoningScore

Conciseness

The body is lean throughout: it never explains what an API key or ElevenLabs is, and every line is operational ('Never open, print or `cat` the env file', 'brew install elevenlabs/tap/elevenlabs'). The one explanatory passage — describing what `onboard check` prints — is behavior Claude cannot know and earns its tokens. This matches the 5 anchor: assumes competence, no padding.

5 / 5

Actionability

Fully executable end to end: exact command `npx -y @elevenlabs/cli@latest onboard check`, per-OS install commands (brew, curl installer, PowerShell), the `~/.cargo/bin/elevenlabs` fallback, and an explicit decision table mapping each `next` value (`run`, `wait`, `ask_user`, `write_code`, `offer_test`, `done`) to an action. Copy-paste ready with the common cases (key present, key broken, no npx) all covered.

5 / 5

Workflow Clarity

Both flows are clearly sequenced with validation built in: the paste-then-check loop with recovery ('if `check` finds no key, or ElevenLabs rejects it... ask the user to check the paste instead of signing in'), the CLI-driven loop with a terminal condition ('Follow it until the key works'), and a final checkpoint ('Once the code is written, run `onboard check` before you finish: it verifies the key and the code'). Error-recovery branches (rejected key, missing npx, CLI not on PATH) are all explicit, matching the 5 anchor.

5 / 5

Progressive Disclosure

No bundle files exist and everything is appropriately inline for a skill this size, with clear sections (## Rules, ## No npx). However, the two main entry flows ('A key the user already has' / 'A key that stopped working') run as bold paragraphs under a single unheaded section alongside the `next` semantics list, making top-level navigation slightly less clean than the 'easy navigation' of the 5 anchor — a minor organization gap consistent with 4.

4 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 tight, well-targeted description with explicit what/when triggers, concrete error-code keywords, third-person voice, and explicit boundary routing to the onboarding skill. Its only weaknesses are modest action coverage and a few missing synonyms for key-failure scenarios.

Suggestions

Enumerate the full action set in the description (e.g., 'runs the CLI's guided check and follows its repair steps, falls back to installing the ElevenLabs CLI when npx is unavailable') to lift specificity from 4 to 5.

Add common failure synonyms users actually say — 'expired', 'revoked', or 'unauthorized' key — alongside 401/invalid_api_key to broaden trigger-term coverage.

Optionally name the check command (`elevenlabs onboard check`) in the description so users who see the error in a terminal can match it verbatim.

DimensionReasoningScore

Specificity

Concrete, third-person actions are stated: 'Fix or hand-configure an existing ElevenLabs API key' and 'Checks whether ELEVENLABS_API_KEY is configured and valid, without reading it into the conversation'. It names ~3 specific actions with minor gaps (e.g., the CLI-guided repair loop and the no-npx CLI fallback go unmentioned), which sits between the 'several specific actions; minor gaps' (4) and 'comprehensive' (5) anchors — closer to 4 because coverage of the skill's actual operations is not exhaustive.

4 / 5

Completeness

Explicitly answers both: what ('Fix or hand-configure an existing ElevenLabs API key... Checks whether ELEVENLABS_API_KEY is configured and valid') and when ('Use when a key stopped working (401 or invalid_api_key), when an administrator issued the key, when the user's role cannot create keys, or when the user already has a key and needs it in the right place'), plus a concrete exclusion ('Not for first-time setup or adding ElevenLabs to a project'). This matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

Strong natural phrases users would say: 'key stopped working (401 or invalid_api_key)', 'administrator issued the key', 'ELEVENLABS_API_KEY'. A few common synonyms are missing ('expired', 'revoked', 'unauthorized', 'rotate/reset the key'), so it matches 'good keyword coverage; a few natural terms missing' (4) rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (existing/broken ElevenLabs keys) with distinct triggers (401, invalid_api_key, admin-issued keys) and explicit routing away from the adjacent skill ('Not for first-time setup... use onboarding'), minimizing conflict risk — a clean match for the 5 anchor.

5 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

elevenlabs/skills

Path

setup-api-key/SKILL.md

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.