azure-ai-contentunderstanding-py

Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video.

Quality

57%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/azure-ai-contentunderstanding-py/SKILL.md

Quality

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 broad content types it handles, which provides a reasonable foundation. However, it lacks specific concrete actions (e.g., 'extract text from scanned documents', 'transcribe audio files'), natural user-facing trigger terms, and a clear 'Use when...' clause with explicit trigger scenarios. It reads more like a library tagline than a skill selection guide.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Extract text from scanned documents, transcribe audio/video, analyze image content, process multimodal files using Azure AI Content Understanding SDK.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Azure Content Understanding, needs OCR on documents, audio transcription, video analysis, or multimodal content processing with Azure.'

Include common file types or extensions users might mention, such as '.pdf', '.mp4', '.wav', '.png', to improve trigger term coverage and distinctiveness.

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' (Azure AI Content Understanding SDK for Python) and a partial 'when' ('Use for multimodal content extraction...'), but the 'when' clause is more of a capability restatement than explicit trigger guidance. It lacks a clear 'Use when the user mentions...' pattern with specific trigger scenarios.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'documents', 'images', 'audio', 'video', and 'content extraction', but misses common user-facing variations like 'OCR', 'transcription', 'image analysis', 'video analysis', or file extensions. 'Azure AI Content Understanding SDK' is fairly technical jargon.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Azure AI Content Understanding SDK' provides some distinctiveness, but 'content extraction from documents, images, audio, and video' is broad enough to overlap with other document processing, image analysis, or audio/video 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 adding error recovery patterns.

Suggestions

Add error handling examples for the long-running poller operations (timeouts, failed analyses, retry logic) to improve workflow clarity for operations that can take minutes.

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 code by establishing it once and referencing it in subsequent examples (e.g., 'Using the client from Authentication above').

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, but it's a monolithic file (~200 lines) with no references to external files. The custom analyzers section and detailed content type examples could be split out, especially since there are no bundle files to support progressive disclosure.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: sickn33/antigravity-awesome-skills
Commit: 76aea27

Reviewed: about 1 hour ago

Table of Contents

Discovery Implementation Validation

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.