elevenlabs-webhooks
Receive and verify ElevenLabs webhooks. Use when setting up ElevenLabs webhook handlers, debugging signature verification, or handling call transcription events.
91
88%
Does it follow best practices?
Impact
99%
1.70xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%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-structured skill description with explicit 'Use when...' guidance and strong trigger terms specific to ElevenLabs webhook integration. The main weakness is that the capability description could be more comprehensive about what specific operations are supported beyond receive/verify.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ElevenLabs webhooks) and some actions (receive, verify, setting up handlers, debugging signature verification, handling call transcription events), but doesn't comprehensively list all concrete actions or capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('Receive and verify ElevenLabs webhooks') and when ('Use when setting up ElevenLabs webhook handlers, debugging signature verification, or handling call transcription events') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'ElevenLabs', 'webhooks', 'webhook handlers', 'signature verification', 'call transcription events'. These are specific terms a user working with ElevenLabs would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting ElevenLabs webhooks specifically. The combination of 'ElevenLabs', 'webhooks', and 'signature verification' creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent conciseness and actionability. The code examples are complete and executable across multiple languages/frameworks, and the progressive disclosure is well-structured. The main weakness is workflow clarity - while the code shows what to do, an explicit numbered workflow for setting up and debugging webhooks would strengthen the skill.
Suggestions
Add an explicit numbered workflow section (e.g., '1. Get webhook secret from dashboard, 2. Set environment variable, 3. Implement handler with SDK verification, 4. Test locally with Hookdeck, 5. Deploy and verify') to improve workflow clarity
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples in JavaScript, TypeScript, and Python. Includes specific commands for local development setup and clear environment variable configuration. | 3 / 3 |
Workflow Clarity | While the code examples show the verification flow, there's no explicit step-by-step workflow with validation checkpoints. The handler sequence is mentioned via external reference but not explicitly outlined in the skill itself. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, essential code upfront, and well-signaled one-level-deep references to detailed materials (references/, examples/). Related skills and external resources are clearly organized. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- hookdeck/webhook-skills
- Commit
f8a4801
- 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.