deepgram-cost-tuning

Optimize Deepgram costs and usage for budget-conscious deployments. Use when reducing transcription costs, implementing usage controls, or optimizing pricing tier utilization. Trigger: "deepgram cost", "reduce deepgram spending", "deepgram pricing", "deepgram budget", "optimize deepgram usage", "deepgram billing".

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/deepgram-pack/skills/deepgram-cost-tuning/SKILL.md

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.

Highly actionable code and commands, but the skill is held back by inline time-sensitive pricing, missing batch-operation validation feedback loops, and an unreferenced bundle file that leaves progressive disclosure underdeveloped.

Suggestions

Move the dated pricing table into references/ (e.g. pricing.md) or a clearly marked section and reference it from the body, so time-sensitive data is one level deep and easy to update.

Add an explicit validate->fix->retry checkpoint around batch transcription (e.g. verify estimated vs actual minutes after a run and halt on budget breach) to raise workflow clarity.

Link the existing references/implementation.md from the body (and turn the bare 'Usage API' / 'Cost Optimization Guide' entries into real links) so progressive disclosure is signaled.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and skill-specific, but the time-sensitive 'Deepgram Pricing (2026)' table sits in the main flow rather than a deprecated section and the $0.0043 rate is hardcoded repeatedly, so it could be tightened.	2 / 3
Actionability	Provides fully executable TypeScript classes, concrete ffmpeg one-liners, real Deepgram API calls, and worked cost-estimation examples that are copy-paste ready.	3 / 3
Workflow Clarity	Steps 1-5 are sequenced and include a budget guardrail, but there is no explicit validate->fix->retry feedback loop for batch transcription; the Error Handling table is reference-style rather than an inline checkpoint, capping this at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	The body is organized into clear sections, but a references/implementation.md bundle exists and is never linked from the body, and 'Resources' lists bare text ('Usage API', 'Cost Optimization Guide') with no navigation, so detail that could be split remains inline.	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.

A strong description with clear 'what' and explicit 'when' triggers and good keyword coverage; the only weakness is that the named capabilities are goal-level rather than concrete operations, capping specificity at 2.

Dimension	Reasoning	Score
Specificity	Names the Deepgram cost domain and several actions ('reducing transcription costs, implementing usage controls, or optimizing pricing tier utilization'), but these are abstract goals rather than the concrete operations (e.g. 'extract text, fill forms') that anchor a 3.	2 / 3
Completeness	Explicitly states what ('Optimize Deepgram costs and usage for budget-conscious deployments') and when ('Use when reducing transcription costs...' plus a Trigger: line), satisfying both halves.	3 / 3
Trigger Term Quality	Triggers 'deepgram cost', 'reduce deepgram spending', 'deepgram pricing', 'deepgram budget', 'optimize deepgram usage', 'deepgram billing' are natural phrases a user would say, with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	A narrow Deepgram cost-optimization niche with Deepgram-specific triggers makes it 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-cost-tuning/SKILL.md
Commit: 399d94c

Reviewed: 4 days 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.