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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/azure-ai-voicelive-py/SKILL.md
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, actionable skill with excellent executable code examples covering authentication, session management, audio streaming, event handling, and common patterns. Its main weaknesses are moderate verbosity (redundant auth patterns, inline reference tables that could be in separate files) and the lack of explicit validation checkpoints or error recovery workflows for a system that involves fragile WebSocket connections and real-time audio processing.

Suggestions

Move the voice options and audio formats reference tables into the referenced models.md or api-reference.md files to reduce the main SKILL.md length and improve progressive disclosure.

Add an explicit end-to-end workflow section with numbered steps and validation checkpoints (e.g., verify connection established, confirm session updated, validate audio format before streaming).

Remove the redundant Quick Start authentication code since it duplicates the Authentication section above it—instead, have Quick Start reference the auth section and focus on the event loop pattern.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good code examples, but includes some redundancy (the Quick Start repeats the authentication pattern already shown above, and the boilerplate 'When to Use' and 'Limitations' sections add little value). The voice options and audio formats tables are useful reference material but could be in a separate reference file.

2 / 3

Actionability

The skill provides fully executable, copy-paste ready Python code for every major operation: authentication, session configuration, audio streaming, event handling, function calls, and error handling. All examples are concrete with specific imports, method calls, and parameter values.

3 / 3

Workflow Clarity

The skill presents clear patterns for individual operations (connect, configure, stream, handle events) but lacks an explicit end-to-end workflow with validation checkpoints. For a WebSocket-based real-time system with potential connection failures and audio format mismatches, there are no verification steps or feedback loops for common failure modes.

2 / 3

Progressive Disclosure

References to api-reference.md, examples.md, and models.md are listed at the bottom, but no bundle files were provided to verify they exist. The main file is quite long (~250 lines of content) with reference tables (voices, audio formats) that could be offloaded to the referenced files, keeping the SKILL.md leaner.

2 / 3

Total

9

/

12

Passed

Description

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

Suggestions

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

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

Include common file types or framework names users might mention (e.g., 'OpenAI Realtime API', 'Twilio', 'LiveKit') to improve trigger term coverage and distinctiveness.

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, a missing 'Use when' clause caps completeness at 2, and the 'what' is also quite thin, 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 assistant', '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.

Validation — 10 / 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
popey/claude-code-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.