Name: azure-speech-service
Rating: 55.2 (1 reviews)
Author: membranedev

azure-speech-service

Azure Speech Service integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure Speech Service data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-speech-service/SKILL.md

Quality

Content

67%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 body provides concrete, executable Membrane CLI guidance with a clear connect-to-run workflow and useful state checkpoints. It is somewhat padded by the full CRUD action tree and an empty-description actions table, and lacks validation guidance for destructive operations.

Suggestions

Trim the nested CRUD action tree and the 'Popular actions' table (which has empty Description columns) to the most-used actions, or move the full catalog to a referenced file.

Add a validation or confirmation step before destructive actions (Delete Transcription, Delete Project, etc.) to strengthen the workflow checkpoints.

Shorten the Membrane authentication explanation, assuming Claude can follow the documented `membrane login` flow without the surrounding narrative.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but the full nested action CRUD tree and the 'Popular actions' table with empty description columns add padding, and the Membrane auth explanation runs long.	3 / 5
Actionability	Concrete, executable `membrane` commands with flags appear throughout (login, connection ensure, action list/run, request proxy), covering the common cases with copy-paste-ready snippets.	4 / 5
Workflow Clarity	The connect -> wait -> search -> run sequence is clearly ordered with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), though destructive Delete actions lack validation guidance.	4 / 5
Progressive Disclosure	Content is well-sectioned in a single file with no nested references and clear headers; the inlined action tree could be split out but is reasonably organized.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly identifies the skill domain and includes a 'Use when' trigger, but the capability list is generic boilerplate ('manage data, records, workflows') rather than concrete speech-specific actions. Adding concrete Azure Speech capabilities and richer trigger synonyms would lift specificity and trigger-term quality.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Azure Speech actions, e.g. 'Create and manage transcriptions, custom speech models, and endpoint deployments'.

Add natural trigger synonyms such as speech-to-text, text-to-speech, transcription, and voice commands so users phrase requests in their own words.

Drop the generic 'data, records' wording that overlaps with unrelated data-management skills to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain but the actions are generic boilerplate rather than concrete Azure Speech capabilities like transcription or text-to-speech.	2 / 5
Completeness	Both a 'what' (manage data, records, workflows) and a 'when' ('Use when the user wants to interact with Azure Speech Service data') are present, though the 'what' is vague.	4 / 5
Trigger Term Quality	It includes the natural term 'Azure Speech Service' and 'interact with ... data', but misses common synonyms a user would say such as transcription, speech-to-text, or text-to-speech.	3 / 5
Distinctiveness Conflict Risk	The named Azure Speech Service niche is fairly distinct, but the generic 'manage data, records, and automate workflows' phrasing could lightly overlap with other data-management 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: membranedev/application-skills
Path: skills/azure-speech-service/SKILL.md
Commit: f484c82

Reviewed: 5 minutes 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.