Azure AI Vision Image Analysis SDK for captions, tags, objects, OCR, people detection, and smart cropping. Use for computer vision and image understanding tasks.
60
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-ai-vision-imageanalysis-py/SKILL.mdQuality
Discovery
85%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 description that clearly identifies the specific SDK (Azure AI Vision) and enumerates six concrete capabilities. The 'Use for...' clause provides trigger guidance, though it could be more detailed with natural user language variations. The description is concise and distinctive but could benefit from more natural trigger terms users might actually say.
Suggestions
Expand trigger terms with natural user phrases like 'read text from image', 'describe a photo', 'detect objects in picture', or mention common image file types (.jpg, .png, .bmp).
Enrich the 'Use for...' clause with more specific scenarios, e.g., 'Use when the user wants to analyze images, extract text from photos, detect objects or people, generate image captions, or perform smart cropping using Azure AI Vision.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: captions, tags, objects, OCR, people detection, and smart cropping. These are clearly defined capabilities within the Azure AI Vision domain. | 3 / 3 |
Completeness | Clearly answers 'what' (Azure AI Vision SDK for captions, tags, objects, OCR, people detection, smart cropping) and 'when' ('Use for computer vision and image understanding tasks'). The 'Use for...' clause serves as an explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some good terms like 'OCR', 'image analysis', 'computer vision', 'image understanding', but misses common user variations like 'read text from image', 'detect objects in photo', 'describe image', 'extract text from picture', or file extensions like '.jpg', '.png'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Azure AI Vision SDK specifically, which distinguishes it from generic image processing skills or other cloud vision APIs. The mention of the specific SDK and its concrete capabilities (smart cropping, people detection) creates a distinct niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable code covering the full Azure AI Vision Image Analysis SDK surface. However, it suffers from being a monolithic reference document with repetitive patterns across feature sections, generic boilerplate at the end, and no progressive disclosure structure. It would benefit significantly from a concise quick-start section with detailed per-feature examples split into a reference file.
Suggestions
Consolidate the seven feature-specific sections into a compact quick-start showing one example with multiple features, then move per-feature details to a separate REFERENCE.md file.
Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no SDK-specific value.
Remove the Visual Features table since each feature is already demonstrated with code — or keep only the table and remove the redundant individual sections.
Integrate error handling into the main workflow as a validation checkpoint rather than a disconnected section at the end.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but it's quite long (~200 lines) with repetitive patterns. Each feature section repeats the full `client.analyze_from_url(...)` call pattern, and the Visual Features table duplicates information already demonstrated in the code sections. The 'When to Use' and 'Limitations' sections are generic boilerplate that add no value. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready Python code with correct imports, proper result handling, and field access patterns. The code covers authentication, all visual features, async usage, and error handling with specific exception types and attributes. | 3 / 3 |
Workflow Clarity | This is primarily an API reference skill rather than a multi-step workflow, so the bar is lower. However, there's no guidance on the sequence of setup steps (install → set env vars → authenticate → analyze), no validation that credentials work before making calls, and the error handling section is disconnected from the main usage patterns rather than integrated as checkpoints. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of code examples with no references to external files and no layered structure. All seven visual features are fully inlined when they could be summarized with a quick-start example and detailed per-feature examples in a separate reference file. With no bundle files, the entire API surface is dumped into one long document. | 1 / 3 |
Total | 8 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
76aea27
Table of Contents
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.