CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-js-speech-to-text

Use when writing or reviewing JavaScript/TypeScript in this repo that calls Deepgram Speech-to-Text v1 (`/v1/listen`) for prerecorded or live audio transcription. Covers `client.listen.v1.media.transcribeUrl` / `transcribeFile` (REST) plus `client.listen.v1.createConnection()` / `connect()` (WebSocket). Use `deepgram-js-audio-intelligence` for summarize/sentiment/topics/diarize overlays, `deepgram-js-conversational-stt` for Flux turn-taking on `/v2/listen`, and `deepgram-js-voice-agent` for full-duplex assistants. Triggers include "transcribe", "speech to text", "STT", "listen.v1", "nova-3", "live transcription", and "websocket transcription".

80

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

100%

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

A well-structured, executable skill body: concise quick-starts for REST and WebSocket, a dense API-surface map, and a focused Gotchas checklist. It delegates full reference detail to canonical external specs one level deep rather than restating them.

DimensionReasoningScore

Conciseness

Lean throughout — no explanations of concepts Claude already knows; the API-surface list and Gotchas are dense and each token earns its place (e.g. the inline 'Swap this for a mic capture' comment is guidance, not filler).

3 / 3

Actionability

Three copy-paste-ready quick-starts (REST URL, REST file, WebSocket) with real model/language params and exact method calls, plus a concrete list of WSS client messages and server events.

3 / 3

Workflow Clarity

The WSS two-stage flow is explicitly sequenced ('createConnection() → register handlers → connect() → waitForOpen()') and the Gotchas act as checkpoints; transcription is non-destructive so no validate/feedback loop is required.

3 / 3

Progressive Disclosure

No bundle files exist, so judged on inline structure and referenced paths; the 'API reference (layered)' section points one-level-deep to canonical OpenAPI/AsyncAPI/docs and in-repo src paths instead of reproducing them, with example files clearly listed and well-organized sections.

3 / 3

Total

12

/

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 precise, third-person description that names exact SDK methods, gives explicit use-when triggers, and proactively separates itself from adjacent Deepgram skills. It answers what, when, and how-to-distinguish concisely without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and exact SDK method names — `transcribeUrl` / `transcribeFile` (REST) and `createConnection()` / `connect()` (WebSocket) — rather than vague language.

3 / 3

Completeness

Opens with an explicit 'Use when...' clause (when) and states the covered REST + WebSocket surface (what), then enumerates triggers — both halves are explicit.

3 / 3

Trigger Term Quality

Provides a broad trigger list a developer would naturally say ('transcribe', 'speech to text', 'STT', 'live transcription', 'websocket transcription') alongside product-specific terms ('nova-3', 'listen.v1').

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Deepgram v1 STT in JS/TS and actively disambiguates by redirecting summarize/diarize, Flux turn-taking, and full-duplex assistants to three named sibling skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
deepgram/deepgram-js-sdk
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.