Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-ai-translation-document-py/SKILL.mdQuality
Discovery
89%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 solid skill description that clearly identifies its niche (Azure AI Document Translation SDK for batch document translation) and provides explicit trigger guidance with specific file formats. Its main weakness is that it could enumerate more specific actions beyond just 'batch translation' to better convey the full range of SDK capabilities.
Suggestions
Add more specific concrete actions such as 'monitor translation jobs, manage glossaries, check translation status' to improve specificity beyond the single action of batch translation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure AI Document Translation SDK) and the primary action (batch translation of documents with format preservation), but doesn't list multiple specific concrete actions beyond translation—e.g., no mention of monitoring translation status, managing glossaries, or handling specific API operations. | 2 / 3 |
Completeness | Clearly answers both 'what' (Azure AI Document Translation SDK for batch translation with format preservation) and 'when' ('Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale'), with an explicit 'Use for...' trigger clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'translate', 'documents', 'Word', 'PDF', 'Excel', 'PowerPoint', 'batch translation', 'document formats', and 'at scale'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—specifies Azure AI Document Translation SDK, batch translation, and format preservation, which clearly distinguishes it from general translation skills, individual file processing skills, or other Azure services. | 3 / 3 |
Total | 11 / 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 API reference skill with excellent actionability—every operation has complete, executable code. However, it reads more like SDK documentation than a task-oriented skill: it lacks a clear end-to-end workflow with validation checkpoints for batch operations, and the monolithic structure could benefit from splitting advanced topics into separate files. Some boilerplate sections ('When to Use', 'Limitations') and minor redundancies reduce token efficiency.
Suggestions
Add an explicit end-to-end workflow section with numbered steps and validation checkpoints: start job → poll status → check document-level errors → retry failed documents → confirm completion.
Move advanced topics (async client, glossary usage, supported formats listing) into separate referenced files to keep the main SKILL.md focused on the core batch translation workflow.
Remove the boilerplate 'When to Use' and 'Limitations' sections, and trim the 'Best Practices' to only non-obvious, SDK-specific guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary content: the 'When to Use' and 'Limitations' sections are boilerplate filler, the supported formats table partially duplicates the programmatic approach shown above it, and the 'Best Practices' section contains some obvious advice Claude would already know (e.g., use minimal permissions, handle errors). | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready code examples for every major operation: authentication (both methods), batch translation, single document translation, glossary usage, async client, status checking, and cancellation. Import statements and environment variable references are consistently included. | 3 / 3 |
Workflow Clarity | The batch translation workflow shows starting a job and checking results, but lacks explicit validation checkpoints and error recovery loops. For a batch operation that could fail at the document level, there's no clear 'check status → handle failures → retry' feedback loop. The steps are presented as isolated code snippets rather than a sequenced workflow with validation gates. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-organized with clear section headers, but it's a long monolithic file (~200 lines) with no references to external files. Some sections like the full async client example, glossary usage, and supported formats could be split into separate reference files to keep the main skill leaner. | 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 | |
9e5d4dd
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.