azure-ai-document-intelligence-ts
Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building cu...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-ai-document-intelligence-ts96
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates specific capabilities (extracting text, tables, structured data), names the technology stack (Azure Document Intelligence), and provides explicit trigger scenarios with natural user terms (invoices, receipts, IDs, forms). The description appears truncated ('building cu...') but the visible content is well-structured and distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Extract text, tables, and structured data from documents' and mentions specific document types like 'invoices, receipts, IDs, forms'. Also references the specific technology used. | 3 / 3 |
Completeness | Clearly answers both what ('Extract text, tables, and structured data from documents using Azure Document Intelligence') and when ('Use when processing invoices, receipts, IDs, forms, or building cu...'). Has explicit 'Use when' clause with trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'invoices', 'receipts', 'IDs', 'forms', 'documents', 'extract text', 'tables', 'structured data'. These are terms users naturally use when needing document processing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to specific technology reference (Azure Document Intelligence, @azure-rest/ai-document-intelligence) and specific document types (invoices, receipts, IDs). Unlikely to conflict with generic document or PDF skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and conciseness. The code examples are complete, properly typed, and follow consistent patterns. The main weakness is the length - the content could benefit from progressive disclosure by moving advanced features (custom models, classifiers) to separate files while keeping the SKILL.md focused on common use cases.
Suggestions
Consider splitting custom model building and classifier sections into a separate ADVANCED.md file, keeping SKILL.md focused on prebuilt model usage
Move the prebuilt models table to a REFERENCE.md file and link to it from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without unnecessary explanations of what Azure Document Intelligence is or how REST APIs work. Every section delivers actionable information. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, error handling, and type annotations. The examples are copy-paste ready and cover the full workflow from authentication to result extraction. | 3 / 3 |
Workflow Clarity | The polling pattern section explicitly documents the 5-step async workflow with numbered steps and error checking. The consistent pattern of initialResponse -> isUnexpected check -> poller -> result is demonstrated throughout all examples. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's a long monolithic file (~200 lines) that could benefit from splitting advanced topics (custom models, classifiers) into separate reference files. The prebuilt models table and best practices could also be externalized. | 2 / 3 |
Total | 11 / 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 | |
- 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.