azure-ai-formrecognizer-java
Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or buildi...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-ai-formrecognizer-java91
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/skillValidation 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 identifies the specific Azure service, SDK language, and concrete use cases. It includes explicit 'Use when' guidance with natural trigger terms covering document types (receipts, invoices) and extraction targets (text, tables, key-value pairs). The description is truncated but the visible portion demonstrates excellent structure.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'extracting text, tables, key-value pairs from documents, receipts, invoices' and mentions building applications with a specific SDK. | 3 / 3 |
Completeness | Clearly answers both what ('Build document analysis applications... extracting text, tables, key-value pairs') and when ('Use when extracting text, tables, key-value pairs from documents, receipts, invoices'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Azure Document Intelligence', 'Form Recognizer', 'SDK for Java', 'documents', 'receipts', 'invoices', 'text', 'tables', 'key-value pairs'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Azure Document Intelligence, Form Recognizer, Java SDK) that clearly differentiates it from generic document processing or other cloud provider skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent code examples that are copy-paste ready. The main weaknesses are the lack of validation/verification steps for multi-step operations like model building, and the monolithic structure that could benefit from splitting advanced topics into separate files for better progressive disclosure.
Suggestions
Add validation checkpoints after model building operations (e.g., verify model status, check for training errors, validate model can analyze test documents before production use)
Split advanced topics (Custom Models, Document Classification, Model Management) into separate reference files with a concise overview in the main SKILL.md
Add error recovery guidance for long-running operations like model training that may fail partway through
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing code examples without unnecessary explanations of what Azure Document Intelligence is or how SDKs work. Every section delivers actionable content without padding. | 3 / 3 |
Actionability | All code examples are fully executable Java code with proper imports, complete method calls, and realistic patterns. Examples cover the full workflow from client creation through document analysis and model management. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints and error recovery workflows. For operations like building custom models or composing models, there's no guidance on verifying success or handling partial failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (300+ lines) and could benefit from splitting detailed API patterns into separate reference files. All content is inline rather than appropriately distributed. | 2 / 3 |
Total | 10 / 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.