CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-ai-voicelive-py

Build real-time voice AI applications with bidirectional WebSocket communication.

46

Quality

48%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/azure-ai-voicelive-py/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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, actionable SDK reference skill with excellent concrete code examples covering authentication, session configuration, audio streaming, event handling, and common patterns. Its main weaknesses are moderate verbosity (redundant examples, long inline reference tables that could be offloaded), and the lack of an explicit end-to-end workflow with validation checkpoints for what is inherently a multi-step real-time application. The referenced bundle files are missing, undermining the progressive disclosure structure.

Suggestions

Add an explicit end-to-end workflow section with numbered steps and validation checkpoints (e.g., verify session.created before configuring, confirm session.updated before streaming audio, handle connection failures with retry logic).

Move the voice options table, audio formats table, and detailed event type catalog into the referenced files (references/models.md, references/api-reference.md) to slim down the main SKILL.md.

Remove the redundant Quick Start code that duplicates the Authentication section—either merge them or make Quick Start a minimal 5-line example that references the auth section.

Remove or customize the generic 'When to Use' and 'Limitations' boilerplate sections, which add no SDK-specific value.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good code examples, but there's redundancy—the Quick Start section largely duplicates the Authentication section's DefaultAzureCredential example. The voice options table and audio formats table add reference value but the boilerplate 'When to Use' and 'Limitations' sections are generic filler. Some sections like the full event handling block are quite long.

2 / 3

Actionability

The skill provides fully executable, copy-paste ready Python code for every major operation: connection, session configuration, audio streaming, event handling, function calls, manual turn mode, and error handling. Code examples are concrete with real imports, real method calls, and realistic parameters.

3 / 3

Workflow Clarity

The skill covers individual operations well but lacks an explicit end-to-end workflow with validation checkpoints. For a real-time WebSocket application involving audio streaming, there's no clear sequence like 'connect → configure session → verify session.updated event → begin streaming → handle events → gracefully close.' The error handling section exists but isn't integrated into a workflow with feedback loops.

2 / 3

Progressive Disclosure

The References section points to references/api-reference.md, references/examples.md, and references/models.md, which is good structure. However, no bundle files were provided, so these references are unverifiable. The main file itself is quite long (~250 lines of content) and could benefit from moving the detailed event handling catalog and voice/audio format tables into reference files, keeping the SKILL.md as a leaner overview.

2 / 3

Total

9

/

12

Passed

Description

32%

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 domain (real-time voice AI with WebSockets) but is too terse and lacks both specific concrete actions and explicit trigger guidance. It would benefit significantly from listing specific capabilities and adding a 'Use when...' clause with natural user terms.

Suggestions

Add a 'Use when...' clause with trigger terms like 'voice assistant', 'audio streaming', 'speech-to-text', 'real-time audio', 'WebSocket audio', 'conversational AI'.

List specific concrete actions such as 'stream audio input/output', 'handle voice activity detection', 'manage WebSocket connections for audio', 'integrate with speech APIs'.

Include common file types or API names users might reference (e.g., 'OpenAI Realtime API', 'Twilio Media Streams', 'LiveKit') to improve distinctiveness and trigger matching.

DimensionReasoningScore

Specificity

Names the domain ('voice AI applications') and a key technical approach ('bidirectional WebSocket communication'), but does not list multiple concrete actions like 'stream audio', 'handle turn-taking', 'transcribe speech', etc.

2 / 3

Completeness

Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also not very detailed, warranting a 1.

1 / 3

Trigger Term Quality

Includes relevant terms like 'voice AI', 'real-time', and 'WebSocket', but misses common user variations such as 'speech-to-text', 'audio streaming', 'voice chat', 'STT', 'TTS', or 'conversational AI'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'voice AI' and 'WebSocket' is somewhat distinctive, but 'real-time' and 'applications' are generic enough that it could overlap with other real-time communication or WebSocket-related skills.

2 / 3

Total

7

/

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
sickn33/antigravity-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.