CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-ai-voicelive-java

Azure AI VoiceLive SDK for Java. Real-time bidirectional voice conversations with AI assistants using WebSocket.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-ai-voicelive-java/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

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

The content is a solid, code-forward quick start with concrete, mostly executable Java examples and a clear core workflow. Its weaknesses are boilerplate 'When to Use'/'Limitations' padding, missing validation/recovery checkpoints in the workflow, and no progressive disclosure — 230 lines of monolithic content where advanced sections should live in reference files.

Suggestions

Delete or replace the boilerplate 'When to Use' and 'Limitations' sections with skill-specific guidance, and drop the line duplicating the frontmatter description.

Split Voice Configuration, Function Calling, and the full event-reference into references/ files (e.g. VOICES.md, EVENTS.md) linked from short overview sections, keeping SKILL.md as a lean quick start.

Add explicit validation checkpoints: check the SESSION_CREATED/ERROR events before streaming, show a concrete reconnection loop in Error Handling, and include the actual close-session code promised by best practice #6.

DimensionReasoningScore

Conciseness

The body is dominated by lean, SDK-specific code with useful comments, but it carries genuine padding: the 'When to Use' section ('This skill is applicable to execute the workflow or actions described in the overview') is contentless boilerplate, the 'Limitations' section is generic filler, and the opening line duplicates the frontmatter description. This is 'mostly efficient but includes some unnecessary explanation' rather than the minor trimming of anchor 4.

3 / 5

Actionability

The guidance is concrete Java with real, specific API calls (builder setup, session options, event dispatch) covering the common cases. It falls short of 5 because fragments rely on undefined placeholders ('readAudioChunk()', 'playAudioChunk()', 'parametersSchema') and the `session` variable in sections 2-3 is never declared in scope, so the examples are not fully copy-paste ready.

4 / 5

Workflow Clarity

The Core Workflow is clearly sequenced (start session, configure options, send audio, handle events), but validation checkpoints are implicit at best — event handling just prints messages, error handling offers only a vague 'Attempt reconnection or cleanup' comment with no concrete recovery loop, and session close (best practice #6) has no code. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, but at ~230 lines everything is inlined in SKILL.md with no bundle files at all — the Voice Configuration, Function Calling, and full event-handling sections are exactly the kind of advanced material that belongs in one-level-deep reference files. This fits 'content that should be separate is inline' (anchor 3); it avoids a 2 only because the structure and navigation within the single file are good.

3 / 5

Total

13

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a specific, distinguishable SDK, but it only states a 'what' with one concrete capability and completely lacks any 'when to use' trigger guidance. Adding a 'Use when...' clause with natural trigger terms would move it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about Azure VoiceLive, real-time voice or speech conversations with AI assistants, or WebSocket audio streaming in Java.'

List 2-3 more concrete capabilities (e.g. 'stream audio input, handle session events, configure voices and turn detection') to raise specificity and completeness together.

Include natural synonyms such as 'speech', 'audio', and 'realtime' alongside 'voice' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure AI VoiceLive SDK for Java') and one concrete capability ('Real-time bidirectional voice conversations'), but the description stops there — no mention of audio streaming, event handling, voice configuration, or function calling that the skill actually covers. This matches the 'names domain and 1-2 concrete actions' anchor, not the 'several specific actions' anchor above.

3 / 5

Completeness

The 'what' is clear (real-time bidirectional voice conversations with AI assistants via this SDK), but there is no 'Use when...' clause or any trigger guidance in the description, which caps completeness at 3 per the judging guidelines. It cannot score 4 because 'when' is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Some relevant natural keywords ('voice', 'real-time', 'AI assistants', 'Java') are present, but common variations users would say — 'speech', 'audio', 'realtime', 'conversation' — are missing, and 'WebSocket' leans technical. Fits 'some relevant keywords but missing common variations' rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The specific SDK name plus 'for Java' carves out a clear niche with minimal conflict risk against generic voice/speech skills, though it could still overlap with other Azure speech or OpenAI realtime skills. 'Mostly distinct; minor overlap risk' is the best fit; a 5 would require distinct trigger phrases, which are absent.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-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.