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 anchors itself to the Azure AI SDK. However, the 'Use for' clause is too generic and doesn't provide concrete trigger scenarios or natural user phrases. The description would benefit from more explicit trigger guidance and natural keyword variations.
Suggestions
Expand the 'Use for' clause with specific 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 Translator.'
Add natural keyword variations users might say, such as 'translate', 'convert to English/Spanish', 'what language is this', 'Azure Translator', or specific language pairs.
| 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 very generic ('translating text content in applications') and doesn't provide explicit trigger scenarios or user phrases that would help Claude know when to select this over other skills. | 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', 'Azure Translator', or specific file/content types users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Azure AI Text Translation SDK' provides some distinctiveness, but 'translating text content' is broad enough to overlap with other translation tools or general language skills. It could conflict with other translation-related skills if present. | 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 SDK reference skill with excellent actionability — every feature is demonstrated with complete, executable code. The main weaknesses are moderate verbosity (generic boilerplate sections, some redundant inline comments) and a monolithic structure that could benefit from splitting advanced features into separate files. The logical ordering from setup through basic to advanced usage is well done.
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 lookup/examples, transliteration, translation options) into a separate REFERENCE.md to keep SKILL.md as a concise quick-start guide.
Remove obvious inline comments like '# Spanish' after 'es' — Claude already knows language codes.
| 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 comments in code are redundant (e.g., '# Spanish'). The best practices section is reasonably concise but could be tighter. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready Python code with correct imports, method signatures, and result handling. The examples cover all major API methods with concrete parameters and output processing patterns. | 3 / 3 |
Workflow Clarity | This is primarily a single-task SDK reference skill rather than a multi-step destructive workflow. The setup sequence (install → env vars → authenticate → use) is clear and logically ordered. No destructive or batch operations require validation checkpoints beyond what's shown. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a summary methods table, but it's a long monolithic file (~200 lines of examples) with no references to external files. The dictionary examples, transliteration details, and advanced options could be split into separate reference files for better organization. | 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
9e5d4dd
- 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.