Name: azure-ai-document-intelligence-dotnet
Rating: 62.4 (1 reviews)
Author: administrakt0r

azure-ai-document-intelligence-dotnet

Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models.

Quality

73%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-ai-document-intelligence-dotnet/SKILL.md

The canonical home for this skill is azure-ai-document-intelligence-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

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 content is highly actionable with comprehensive executable code examples, but it is a long monolithic file with no progressive disclosure to separate reference material, and destructive workflows lack validation checkpoints.

Suggestions

Move the bulk reference tables (Prebuilt Models, Key Types, Build Modes) and extended code examples into separate reference files linked from the overview to improve progressive disclosure.

Add validation/verification checkpoints to destructive and management workflows, especially around BuildDocumentModel, BuildClassifier, and DeleteModel operations.

Remove the single-row 'Related SDKs' table and the repeated overview sentence to trim redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body is largely lean tables and executable code with sectioned structure, but contains minor trimmable redundancy such as the single-row "Related SDKs" table and a repeated overview sentence, matching the score-4 anchor; not 5 because of these padding instances.	4 / 5
Actionability	Seven numbered workflows plus error handling provide fully executable, copy-paste-ready C# covering the common cases (invoice, layout, receipt, custom model, classifier, classify, manage), matching the score-5 anchor; not 4 because guidance is complete rather than having gaps.	5 / 5
Workflow Clarity	Workflows are numbered and sequenced but lack validation/verification checkpoints, and destructive operations like DeleteModelAsync proceed with no confirm step; per the rubric this caps workflow_clarity at 3. Not 4 because explicit validation checkpoints are absent.	3 / 5
Progressive Disclosure	The file is well-sectioned but ~340 lines with large reference tables (Prebuilt Models, Key Types, Build Modes) and full code examples all inlined in a single SKILL.md with no bundle files split out, matching the score-3 anchor; not 4 because substantial content that belongs in separate reference files is inline.	3 / 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 and distinctive, clearly conveying the SDK's concrete capabilities, but it lacks an explicit "Use when..." trigger clause and omits common user-facing synonyms like PDF/invoices/receipts.

Suggestions

Add an explicit 'Use when ...' clause naming natural trigger phrases, e.g. 'Use when extracting text or tables from PDFs, invoices, receipts, or forms in .NET.'

Include common synonyms and file formats users actually say (PDF, invoices, receipts, OCR, forms) to broaden trigger-term coverage.

Keep the third-person voice but ensure the 'when' guidance is as concrete as the 'what' guidance.

Dimension	Reasoning	Score
Specificity	"Extract text, tables, and structured data from documents using prebuilt and custom models" lists multiple concrete actions (extract text, tables, structured data) with comprehensive coverage, matching the score-5 anchor; not 4 because coverage is broad rather than having notable gaps.	5 / 5
Completeness	The description clearly states what the skill does but contains no "Use when..." clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3; not 4 because "when" is entirely absent rather than weakly present.	3 / 5
Trigger Term Quality	Natural terms like "documents", "text", "tables", "structured data" are present, but common variations users say (PDF, invoices, receipts, OCR, forms) are missing, matching the score-4 anchor; not 5 because synonym/extension coverage is incomplete.	4 / 5
Distinctiveness Conflict Risk	"Azure AI Document Intelligence SDK for .NET" names a specific niche with distinct triggers and minimal overlap risk, matching the score-5 anchor; not 4 because the platform+product scoping makes it highly distinguishable.	5 / 5
	Total	17 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-ai-document-intelligence-dotnet/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.