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.

68

2.12x
Quality

52%

Does it follow best practices?

Impact

100%

2.12x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-ai-voicelive-java/SKILL.md

The canonical home for this skill is azure-ai-voicelive-java in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

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 SDK reference skill with excellent actionability — every feature has executable Java code with proper imports. The main weaknesses are the lack of validation/verification steps in the WebSocket workflow (connection checks, retry logic) and some verbosity in sections like Key Concepts and Best Practices that don't add much beyond what the code already demonstrates. The 'When to Use' section is entirely vacuous.

Suggestions

Add explicit validation checkpoints to the core workflow: verify session connection before sending config, validate audio format before streaming, and include a reconnection feedback loop for WebSocket failures.

Remove the 'When to Use' section (adds no information) and trim the 'Key Concepts' table and 'Best Practices' list, as most of this is already demonstrated in the code examples.

Consider splitting voice configuration variants and function calling into separate referenced files to keep SKILL.md as a concise overview with progressive disclosure.

DimensionReasoningScore

Conciseness

Generally efficient with good code examples, but includes some unnecessary content like the 'Key Concepts' table describing things Claude can infer, the 'When to Use' section is a meaningless tautology, and the 'Best Practices' section restates what's already shown in the code examples.

2 / 3

Actionability

Provides fully executable Java code for every step: installation via Maven, authentication (two methods), session creation, configuration, audio sending, event handling, voice configuration, function calling, and error handling. All code is copy-paste ready with proper imports.

3 / 3

Workflow Clarity

The core workflow is clearly numbered (1-4) with a logical sequence from session start to event handling. However, there are no validation checkpoints — no verification that the session connected successfully before sending config, no audio format validation, and no feedback loop for error recovery in the main workflow. For a WebSocket-based streaming operation, missing connection validation and retry logic caps this at 2.

2 / 3

Progressive Disclosure

Content is reasonably structured with clear sections, but it's somewhat monolithic — the voice configuration variants, function calling details, and full event handling code could be split into referenced files. The reference links at the bottom are helpful but the inline content is heavy for a SKILL.md overview.

2 / 3

Total

9

/

12

Passed

Description

40%Scale 1-3

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 identifies a clear and distinctive technology niche (Azure AI VoiceLive SDK for Java) but is too terse and lacks explicit trigger guidance. It reads more like a product tagline than a skill description that helps Claude decide when to use it. Adding a 'Use when...' clause and more specific actions would significantly improve its utility for skill selection.

Suggestions

Add a 'Use when...' clause specifying triggers like 'Use when the user asks about Azure AI VoiceLive, real-time voice streaming in Java, WebSocket-based voice conversations, or building voice assistants with Azure.'

List specific concrete actions the skill covers, such as 'Set up WebSocket connections, configure voice input/output streams, handle conversation turns, manage session lifecycle, and integrate with Azure AI services.'

Include additional natural trigger terms users might say, such as 'speech', 'audio streaming', 'voice chat', 'Azure speech', or 'real-time audio'.

DimensionReasoningScore

Specificity

Names the domain (Azure AI VoiceLive SDK for Java) and mentions a key capability (real-time bidirectional voice conversations with AI assistants using WebSocket), but doesn't list multiple specific concrete actions like setup, configuration, streaming, error handling, etc.

2 / 3

Completeness

Describes what the skill is about but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also only moderately detailed, this scores at 1.

1 / 3

Trigger Term Quality

Includes relevant keywords like 'Azure AI', 'VoiceLive', 'Java', 'WebSocket', 'voice conversations', and 'real-time', but misses common user variations like 'speech', 'audio streaming', 'voice chat', 'voice SDK', or 'Azure speech services'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'Azure AI VoiceLive SDK', 'Java', and 'WebSocket' creates a very specific niche that is unlikely to conflict with other skills. The technology stack and product name are highly distinctive.

3 / 3

Total

8

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.