azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications.
59
68%
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-text-py/SKILL.mdQuality
Discovery
60%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 does a good job listing specific capabilities (translation, transliteration, language detection, dictionary lookup) and anchoring to the Azure AI platform. However, the 'Use for' clause is too generic and doesn't provide strong trigger guidance for skill selection. Adding more natural user trigger terms and explicit scenarios would significantly improve its effectiveness.
Suggestions
Expand the 'Use for' clause with explicit trigger scenarios, e.g., 'Use when the user asks to translate text between languages, detect what language text is in, transliterate scripts, or look up word translations using Azure services.'
Add natural trigger term variations such as 'translate', 'convert to English/Spanish/etc.', 'what language is this', 'Azure Translator', to improve matching against user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'real-time text translation, transliteration, language detection, and dictionary lookup.' These are distinct, well-defined capabilities. | 3 / 3 |
Completeness | The 'what' is well-covered with specific capabilities. There is a 'Use for' clause but it's vague ('translating text content in applications') and doesn't provide explicit trigger scenarios or user phrases that would help Claude distinguish when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'translation', 'transliteration', 'language detection', and 'dictionary lookup', but misses common user variations like 'translate', 'convert language', 'detect language', specific language names, or 'Azure Translator'. The term 'SDK' is more developer-oriented than user-facing. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Azure AI Text Translation SDK' provides some distinctiveness from generic translation skills, but the 'Use for' clause is broad enough ('translating text content') that it could overlap with other translation-related skills. It doesn't clearly distinguish itself from non-Azure translation tools or general language processing skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
77%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 section has executable code examples covering the full SDK surface. The main weaknesses are moderate verbosity (generic boilerplate sections, some redundant comments) and a monolithic structure that could benefit from splitting advanced topics into separate files. The content is well-organized but could be more token-efficient.
Suggestions
Remove the generic 'When to Use' and 'Limitations' boilerplate sections — they add no SDK-specific value and waste tokens.
Consider splitting advanced features (dictionary operations, async client, translation options) into a separate ADVANCED.md to keep the main skill focused on core translation workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements: the 'When to Use' and 'Limitations' sections are generic boilerplate that add no value, and some inline comments are redundant (e.g., '# Spanish'). The best practices section is useful but slightly verbose. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready Python code with correct imports, method calls, and result handling. The examples cover all major SDK operations with concrete parameters and output processing patterns. | 3 / 3 |
Workflow Clarity | This is primarily an API reference skill rather than a multi-step destructive workflow, so the single-task clarity standard applies. Each operation is unambiguous with clear setup (auth) → usage patterns. The methods table provides a clear overview of available operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and logical progression from setup to basic to advanced features. However, at ~200 lines it's a long monolithic file with no references to external files. The dictionary examples, async client, and translation options sections could be split out to keep the main skill leaner. | 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
76aea27
- 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.