azure-ai
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/plugins/azure-skills/skills/azure-ai/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its Azure AI domain and provides explicit trigger guidance via a 'WHEN:' clause. Its main strengths are comprehensive trigger term coverage and clear completeness. Its weaknesses are that the capabilities could be more concrete (listing specific actions rather than feature categories) and some generic terms like 'OCR' and 'search' could cause conflicts with non-Azure skills.
Suggestions
Make capabilities more concrete by specifying actions like 'configure search indexes', 'transcribe audio files', 'extract text from scanned documents' rather than just listing feature areas.
Add 'Azure' as a qualifier to generic terms in the WHEN clause (e.g., 'Azure OCR', 'Azure speech-to-text') to reduce conflict risk with non-Azure skills that handle similar tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Azure AI services) and lists several actions like search, speech-to-text, text-to-speech, transcription, and OCR, but these are more like feature areas than concrete specific actions (e.g., it doesn't say 'configure an Azure AI Search index' or 'transcribe audio files'). | 2 / 3 |
Completeness | The description clearly answers both 'what' (Azure AI services for search, speech, OCR, document intelligence) and 'when' with an explicit 'WHEN:' clause listing specific trigger scenarios. The when clause is clearly delineated. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'vector search', 'hybrid search', 'semantic search', 'speech-to-text', 'text-to-speech', 'transcribe', 'OCR', 'AI Search', 'Document Intelligence'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | While Azure-specific terms like 'Azure AI Search' and 'Document Intelligence' are distinctive, generic terms like 'OCR', 'speech-to-text', and 'search' could overlap with non-Azure skills that handle similar capabilities (e.g., a general OCR skill or a generic search skill). | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized reference skill that efficiently maps Azure AI services to their tools, capabilities, and SDK references. Its main weakness is the lack of concrete executable examples—it tells Claude which tools and SDKs exist but doesn't show how to use them with specific parameters or code snippets. Adding even one quick-start example per service would significantly improve actionability.
Suggestions
Add a concrete executable example for at least AI Search and Speech MCP tool usage, showing specific parameters (e.g., `azure__search` with `search_query` including a sample query payload and expected response shape).
Include a brief workflow for common multi-step tasks like 'set up and query a vector search index' or 'transcribe an audio file', with validation checkpoints where appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured using tables to convey information densely. No unnecessary explanations of what Azure services are or how they work conceptually—it jumps straight to actionable reference material. | 3 / 3 |
Actionability | The skill provides specific MCP tool commands and references to SDK guides, but lacks executable code examples. The MCP commands are named but don't show usage with parameters or expected outputs. For SDK usage, it defers entirely to reference files. | 2 / 3 |
Workflow Clarity | There's a clear fallback path (MCP preferred, then setup instructions), but no multi-step workflows are defined for common tasks like setting up a search index, running a hybrid query, or transcribing audio. For a skill covering multiple services, some workflow guidance for at least the primary use cases would be valuable. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in the main file and well-organized one-level-deep references to SDK guides across multiple languages and services, plus links to external Microsoft documentation for deep dives. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/azure-skills
- Commit
742d20b
- 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.