CtrlK
BlogDocsLog inGet started
Tessl Logo

elevenlabs

ElevenLabs integration. Manage data, records, and automate workflows. Use when the user wants to interact with ElevenLabs data.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/elevenlabs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a strong, actionable integration guide: concrete CLI commands, a clear connection state machine with polling, and well-organized sections. Minor trimming and a clearer step numbering would push it to the top level.

DimensionReasoningScore

Conciseness

The body is largely efficient, built from concrete commands, tables, and state-machine docs; only minor bits like the intro paragraph on who uses ElevenLabs and "Use action names and parameters as needed" could be trimmed, matching 'Efficient; minor instances of over-explanation.'

4 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a complete popular-actions table and proxy flag table, fully covering the common cases as in anchor 5.

5 / 5

Workflow Clarity

The install → authenticate → connect → poll-for-ready → search → run sequence is clear with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, but the "skip to Step 2" reference is slightly ambiguous since steps are not consistently numbered, fitting anchor 4.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references and only an external docs link; the large popular-actions table is arguably inline material that could live in a reference file, giving 'Good structure; minor organization gaps.'

4 / 5

Total

17

/

20

Passed

Description

50%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.

The description clearly identifies the ElevenLabs niche and includes an explicit trigger clause, but its actions are generic and it omits the natural TTS/voice keywords users would actually say. Strengthening concrete actions and trigger terms would raise the score.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete ElevenLabs actions such as "generate text-to-speech audio, manage voices, retrieve generation history, and edit voice settings."

Add natural trigger terms users say, e.g. "Use when the user wants to generate speech, voiceovers, or AI voices with ElevenLabs."

Mention file/term synonyms (e.g. TTS, voice cloning, audio generation) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase "Manage data, records, and automate workflows" names the ElevenLabs domain but the actions are generic and not tied to concrete TTS capabilities (e.g. generate speech, manage voices), matching the anchor 'Names the domain but actions are minimal or generic.'

2 / 5

Completeness

Both a 'what' (ElevenLabs integration; manage data, records, automate workflows) and an explicit 'when' ("Use when the user wants to interact with ElevenLabs data") are present, though the 'when' is generic and could be more specific, matching anchor 4.

4 / 5

Trigger Term Quality

Only the brand keyword "ElevenLabs" and the generic phrase "interact with ElevenLabs data" appear; the natural terms users say (text-to-speech, voiceover, AI voice, TTS) are absent, fitting 'One or two generic keywords; missing the natural phrases users say.'

2 / 5

Distinctiveness Conflict Risk

"ElevenLabs integration" is a clear, distinct platform niche with low conflict risk, but the generic action wording leaves minor overlap risk with other data-management skills, fitting 'Mostly distinct; minor overlap risk.'

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-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.