azure-ai-contentunderstanding-py
Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.
52
57%
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/antigravity-azure-ai-contentunderstanding-py/SKILL.mdQuality
Discovery
50%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 identifies the specific SDK and general capability but lacks concrete action verbs, explicit trigger guidance, and natural user-facing keywords. It provides a reasonable starting point but needs more specificity in both actions and trigger conditions to reliably distinguish it from other content extraction or document processing skills.
Suggestions
List specific concrete actions such as 'extract text from documents, transcribe audio, analyze video frames, perform OCR on images' instead of the generic 'multimodal content extraction'.
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about Azure Content Understanding, needs to extract structured data from PDFs/images/audio/video using Azure, or mentions the Content Understanding SDK'.
Include common natural language variations users might say, such as 'OCR', 'transcription', 'document parsing', 'video analysis', or specific file extensions like '.pdf', '.mp4', '.wav'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure AI Content Understanding SDK) and a general action ('multimodal content extraction'), but does not list multiple specific concrete actions like 'extract text', 'transcribe audio', 'analyze images', etc. | 2 / 3 |
Completeness | Has a 'what' (multimodal content extraction) and a partial 'when' ('Use for...'), but lacks an explicit 'Use when...' clause with trigger scenarios describing when Claude should select this skill over others. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure AI', 'content extraction', 'documents', 'images', 'audio', 'video', and 'SDK', but misses common user variations like 'OCR', 'transcription', 'analyze video', 'parse document', or specific file types. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Azure AI Content Understanding SDK' is fairly specific to a particular tool, but 'content extraction from documents, images, audio, and video' is broad enough to potentially overlap with other document processing, OCR, or media analysis skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid API reference skill with excellent actionability — every use case has complete, executable code. Its main weaknesses are the lack of error handling/validation guidance for long-running operations and some redundancy in repeated client setup code and generic boilerplate sections. The content would benefit from being trimmed and having error recovery patterns added.
Suggestions
Add error handling and validation for the long-running operation pattern (e.g., try/except around poller.result(), timeout configuration, checking result status before accessing contents).
Remove the generic 'When to Use' and 'Limitations' boilerplate sections — they add no SDK-specific value and waste tokens.
Factor out the repeated client initialization into a single reference and use comments like '# using client from Authentication section' in subsequent examples to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but has some redundancy: the authentication/client setup is repeated across multiple examples, the 'When to Use' and 'Limitations' sections are generic boilerplate that adds no value, and some best practices state obvious things Claude would already know (e.g., 'use async client for high-throughput scenarios'). | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples for every major use case: document analysis, image analysis, video analysis, audio analysis, custom analyzers, async usage, and analyzer management. Import paths, method signatures, and result access patterns are all concrete and specific. | 3 / 3 |
Workflow Clarity | The core workflow section outlines the 3-step async pattern clearly, but there are no validation checkpoints or error handling guidance. For long-running operations that can fail (video/audio taking minutes), there's no mention of error recovery, timeout handling, or how to check for failures in the poller result. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical progression from simple to complex use cases. However, at ~200 lines it's a monolithic file with no references to external files; the custom analyzers section and detailed content type examples could be split out to keep the main skill leaner. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- boisenoise/skills-collections
- Commit
8ac11ab
- 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.