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".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and clearly sequenced with proper validation, but the body is a monolithic wall of inline code that ignores an existing reference bundle, hurting token efficiency and navigation.

Suggestions

Link references/implementation.md from the body and move the duplicated callback-server and client-SDK code there, keeping SKILL.md as an overview.

Remove the duplicate /webhooks/deepgram handler in Step 6 and instead show only the idempotency delta against the Step 2 handler.

Collapse the inline curl examples and verbose code comments to reduce tokens without losing actionability.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-focused, but Step 6 redefines the same /webhooks/deepgram handler already built in Step 2, and inline curl/comments add padding that could be trimmed.	2 / 3
Actionability	Every step provides complete, copy-paste-ready TypeScript or curl with real Deepgram parameters, env vars, and a working client SDK, fully executable rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1-6 form a clear sequence with explicit validation checkpoints (HMAC signature verification, idempotency dedup) and feedback loops (return 500 to trigger Deepgram retry, retry/backoff described).	3 / 3
Progressive Disclosure	A bundle file references/implementation.md exists but is never referenced from the body, while ~290 lines of overlapping code (callback server, client SDK) are inlined instead of split out, matching the "content that should be separate is inline" anchor.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 well-structured description with explicit what/when guidance and strong, natural trigger terms. The only weakness is the generic verb "handling", which keeps specificity from the top anchor.

Suggestions

Replace the generic verb "handling" with concrete actions, e.g. "Submit async transcription jobs, verify webhook signatures, and track results via callbacks."

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ("callback and webhook handling for async transcription") but the only verb is the generic "handling" rather than multiple concrete actions like extract/fill/merge.	2 / 3
Completeness	Explicitly answers both what ("Implement Deepgram callback and webhook handling") and when (a "Use when" clause plus an explicit Trigger list), satisfying the both-what-and-when bar.	3 / 3
Trigger Term Quality	The Trigger list ("deepgram callback", "deepgram webhook", "async transcription", "deepgram events", "deepgram notifications", "deepgram async") gives good coverage of natural terms a user would say.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Deepgram callbacks/webhooks for async transcription) with distinct, brand-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/deepgram-pack/skills/deepgram-webhooks-events/SKILL.md
Commit: 0540a62

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.