CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-performance-tuning

Optimize Deepgram API performance for faster transcription and lower latency. Use when improving transcription speed, reducing latency, or optimizing audio processing pipelines. Trigger: "deepgram performance", "speed up deepgram", "optimize transcription", "deepgram latency", "deepgram faster", "deepgram throughput".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is concise and highly actionable with executable code, but workflow clarity is capped by missing validation checkpoints for batch operations and progressive disclosure is weakened by an unlinked reference file.

Suggestions

Add explicit validation/verification checkpoints to the batch workflow (e.g., verify each transcription result, retry with reduced concurrency on 429, validate before caching) to support a validate→fix→retry feedback loop.

Split the per-step full implementations out of SKILL.md into references/implementation.md and link to them from each step so the body stays an overview with well-signaled one-level-deep references.

Add a brief 'Verify' step that confirms benchmark throughput meets the stated targets (<2s latency, 100+ files/min) before declaring optimization complete.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — it does not explain what Deepgram or ffmpeg are, and inline comments are functional rather than tutorial padding.

3 / 3

Actionability

Provides fully executable bash and TypeScript (ffmpeg preprocessing, SDK calls, p-limit concurrency, Redis caching) that is copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Steps are numbered and an Error Handling table exists, but the batch-operations step (Step 4) and overall flow lack explicit validate→fix→retry checkpoints, capping batch/destructive workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

The body is a ~300-line monolith with full implementations inline and never links to the existing references/implementation.md bundle, so content that should be split stays inline and the real reference is not signaled.

2 / 3

Total

10

/

12

Passed

Description

100%

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 concise, third-person, and clearly states both capability and trigger conditions with natural keyword coverage. It is a strong, well-scoped skill description.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'faster transcription', 'lower latency', 'improving transcription speed', 'optimizing audio processing pipelines' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Optimize Deepgram API performance for faster transcription and lower latency') and when ('Use when improving transcription speed...') with an explicit Trigger list.

3 / 3

Trigger Term Quality

Gives good coverage of natural phrases a user would say ('speed up deepgram', 'deepgram faster', 'deepgram latency', 'optimize transcription', 'deepgram throughput'), not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Clear Deepgram-specific niche with Deepgram-branded triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

12

/

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.