deepgram-js-text-to-speech
Use when writing or reviewing JavaScript/TypeScript in this repo that calls Deepgram Text-to-Speech v1 (`/v1/speak`) for audio synthesis. Covers one-shot REST via `client.speak.v1.audio.generate` and streaming WebSocket via `client.speak.v1.createConnection()` / `connect()`. Use `deepgram-js-voice-agent` when you need full-duplex STT + LLM + TTS instead of one-way synthesis. Triggers include "TTS", "text to speech", "speak", "aura", "streaming TTS", and "speak.v1".
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that hits all the marks: it specifies concrete API methods and endpoints, provides explicit 'Use when' guidance with natural trigger terms, and even disambiguates from a related skill. The description is concise yet comprehensive, making it easy for Claude to select the right skill from a large pool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: one-shot REST via `client.speak.v1.audio.generate`, streaming WebSocket via `client.speak.v1.createConnection()` / `connect()`, and references the specific API endpoint `/v1/speak`. Very concrete and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (Deepgram TTS v1 audio synthesis via REST and WebSocket) and 'when' (explicit 'Use when' clause at the start, plus explicit trigger terms). Also includes a disambiguation clause pointing to a different skill for full-duplex scenarios. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms: 'TTS', 'text to speech', 'speak', 'aura', 'streaming TTS', and 'speak.v1'. These cover common user phrasings and product-specific terms well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific API paths, method names, and an explicit disambiguation from the related `deepgram-js-voice-agent` skill. The niche is clearly scoped to one-way TTS synthesis via Deepgram's JS SDK, making conflicts unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability — both REST and WebSocket paths have complete, executable examples with specific method signatures and message formats. The gotchas section is particularly valuable, capturing non-obvious SDK behaviors. The main weaknesses are minor verbosity in framing sections and missing error-handling/validation guidance for the WebSocket streaming workflow.
Suggestions
Add a brief error-handling checkpoint to the WebSocket workflow (e.g., handling connection errors, Warning events, or reconnection), since streaming is a multi-step process where failures are common.
Trim the 'Central product skills' section to 1-2 lines or move it to a footer — it's tangential to the TTS task and consumes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., the 'Central product skills' section at the bottom, the 'When to use this product' section partially restates what Claude could infer). The gotchas and parameter lists are well-condensed, but the overall document could be tightened by ~15-20%. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready code for both REST and WebSocket paths, with concrete method names, event types, and structured message formats. The gotchas section gives specific, actionable warnings tied to real API behavior. | 3 / 3 |
Workflow Clarity | The REST path is a single call and is clear. The WebSocket path shows the correct sequence (create → register handlers → connect → waitForOpen → sendText → sendFlush) but lacks explicit validation/error-handling checkpoints — no mention of what to do if connection fails, how to handle Warning events, or retry logic for dropped connections. | 2 / 3 |
Progressive Disclosure | Well-structured with a quick start for each mode, a separate key parameters section, layered API references pointing to in-repo files and external docs, and a clear list of example files. References are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- deepgram/deepgram-js-sdk
- Commit
c567b98
- 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.