CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-ai

Build and troubleshoot Azure AI Search, Speech, OpenAI, and Document Intelligence apps. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, Speech SDK logs, session ID, result ID, OCR, convert text to speech.

Quality

83%

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

The canonical home for this skill is azure-ai in microsoft/GitHub-Copilot-for-Azure

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured routing skill: lean tables, concrete MCP commands, an explicit MCP-fallback branch, and verified one-level-deep SDK references. Weaknesses are minor — a duplicated diagnostics link, no inline executable code, and a handful of bundle files (speech sub-docs, scripts, auth-best-practices.md) that are buried or orphaned from the top-level overview.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with no concept explanations aimed at novices (' azure__search` with command `search_index_list`', the Services routing table), but has minor trims available: the diagnostics.md link appears twice (Speech Capabilities table and Service Details), and the capability tables mildly restate known concepts ('Full-text search | Linguistic analysis, stemming'). This fits the 4 anchor ('efficient; minor instances... that could be trimmed') rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable guidance dominates: named MCP tool/command pairs ('azure__speech` with command `speech_transcribe'), real CLI ('az search'), and a specific MCP-unavailable fallback ('ask the user to run `/mcp` and enable Azure MCP'). Minor gaps keep it from 5: no example query payloads for `search_query`, and executable SDK code is entirely delegated to reference files rather than shown even once.

4 / 5

Workflow Clarity

The decision flow is clear and unambiguous: a Services table routes to the right service, then an explicit branch ('When Azure MCP is enabled' vs. 'If Azure MCP is not enabled') tells Claude exactly what to do in each state. No destructive or batch operations exist, so no validation cap applies; it falls short of 5 only because there are no validation/error-recovery checkpoints, which is acceptable for a routing skill but not exemplary.

4 / 5

Progressive Disclosure

Verified against the actual bundle: all 14 referenced SDK guides exist and are clearly signaled one level deep, and the body is a genuine overview. However, the 7 speech sub-files (collection.md, output.md, interpretation.md, etc.) and the 3 scripts/ launchers are only reachable two levels deep via diagnostics.md, and references/auth-best-practices.md is never linked from SKILL.md at all — real but minor organization gaps matching the 4 anchor.

4 / 5

Total

16

/

20

Passed

Description

86%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.

A strong description with an explicit WHEN trigger clause and comprehensive, synonym-rich trigger terms. The main weakness is the what-clause's limited action vocabulary — only 'build and troubleshoot' — leaving the capability enumeration to the trigger list, and the broad 'OpenAI'/'OCR' terms create minor conflict risk with non-Azure skills.

DimensionReasoningScore

Specificity

The 'what' clause 'Build and troubleshoot Azure AI Search, Speech, OpenAI, and Document Intelligence apps' names four domains but only two action verbs (build, troubleshoot), matching the anchor for 1-2 concrete actions without comprehensive coverage. A score of 4 would require several distinct actions enumerated (extract, fill, convert, etc.), which the what-clause does not provide.

3 / 5

Completeness

It explicitly answers both questions: 'Build and troubleshoot Azure AI Search, Speech, OpenAI, and Document Intelligence apps' (what) and an explicit 'WHEN:' clause with concrete trigger phrases (when). The 4 anchor requires a weaker or less explicit 'when', but here the trigger guidance is explicit and phrase-level, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

'AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, Speech SDK logs, session ID, result ID, OCR, convert text to speech' provides comprehensive natural-term coverage including synonyms (speech-to-text / transcribe / convert text to speech) and troubleshooting-specific phrases users would actually say. This clearly matches the 5 anchor's 'comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

Triggers like 'Azure', 'AI Search', 'Speech SDK logs', and 'session ID' establish a clear niche, but 'OpenAI' and 'OCR' carry minor overlap risk with generic OpenAI-API and document-OCR skills. This fits the 4 anchor ('mostly distinct; minor overlap risk with closely related skills') rather than 5, which demands minimal conflict risk across all triggers.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 16 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 16 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/azure-skills

Path

.github/plugins/azure-skills/skills/azure-ai/SKILL.md

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.