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 well-structured 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 faces', 'analyze picture', and common file extensions like '.jpg', '.png'.
| 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 provider vision APIs. The mention of the specific SDK and its capabilities 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 is a comprehensive API reference with excellent actionability—every code example is executable and covers the full SDK surface. However, it suffers from being a monolithic document that could benefit significantly from splitting detailed per-feature examples into a separate reference file. The boilerplate 'When to Use' and 'Limitations' sections and the repetitive call patterns reduce conciseness.
Suggestions
Split per-feature code examples (Dense Captions, Tags, Objects, OCR, People, Smart Crops) into a separate REFERENCE.md and keep SKILL.md as a quick-start with one combined example showing multiple features, plus links to the reference.
Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no skill-specific value.
Consolidate the Visual Features table with the individual sections—either keep the table as the overview and move examples to a reference file, or remove the table since each feature is already demonstrated.
Integrate error handling into the main usage examples rather than as a separate section, showing it as a validation step in the workflow.
| 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), and the error handling section is disconnected from the main usage examples rather than integrated as validation checkpoints. For a skill involving external API calls, inline validation/error checking would improve clarity. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of code examples with no references to external files and no layered structure. The detailed per-feature examples (dense captions, people detection, smart crops, etc.) could be split into a reference file, keeping SKILL.md as a concise overview with quick-start and links. With no bundle files, everything is crammed 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 | |
9e5d4dd
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.