deepgram-webhooks-events
Implement Deepgram callback and webhook handling for async transcription. Use when implementing callback URLs, processing async transcription results, or handling Deepgram event notifications. Trigger: "deepgram callback", "deepgram webhook", "async transcription", "deepgram events", "deepgram notifications", "deepgram async".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 solid skill description with excellent trigger term coverage and completeness, clearly specifying both what the skill does and when to use it. Its main weakness is that the capability description could be more specific about the concrete actions performed beyond generic 'implement' and 'handle' verbs. The distinctiveness is strong due to the narrow Deepgram-specific domain.
Suggestions
Add more specific concrete actions such as 'parse webhook payloads', 'verify callback signatures', 'set up callback endpoint routes', or 'process transcription result events' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Deepgram callback/webhook handling) and mentions async transcription, but doesn't list multiple concrete actions beyond 'implement' and 'handle'. It could specify actions like 'parse webhook payloads', 'verify signatures', 'set up callback endpoints', etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Deepgram callback and webhook handling for async transcription) and 'when' (explicit 'Use when' clause with trigger scenarios, plus a dedicated Trigger list). Both components are explicitly stated. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms including 'deepgram callback', 'deepgram webhook', 'async transcription', 'deepgram events', 'deepgram notifications', and 'deepgram async'. These cover the natural variations a user would say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Deepgram's callback/webhook/async transcription niche. The combination of 'Deepgram' with 'callback', 'webhook', and 'async transcription' creates a very distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable skill with excellent executable code examples and a well-sequenced workflow covering the full async transcription lifecycle. Its main weakness is verbosity — the Redis job tracker, full client SDK, and idempotency handler add substantial token cost for patterns that could be referenced separately or condensed. The error handling table and testing instructions are strong practical additions.
Suggestions
Extract Steps 3-4 (Redis tracking, client SDK) into a separate reference file and link from the main skill to reduce token footprint while preserving the core callback pattern.
Trim explanatory comments in code that restate what the code already makes obvious (e.g., '// Deepgram returns immediately with request_id' before logging the request_id).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes more code than necessary — Steps 3 and 4 (Redis tracking, client SDK with poll/wait) add significant length for patterns Claude could derive from the core callback concept. The overview and flow diagram are efficient, but the overall content is heavy for a skill file. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript/bash with real imports, proper error handling, and copy-paste ready patterns. The curl examples, ngrok testing setup, and signature verification are concrete and complete. | 3 / 3 |
Workflow Clarity | The 6-step sequence is clearly ordered from submission through callback handling, job tracking, client polling, local testing, and idempotency. Validation is embedded throughout — signature verification in Step 2, idempotency checks in Step 6, error handling with retry semantics (return 200 vs 500), and the error handling table covers common failure modes with solutions. | 3 / 3 |
Progressive Disclosure | The content is monolithic — all ~200 lines of code are inline with no references to separate files. The Redis tracker, client SDK, and idempotency patterns could be split into separate reference files. The Resources section links to external docs but the skill itself would benefit from better internal organization. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.