deepgram-java-conversational-stt
Use when writing or reviewing Java code in this repo that calls Deepgram Conversational STT v2 / Flux over `/v2/listen`. Covers `client.listen().v2().v2WebSocket()`, `V2ConnectOptions`, `onTurnInfo`, and turn-aware close handling. Use `deepgram-java-speech-to-text` for standard v1 transcription and `deepgram-java-voice-agent` for fully interactive assistants. Triggers include "flux", "conversational stt", "listen v2", "turn detection", "end of turn", and "eot".
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 provides specific API-level details, explicit trigger terms, clear 'Use when' guidance, and proactively disambiguates from related skills. 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 and API elements: 'client.listen().v2().v2WebSocket()', 'V2ConnectOptions', 'onTurnInfo', 'turn-aware close handling', and references the specific endpoint '/v2/listen'. Very concrete and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (writing/reviewing Java code for Deepgram Conversational STT v2/Flux, specific API classes and patterns) and 'when' (explicit 'Use when' clause plus trigger terms). Also helpfully disambiguates from related skills ('deepgram-java-speech-to-text' for v1, 'deepgram-java-voice-agent' for agents). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms explicitly listed: 'flux', 'conversational stt', 'listen v2', 'turn detection', 'end of turn', 'eot'. Also includes contextual terms like 'Deepgram', 'Java', and 'v2' that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (Deepgram v2/Flux conversational STT in Java). Explicitly disambiguates from two related skills by name, making conflict very unlikely. The specific API references and endpoint further narrow the scope. | 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 solid, well-structured skill that provides actionable Java code for Deepgram's Conversational STT v2 API. Its strengths are the executable quick start, clear API surface documentation, and well-organized progressive disclosure with layered references. Minor weaknesses include some verbosity in the promotional/routing sections and the lack of explicit error handling or validation steps in the WebSocket workflow.
Suggestions
Add a brief error handling/recovery pattern (e.g., onErrorMessage handler with reconnection logic) to improve workflow clarity for WebSocket failures.
Trim the 'Central product skills' section to a single line or move it to a less prominent position — it reads as promotional rather than instructional.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary sections like the 'Central product skills' promo block and the 'When to use this product' section which could be trimmed. The gotchas section is valuable but slightly verbose with explanations Claude could infer. | 2 / 3 |
Actionability | Provides fully executable Java code for authentication, connection, event handling, and close flow. Import statements are included, method signatures are specific, and the quick start is copy-paste ready with real class names and builder patterns. | 3 / 3 |
Workflow Clarity | The quick start demonstrates a clear sequence (connect → handle events → send media → close), and gotcha #7 explicitly warns about ordering. However, there are no explicit validation checkpoints or error recovery steps for the WebSocket lifecycle, which matters for a streaming connection that can fail. | 2 / 3 |
Progressive Disclosure | Well-structured with a clear hierarchy: quick start for immediate use, key parameters for reference, layered API references pointing to in-repo source, AsyncAPI spec, and external docs. References are one level deep and clearly signaled with specific paths and URLs. | 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-java-sdk
- Commit
de2dd4b
- 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.