CtrlK
BlogDocsLog inGet started
Tessl Logo

elevenlabs-webhooks

Receive and verify ElevenLabs webhooks. Use when setting up ElevenLabs webhook handlers, debugging signature verification, or handling call transcription events.

63

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

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

A well-structured, code-first overview with three complete verification examples and genuine one-level-deep references. The main weaknesses are an empty install command block, a padded Related Skills section, and three referenced example directories that are missing from the bundle.

Suggestions

Fill in the empty npm install code block in 'Local Development' (e.g., 'npm install -g hookdeck-cli' or just remove the block since 'npx' is used next).

Trim the 'Related Skills' section to the few most relevant skills (e.g., webhook-handler-patterns and one or two provider skills) to cut padding tokens.

Either add the referenced examples/express/, examples/nextjs/, and examples/fastapi/ directories to the bundle or remove those three broken links from the Resources section.

DimensionReasoningScore

Conciseness

The body is mostly tight (SDK code, event table, env vars), but it could be tightened: the 'Related Skills' section lists 10 external skills and the 'Recommended: webhook-handler-patterns' section duplicates one of them with four more external links. The 'Local Development' section also contains an empty code block after '# Install via npm (recommended)' with no actual install command.

3 / 5

Actionability

Three complete, executable handlers are provided (Express/Node, Next.js App Router, FastAPI) plus a concrete tunnel command ('npx hookdeck-cli listen 3000 elevenlabs --path /webhooks/elevenlabs'). Minor gaps: the npm install block is empty and the event-handling step is left as a comment placeholder ('// Handle event.type, event.data...').

4 / 5

Workflow Clarity

The verify-first sequence is clear in each example: get raw body → read 'ElevenLabs-Signature' → constructEvent → return 401 on signature failure, 200 on success, with the FastAPI example adding an explicit missing-header check. Not a destructive/batch workflow, so no cap applies; it falls short of a 5 because error-recovery guidance beyond 'return 401 and the error message' is deferred to an external skill rather than included.

4 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, real, one-level-deep references (references/overview.md, setup.md, verification.md all exist). Kept from a 5 by broken bundle paths: 'examples/express/', 'examples/nextjs/', and 'examples/fastapi/' are listed under Resources but those directories do not exist in the skill bundle.

4 / 5

Total

15

/

20

Passed

Description

82%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 concise, third-person description that explicitly answers both what the skill does and when to use it, with natural trigger terms and a clearly bounded ElevenLabs niche. Its only weakness is that the 'what' half understates the full scope covered by the body (event types, voice-removal handling, local testing).

DimensionReasoningScore

Specificity

'Receive and verify ElevenLabs webhooks' names the domain plus exactly two concrete actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It omits other covered capabilities (event-type/payload handling, voice-removal events, local tunnel testing), so it is not a 4.

3 / 5

Completeness

Both halves are explicit and concrete: what ('Receive and verify ElevenLabs webhooks') and when ('Use when setting up ElevenLabs webhook handlers, debugging signature verification, or handling call transcription events'), mirroring the anchor-5 example structure exactly. Not a 4 because the when-clause lists three specific triggers rather than a generic condition.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — 'setting up ElevenLabs webhook handlers', 'debugging signature verification', 'handling call transcription events' — matching 'good keyword coverage; a few natural terms missing.' It lacks synonyms users might say such as 'post_call_transcription', 'voice removal', or 'webhook secret', keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

'ElevenLabs' pins a clear niche with distinct triggers; the only overlap risk is with other provider-specific webhook skills (stripe, shopify, etc.), whose descriptions name different providers. Not a 4 since the provider qualifier makes cross-triggering unlikely.

5 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
hookdeck/webhook-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.