CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-common-errors

Diagnose and fix common Deepgram errors and issues. Use when troubleshooting Deepgram API errors, debugging transcription failures, or resolving integration issues. Trigger: "deepgram error", "deepgram not working", "fix deepgram", "deepgram troubleshoot", "transcription failed", "deepgram 401".

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 ./plugins/saas-packs/deepgram-pack/skills/deepgram-common-errors/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

The body is highly actionable and well-structured with executable commands and solution tables, but it functions as a flat reference catalog rather than a routed diagnostic workflow, and it fails to surface the existing implementation.md reference bundle that would offload detail from the main file.

Suggestions

Add a short routing step after the Step 1 diagnostic (e.g. 'Based on the HTTP code or symptom above, jump to Step 2–6') so the catalog becomes a guided workflow with explicit checkpoints.

Link references/implementation.md where relevant (e.g. under Step 4/5) so the validation, splitting, and rate-limiter code lives in the bundle instead of being omitted or duplicated inline.

Remove the meta 'Output' section and fold the 'Error Handling' table into Step 2 or Step 6 to eliminate redundancy and recover tokens.

DimensionReasoningScore

Conciseness

The body is mostly lean tables and executable snippets assuming Claude's knowledge, but the 'Output' section is meta-fluff and the 'Error Handling' table duplicates the retry/backoff guidance already in Step 6, so it could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance throughout: executable curl diagnostics, ffprobe/ffmpeg commands, a retry-with-backoff TypeScript function, and solution tables with specific fixes keyed to error codes.

3 / 3

Workflow Clarity

Steps are numbered and Step 1 offers a triage diagnostic, but the body reads as a reference catalog rather than a routed workflow — there is no explicit 'if symptom X go to step Y' checkpointing or a validate→fix→retry feedback loop outside the single retry snippet.

2 / 3

Progressive Disclosure

Sections are well-organized and a real references/implementation.md bundle exists (audio validation, splitting, rate limiter, WebSocket test), but the body never signals or links that file, and inline code that could delegate to it keeps content that should be split sitting in the main file.

2 / 3

Total

9

/

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.

The description is well-targeted: it states the domain and purpose, gives explicit use-when guidance, and lists natural trigger phrases with a concrete error code. Its only weakness is that the stated capabilities ('diagnose and fix') are generic rather than enumerating several specific concrete actions.

Suggestions

Replace the generic 'Diagnose and fix common Deepgram errors' with a few concrete capabilities, e.g. 'Resolve HTTP error codes, WebSocket disconnects, transcription quality issues, and SDK version errors for the Deepgram API.'

DimensionReasoningScore

Specificity

Names the Deepgram domain and a few actions ('Diagnose and fix common Deepgram errors and issues', 'troubleshooting…debugging transcription failures, or resolving integration issues'), but 'diagnose and fix' is generic rather than a list of multiple distinct concrete actions.

2 / 3

Completeness

Explicitly answers both 'what' ('Diagnose and fix common Deepgram errors and issues') and 'when' ('Use when troubleshooting Deepgram API errors…'), plus an explicit Trigger clause.

3 / 3

Trigger Term Quality

Includes natural user phrases a person would actually say — 'deepgram error', 'deepgram not working', 'fix deepgram', 'deepgram troubleshoot', 'transcription failed', 'deepgram 401' — with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

A clearly Deepgram-specific niche with distinct triggers including 'deepgram 401', making it unlikely to fire for or conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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