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.

64

Quality

77%

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.

The body delivers executable verification guidance and a clear verify-then-handle workflow, but loses conciseness to redundant multi-language examples and promotional link lists, and ships broken examples/ references. Tightening duplication and fixing dead links would raise the score.

Suggestions

Collapse the three near-identical Node/TypeScript/Python verification blocks into one canonical example plus terse language-specific notes, removing redundancy.

Remove or relocate the 10-link 'Related Skills' promotional list out of the core skill body to reclaim token budget.

Either add the missing examples/express, examples/nextjs, and examples/fastapi directories or drop those references from the Resources section so all links resolve.

DimensionReasoningScore

Conciseness

The body is mostly efficient but pads token budget with three near-identical verification examples (Node, TypeScript, Python repeating constructEvent) and a long 'Related Skills' list of 10 external links that is promotional rather than task-essential. This is more than minor trimming, so it sits at 3 rather than 4.

3 / 5

Actionability

Concrete, copy-paste-ready verification code in three languages plus the exact env var and `npx hookdeck-cli listen 3000 elevenlabs --path /webhooks/elevenlabs` command cover the core task. A minor gap — the empty `# Install via npm (recommended)` block with no actual command — keeps it just below the fully-executable 5 anchor.

4 / 5

Workflow Clarity

The verify-then-handle flow is clear: get raw body and signature, constructEvent, handle event.type, catch and return 401 — with the catch block acting as the error-recovery checkpoint. No destructive/batch cap applies. It lacks an explicit numbered checklist, so it is just below the 5 anchor.

4 / 5

Progressive Disclosure

Structure is good: a concise overview links one level deep to real references/overview.md, setup.md, verification.md (all verified present). However the body also links examples/express/, examples/nextjs/, and examples/fastapi/ which do not exist in the bundle — broken references that keep it below the 5 anchor.

4 / 5

Total

15

/

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.

The description is strong: third-person voice, explicit what-and-when structure, and brand-specific triggers that distinguish it from sibling webhook skills. Minor specificity gains are possible by naming a few more concrete actions.

DimensionReasoningScore

Specificity

Quotes 'Receive and verify ElevenLabs webhooks' and the Use-when list ('setting up ElevenLabs webhook handlers, debugging signature verification, or handling call transcription events') name several concrete actions. It is above the 3 anchor (1-2 actions) but not the fully comprehensive 5 anchor, so 4 fits.

4 / 5

Completeness

It explicitly answers 'what' ('Receive and verify ElevenLabs webhooks') and 'when' via a concrete 'Use when...' clause with three trigger phrases, matching the 5 anchor. The Use-when clause is present, so the missing-trigger cap does not apply.

5 / 5

Trigger Term Quality

Natural terms a user would say are present: 'ElevenLabs webhooks', 'webhook handlers', 'signature verification', 'call transcription events'. Good keyword coverage, but a few natural variations (e.g. 'voice removal', 'callbacks') are missing, placing it just below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

ElevenLabs-specific branding plus signature-verification triggers carve a clear niche with minimal overlap against other provider webhook skills (stripe, shopify, etc.), matching the 5 anchor.

5 / 5

Total

18

/

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

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.