azure-ai-contentunderstanding-py

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-ai-contentunderstanding-py/SKILL.md

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured with executable examples across all modalities, but workflow clarity is capped by missing validation for long-running/batch and destructive operations, and content is monolithic with no progressive disclosure via reference files.

Suggestions

Add validation/feedback checkpoints for long-running and destructive operations (e.g. poll with timeout guidance, confirm before delete_analyzer, verify analyze result fields exist).

Split bulk API/class reference and async details into reference files (e.g. REFERENCE.md, ASYNC.md) and link them from SKILL.md to improve progressive disclosure.

De-duplicate repeated imports and client construction across examples and replace the generic "When to Use" filler with concrete triggering conditions.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-first body with clear sections and little over-explanation, but repeated imports/client construction across examples and generic "When to Use"/"Limitations" boilerplate could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, self-contained code for document, image, video, audio analysis, custom analyzers, analyzer management, and async usage, covering the common cases comprehensively.	5 / 5
Workflow Clarity	A Core Workflow sequence (begin_analyze -> poll -> process results) is present, but long-running/batch and destructive operations (analyze that can take minutes, delete_analyzer) lack validation checkpoints or feedback loops, capping this at 3.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but all content (including full class/API detail and async usage) is inlined in a single ~270-line SKILL.md with no external reference layer.	3 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is clear, specific, and includes an explicit trigger clause, covering both what and when at a solid level. It could be strengthened by listing several distinct actions and concrete user-facing trigger phrases with file extensions.

Suggestions

Add concrete trigger phrases a user would say, e.g. "Use when the user mentions PDFs, invoices, transcripts, or video keyframes".

Enumerate distinct actions beyond extraction (e.g. transcribe audio, extract invoice fields, generate video summaries) to raise specificity.

Include common file extensions (.pdf, .mp4, .mp3, .jpg) and synonyms to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"multimodal content extraction from documents, images, audio, and video" names the domain and enumerates modalities, but offers only a single concrete action (extraction) rather than several distinct actions.	3 / 5
Completeness	Explicitly states both what (multimodal content extraction) and when ("Use for..."), but the when clause restates the domain rather than giving concrete user-trigger phrases.	4 / 5
Trigger Term Quality	Includes natural modality keywords (documents, images, audio, video) plus a "Use for" trigger, but lacks common synonyms and file extensions like .pdf, .mp4, or .mp3.	4 / 5
Distinctiveness Conflict Risk	Names a specific Azure SDK with a clear niche, with only minor overlap risk against related Azure AI (Document Intelligence, Speech) and general extraction skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/azure-ai-contentunderstanding-py/SKILL.md
Commit: 1f67c44

Reviewed: about 15 hours 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.