CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-ai-contentunderstanding-py

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

79

11.11x
Quality

69%

Does it follow best practices?

Impact

100%

11.11x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/azure-ai-contentunderstanding-py/SKILL.md

The canonical home for this skill is azure-ai-contentunderstanding-py in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 with executable examples for every scenario and is reasonably concise, but workflow clarity is capped by missing validation checkpoints around destructive and batch analyzer operations.

Suggestions

Add an explicit validation step after create_analyzer and before delete_analyzer (e.g., list/get the analyzer to confirm state) to add a feedback loop.

Trim repeated import boilerplate across examples by showing the shared imports once and focusing later blocks on the operation.

Consider splitting the large per-media-type example set into a reference file and keeping SKILL.md as a concise overview to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly executable code and compact tables with no padded concept explanations, though a few inline comments and the repeated import blocks could be trimmed slightly, fitting anchor 4.

4 / 5

Actionability

Every media type, custom analyzers, async client, and analyzer management have copy-paste-ready executable code covering the common cases, matching anchor 5.

5 / 5

Workflow Clarity

The Core Workflow lists begin/poll/process steps, but there are no validation checkpoints and the destructive delete_analyzer and batch analysis paths lack verification, capping at anchor 3 per the batch/destructive guideline.

3 / 5

Progressive Disclosure

Content is well-organized into clear sections with lean inline examples and no bundle files to reference, fitting anchor 4 for good structure, though it is a single longer file rather than a concise overview pointing outward.

4 / 5

Total

16

/

20

Passed

Description

62%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 clearly states the product and use case with a concrete trigger clause, but its action coverage is narrow (extraction only) and it omits file extensions and synonyms.

Suggestions

Broaden the action list beyond "extraction" (e.g., transcription, field extraction, summaries) to raise specificity.

Add common file extensions and synonyms (e.g., .pdf, .mp4, transcripts) to improve trigger-term coverage.

Tighten the "Use for" clause to a more explicit trigger phrasing such as "Use when extracting content from documents, images, audio, or video for RAG or workflows."

DimensionReasoningScore

Specificity

"multimodal content extraction from documents, images, audio, and video" names the domain and one concrete action across four media types, but does not list multiple distinct actions, matching anchor 3 rather than 4.

3 / 5

Completeness

It states both what ("Azure AI Content Understanding SDK for Python") and when ("Use for multimodal content extraction from documents, images, audio, and video"), with an explicit trigger clause, matching anchor 4 though the when could be more specific.

4 / 5

Trigger Term Quality

"documents, images, audio, and video" are natural media keywords, but file extensions (.pdf, .mp4, .mp3) and common synonyms are absent, fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

The named Azure SDK niche and multimodal extraction triggers are clearly distinct with only minor overlap risk against general document skills, fitting anchor 4 rather than the fully isolated anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.