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.

80

11.11x
Quality

71%

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-claude/skills/azure-ai-contentunderstanding-py/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 a dense, well-structured, largely executable reference covering all modalities and sync/async usage. Its main weakness is the absence of validation and error-recovery checkpoints around destructive and long-running operations, which caps workflow clarity.

Suggestions

Add explicit validation checkpoints before destructive operations, e.g. verify an analyzer exists via get_analyzer before delete_analyzer, and confirm analysis succeeded (check poller status) before accessing results.

Introduce an error-recovery feedback loop for long-running analysis (poll -> on failure inspect the error -> retry/adjust), since video/audio analysis can take minutes and fail.

Extract repeated client-construction boilerplate into a single setup snippet referenced from each example, or move per-modality API detail into reference files to reduce inlined duplication.

DimensionReasoningScore

Conciseness

The body is lean with code-forward sections and no padding of concepts Claude already knows, but the client-setup boilerplate is repeated across multiple code blocks, keeping it just below fully efficient.

4 / 5

Actionability

Provides copy-paste-ready executable Python for sync/async clients, all four modalities, custom analyzer creation, and management, with minor gaps around error handling and the result.fields walkthrough.

4 / 5

Workflow Clarity

The Core Workflow sequences begin/poll/process clearly, but destructive (delete_analyzer) and long-running batch operations lack validation checkpoints or error-recovery feedback loops, which caps this dimension at 3 per the rubric precedence rule.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested-reference problem (no bundle files exist), but substantial API-reference-style material is inlined with no one-level-deep references for deeper navigation.

4 / 5

Total

15

/

20

Passed

Description

75%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 specific, third-person, and answers both what the skill does and when to use it, with concrete modality enumeration. It falls just short of top marks because the 'when' clause restates the 'what' and lacks file-extension/synonym trigger terms.

Suggestions

Add concrete trigger phrases and file extensions to the 'when' clause, e.g. 'Use when the user mentions extracting content from PDFs, images (.jpg/.png), audio (.mp3/.wav), or video (.mp4) files'.

Differentiate the 'what' and 'when' so the trigger guidance names user-facing scenarios (RAG ingestion, transcript extraction) rather than restating 'multimodal content extraction'.

DimensionReasoningScore

Specificity

Names the domain and the concrete action of content extraction across four enumerated modalities (documents, images, audio, video), landing above the 1-2-action anchor but short of the multiple-distinct-operations anchor.

4 / 5

Completeness

Provides both a clear 'what' and a 'Use for...' 'when' clause, but the 'when' largely restates the 'what' rather than offering distinct concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural keywords (documents, images, audio, video, content extraction) but omits file extensions (.pdf, .mp4) and synonyms that the top anchor requires.

4 / 5

Distinctiveness Conflict Risk

The named Azure AI Content Understanding niche plus the four-modality combination is mostly distinct, with only minor overlap risk against closely related Azure vision/document services.

4 / 5

Total

16

/

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.

Validation — 15 / 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.