CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-ai-contentunderstanding-py

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

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

65%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.

A dense, largely executable reference for the SDK whose code examples cover the common cases well. Its weaknesses are the absence of explicit validation/error-recovery checkpoints in the workflow and the monolithic single-file layout that inlines detail a references/ bundle would carry.

Suggestions

Add explicit validation checkpoints to the workflow: try/except around poller.result() with failure reporting, an explicit 'check contents is non-empty before indexing' step in the result-handling examples, and a confirm-before-delete note on delete_analyzer.

Split per-modality deep dives (video/audio transcript and key-frame details, custom analyzer field-schema reference) into references/ files and keep SKILL.md as a quick-start overview with clearly signaled one-level-deep links.

Make each modality snippet self-contained (client setup or a stated 'assumes client from above') and add one local-file upload example to complement the URL-only inputs.

DimensionReasoningScore

Conciseness

Lean body dominated by code, tables, and terse prose that assumes Claude's competence, with only minor trimmable repetition — client/endpoint setup and imports are re-shown across six snippets.

4 / 5

Actionability

Mostly executable, copy-paste-ready code covering install, auth, all four modality analyses, custom analyzers, management, and async, with minor gaps: image/video/audio snippets assume an earlier-defined client and no local-file (non-URL) input example or error handling is shown.

4 / 5

Workflow Clarity

The Core Workflow (begin_analyze → poll → process) is a clear sequence, but validation checkpoints are only implicit prose advice, and the destructive delete_analyzer operation and batch-like long-running analysis lack explicit validation/feedback loops, capping this at 3.

3 / 5

Progressive Disclosure

Well-organized single file with clear section headers, but ~275 lines inline per-modality deep dives, custom-analyzer schema details, and async patterns — content that belongs in separate reference files — with no reference file structure at all.

3 / 5

Total

14

/

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.

A solid description that clearly identifies the product and its core capability with an explicit 'Use for' clause. It would benefit from listing more of the SDK's concrete capabilities and from a more distinct 'when to use' statement that goes beyond restating the what.

Suggestions

Enumerate the concrete extraction capabilities (e.g., transcribe audio with timestamps, extract invoice fields, generate markdown for RAG) so specificity reaches comprehensive coverage.

Add trigger phrases users would naturally say, such as 'when the user mentions transcription, invoice extraction, or needs markdown from PDFs/audio/video for RAG', to sharpen the 'when' clause and trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Azure AI Content Understanding SDK for Python') with one concrete action ('multimodal content extraction') spanning four input types, but is not comprehensive — transcription timing, invoice field extraction, and custom analyzer creation are absent.

3 / 5

Completeness

Both 'what' and 'when' are present via an explicit 'Use for...' clause, but the 'when' largely restates the 'what' rather than providing distinct concrete trigger phrases.

4 / 5

Trigger Term Quality

Good keyword coverage with natural phrases like 'multimodal content extraction', 'documents, images, audio, and video', and the SDK name, but misses common synonyms (transcribe, invoice extraction, RAG) and file extensions.

4 / 5

Distinctiveness Conflict Risk

The Azure-specific SDK naming creates a clear niche with distinct triggers, but 'multimodal content extraction from documents' has minor overlap risk with generic document-extraction and Azure Document Intelligence skills.

4 / 5

Total

15

/

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

sickn33/agentic-awesome-skills

Path

skills/azure-ai-contentunderstanding-py/SKILL.md

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.