azure-ai-voicelive-java

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

2.12x

Quality

66%

Does it follow best practices?

Impact

100%

2.12x

Average score across 3 eval scenarios

Securityby

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

Quality

Content

78%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 strongly actionable, mostly lean SDK guide with a clear core workflow and broad executable examples. Its main weakness is progressive disclosure — all detail lives in one inlined file with no split reference files or signaled deeper navigation.

Suggestions

Move the full voice catalog, function-calling schema details, and extended API reference into separate reference files (e.g. VOICES.md, FUNCTIONS.md) referenced one level deep from SKILL.md.

Add an explicit validation checkpoint after session start (await SESSION_CREATED before configuring/sending audio) to strengthen the workflow.

Replace the vague 'When to Use' filler with concrete trigger conditions for invoking this skill.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable code with useful inline comments and minimal over-explanation of concepts Claude already knows; only minor padding remains (the repeated one-line overview and the vague 'When to Use' filler sentence).	4 / 5
Actionability	Provides copy-paste-ready Java across installation, auth, session lifecycle, configuration, audio I/O, event handling, voice selection, function calling, and error handling — concrete and executable for the common cases.	5 / 5
Workflow Clarity	The Core Workflow is a clear numbered four-step sequence (start → configure → send audio → handle events) with an error-handling section, but there are no explicit validation checkpoints (e.g. confirm SESSION_CREATED before streaming) — this is interactive streaming rather than destructive/batch, so the 3-cap does not apply.	4 / 5
Progressive Disclosure	Sections are well-organized, but everything is inlined in one ~220-line file with no separate reference/bundle files; advanced material (full voice catalog, function-calling schema, API reference) that could be split out is inline, and the only references are external GitHub links rather than signaled one-level-deep local files.	3 / 5
	Total	16 / 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 clearly identifies the product and its core capability but lacks explicit 'when to use' trigger guidance and broader natural-language keywords. It is specific and distinctive but not comprehensive.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers, e.g. 'Use when building real-time voice chat or speech-to-speech AI assistants in Java.'

Include more user-natural synonyms (e.g. 'realtime audio', 'speech', 'voice chat') alongside the product term 'VoiceLive'.

Mention one or two more concrete actions (audio streaming, session configuration, transcription) to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure AI VoiceLive SDK for Java') and one concrete action ('Real-time bidirectional voice conversations with AI assistants using WebSocket'), but coverage is not comprehensive — no mention of audio streaming, configuration, transcription, or function calling.	3 / 5
Completeness	There is a clear 'what' (real-time bidirectional voice conversations via WebSocket) but no 'when' / 'Use when...' trigger guidance in the description, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Contains relevant keywords ('voice conversations', 'AI assistants', 'WebSocket', 'Java', 'real-time') but 'VoiceLive' is product jargon and common synonyms users would actually say (e.g. 'realtime audio', 'speech', 'voice chat') are missing.	3 / 5
Distinctiveness Conflict Risk	The Azure + VoiceLive + Java + WebSocket combination is a clear niche with minimal conflict risk, though 'voice conversations with AI assistants' could mildly overlap with other realtime/audio skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/azure-ai-voicelive-java/SKILL.md
Commit: debb2ec

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.