Azure AI Document Intelligence SDK for .NET. Extract text, tables, and structured data from documents using prebuilt and custom models.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-ai-document-intelligence-dotnet77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.35xAgent success when using this skill
Validation for skill structure
Discovery
67%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 effectively identifies a specific technology (Azure AI Document Intelligence SDK for .NET) and lists concrete extraction capabilities. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user-facing keywords like 'OCR' or 'form recognition' that users might actually say when needing this skill.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when working with Azure document processing, Form Recognizer, or .NET document extraction'
Include common user terms like 'OCR', 'form recognition', 'invoice processing', 'receipt scanning' that map to Document Intelligence capabilities
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Extract text, tables, and structured data from documents' and mentions 'prebuilt and custom models'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (extract text, tables, structured data using SDK), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Azure AI', 'Document Intelligence', 'extract text', 'tables', 'structured data', but missing common variations users might say like 'OCR', 'form recognition', 'document parsing', or file extensions like '.pdf', '.docx'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Azure AI Document Intelligence SDK for .NET' - this is a specific technology stack that clearly differentiates it from generic document processing skills or other cloud providers' document services. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable SDK reference with excellent executable code examples covering the full range of Document Intelligence capabilities. The main weaknesses are the monolithic structure (could benefit from splitting detailed workflows into separate files) and missing validation/error recovery guidance for long-running operations like model building.
Suggestions
Add validation checkpoints to custom model building workflow (e.g., verify training data exists, check operation status, validate model accuracy before use)
Split detailed workflow examples (sections 4-7) into a separate WORKFLOWS.md file, keeping only the most common use case (invoice/layout analysis) in the main skill
Remove the empty 'When to Use' section or replace with specific trigger conditions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary elements like the 'When to Use' section that adds no value, and some tables could be trimmed. The reference links section is comprehensive but lengthy. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all snippets are copy-paste ready with proper imports, error handling patterns, and complete workflows for invoices, receipts, layout extraction, custom models, and classifiers. | 3 / 3 |
Workflow Clarity | Workflows are clearly numbered and sequenced, but lack validation checkpoints. For operations like building custom models or classifiers (which can fail), there's no guidance on verifying success, handling partial failures, or retry logic. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's monolithic - all content is inline rather than split into separate reference files. The extensive API reference tables and 7 workflow examples could be in separate files with links from a leaner overview. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.