CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-local-dev-loop

Configure Deepgram local development workflow with testing and mocks. Use when setting up development environment, configuring test fixtures, or establishing rapid iteration patterns for Deepgram integration. Trigger: "deepgram local dev", "deepgram development setup", "deepgram test environment", "deepgram dev workflow", "deepgram mock".

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable, well-sequenced setup guide with executable code throughout, weakened by padded mock objects, missing explicit validation checkpoints, and an unreferenced bundle file whose content duplicates the body.

Suggestions

Add an explicit validation checkpoint between Step 5 and Step 6, e.g. "Run `npm test` and confirm mocked unit tests pass before running integration tests against the real API."

Link references/test-setup.md from the body (e.g. under a "## Test setup details" section) and trim the inline mock/test code that duplicates it, keeping SKILL.md as an overview pointing one level deep.

Shrink the mock response objects to one or two representative word entries each to reduce token cost while still illustrating the API shape.

DimensionReasoningScore

Conciseness

Mostly efficient code-and-commands with no concept re-explanation, but the mock objects pad token budget with repetitive four-entry word-timing arrays where one or two entries would illustrate the shape.

2 / 3

Actionability

Fully executable bash commands, package.json scripts, and complete TypeScript for mocks, unit tests, and integration tests — copy-paste ready with specific API calls and assertions.

3 / 3

Workflow Clarity

Steps 1–6 are clearly sequenced and an error-handling table gives recovery guidance, but there is no explicit validation checkpoint (e.g. "run npm test and confirm mocks pass before adding integration tests") tying the steps together.

2 / 3

Progressive Disclosure

Sections are well-organized, but the bundled references/test-setup.md is never signaled from the body and its mock/test content overlaps with inline code, so content that should be referenced is duplicated rather than split one level deep.

2 / 3

Total

9

/

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.

A strong, third-person description that pairs concrete capabilities with explicit "Use when" guidance and a natural trigger-term list, cleanly answering both what and when. It is distinctive and unlikely to mis-trigger.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Configure Deepgram local development workflow with testing and mocks", "configuring test fixtures", "establishing rapid iteration patterns" — rather than vague language.

3 / 3

Completeness

Clearly answers both what (configure dev workflow with testing and mocks) and when, via an explicit "Use when..." clause plus an explicit Trigger list.

3 / 3

Trigger Term Quality

Lists natural phrases a user would say — "deepgram local dev", "deepgram development setup", "deepgram test environment", "deepgram dev workflow", "deepgram mock" — with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Scoped to Deepgram-specific dev/testing with Deepgram-branded triggers, giving it a clear niche unlikely to conflict with unrelated skills.

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.