azure-ai-contentunderstanding-py
Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.
65
57%
Does it follow best practices?
Impact
Pending
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 broadly categorizes its capabilities across multiple media types, which is helpful. However, it lacks specific concrete actions, natural trigger terms users would say, and an explicit 'when to use' clause, making it harder for Claude to confidently select this skill over alternatives.
Suggestions
Add specific concrete actions for each media type, e.g., 'Extract text and tables from documents, transcribe audio, analyze video frames, perform OCR on images'.
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user needs to extract content from multimedia files using Azure, mentions Content Understanding, or needs multimodal analysis with Azure AI services'.
Include common file extensions and natural user terms like '.pdf', '.mp4', '.wav', 'OCR', 'transcription', 'video analysis' to improve trigger term coverage.
| 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 multimodal content extraction from documents, images, audio, and video'), but lacks an explicit 'Use when...' clause with trigger scenarios describing when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'documents', 'images', 'audio', 'video', 'content extraction', and 'Azure AI', but misses common user variations like 'OCR', 'transcription', 'image analysis', 'video analysis', or specific file types (.pdf, .mp4, .wav). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Azure AI Content Understanding SDK' provides some distinctiveness, but 'content extraction from documents, images' could overlap with other document processing or image analysis skills. The broad scope across four media types increases conflict risk. | 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 SDK reference skill with excellent actionability — every use case has complete, executable code. The main weaknesses are moderate verbosity from repeated boilerplate (client setup, generic limitations section) and missing error handling/validation guidance for what are inherently long-running, potentially failing async operations. The content would benefit from deduplication and adding error recovery patterns.
Suggestions
Add error handling examples for common failure modes (polling timeout, invalid URL, authentication failure) and validation of results before processing — this is important for long-running operations.
Remove the generic 'When to Use' and 'Limitations' boilerplate sections which add no SDK-specific value.
Factor out the repeated client initialization into a single setup section and reference it, rather than repeating imports and credential setup across examples.
Consider splitting custom analyzers, async client, and media-type-specific examples into a separate REFERENCE.md to keep the main skill focused on the core pattern.
| 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. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples for every major use case — document, image, video, audio analysis, custom analyzers, async usage, and analyzer management. Import paths, model classes, and method signatures are all concrete and specific. | 3 / 3 |
Workflow Clarity | The core workflow section outlines the 3-step async pattern clearly, and individual examples demonstrate the pattern. However, there are no validation checkpoints or error handling guidance — no mention of what to do if polling fails, how to handle timeouts for long-running video/audio operations, or how to verify results are valid before processing. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical progression from setup to basic usage to advanced features. However, at ~200 lines it's becoming a wall of content that could benefit from splitting detailed examples (custom analyzers, async client, video/audio specifics) into separate reference files. | 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
431bfad
- 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.