Receive and verify Deepgram webhooks (callbacks). Use when setting up Deepgram webhook handlers, processing transcription callbacks, or handling asynchronous transcription results.
88
81%
Does it follow best practices?
Impact
100%
1.63xAverage score across 3 eval scenarios
Passed
No known issues
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 excellent completeness and distinctiveness. It clearly identifies the Deepgram webhook niche and provides explicit 'Use when' guidance with good trigger terms. The main weakness is that the capability description could be more specific about what actions are performed beyond 'receive and verify'.
Suggestions
Expand the capabilities to include more specific actions like 'parse transcription payloads', 'validate webhook signatures', or 'handle different callback event types' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram webhooks) and two actions (receive and verify), but lacks comprehensive detail about specific capabilities like parsing callback payloads, handling different event types, or error handling. | 2 / 3 |
Completeness | Clearly answers both what ('Receive and verify Deepgram webhooks') and when ('Use when setting up Deepgram webhook handlers, processing transcription callbacks, or handling asynchronous transcription results') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Deepgram', 'webhooks', 'callbacks', 'transcription callbacks', 'asynchronous transcription results'. Good coverage of variations (webhook/callback terminology). | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Deepgram webhooks - the combination of 'Deepgram' + 'webhooks' + 'transcription callbacks' creates a clear niche that is unlikely to conflict with generic webhook or transcription skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid webhook skill with excellent actionability and progressive disclosure. The code examples are complete and executable, and references are well-organized. The main weaknesses are some verbosity in explanations and a lack of a clear sequential workflow for setting up webhook handling end-to-end.
Suggestions
Add a numbered quick-start workflow at the top showing the complete sequence: 1) Set up endpoint, 2) Configure callback URL, 3) Verify authentication, 4) Test with local tunnel
Remove explanatory text that Claude already knows (e.g., what webhooks are, what asynchronous means) to improve conciseness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation (e.g., 'Deepgram webhooks (callbacks) are used to receive transcription results asynchronously' explains what Claude already knows). The table of common fields and some inline comments could be tightened. | 2 / 3 |
Actionability | Provides fully executable code examples in JavaScript with complete webhook handlers, curl commands for making requests, and specific CLI commands for local development. Code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers individual components well but lacks a clear end-to-end workflow sequence. Steps for setting up a complete webhook integration are scattered across sections rather than presented as a numbered sequence with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-organized sections, and clearly signaled one-level-deep references to additional resources (references/, examples/). Navigation to related skills and external patterns is well-documented. | 3 / 3 |
Total | 10 / 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.
f8a4801
Table of Contents
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.