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.

Quality

68%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/azure-ai-translation-text-py/SKILL.md

Quality

Content

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, complete code examples covering the full breadth of the Azure Text Translation SDK. The main weaknesses are moderate verbosity (boilerplate sections, some content that could be split out) and a monolithic structure that could benefit from progressive disclosure into separate reference files for advanced features. The 'When to Use' and 'Limitations' sections are generic filler that waste tokens.

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 the main skill focused on core translation workflows.

Trim the 'Best Practices' section to only non-obvious guidance — items like 'use html text_type when translating HTML' are self-evident to Claude.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with executable code examples, but includes some unnecessary sections like the boilerplate 'When to Use' and 'Limitations' sections that add no value, and the 'Best Practices' section contains some obvious advice. The overall length (~200 lines) is reasonable for the breadth of API coverage, but could be tightened.	2 / 3
Actionability	Every section provides fully executable, copy-paste ready Python code with correct imports, method signatures, and response handling. The examples cover all major API methods with concrete parameters and output processing patterns.	3 / 3
Workflow Clarity	This is primarily a reference/API skill rather than a multi-step destructive workflow, so the single-task examples are appropriately clear. Each operation is self-contained and unambiguous, with setup (auth) clearly preceding usage examples. No destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and a summary methods table, but it's a long monolithic file with no references to external files. The dictionary examples, transliteration details, and advanced options could be split into separate reference files to keep the main skill leaner.	2 / 3
	Total	10 / 12 Passed

Description

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 enough trigger detail to help Claude distinguish this from other translation skills. Adding more natural user trigger terms and specific use-case scenarios would significantly improve selection accuracy.

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 Cognitive Services.'

Add natural keyword variations users might say: 'translate', 'convert to English/Spanish/etc.', 'what language is this', 'Azure Translator', 'Cognitive Services translation'.

Differentiate from generic translation by emphasizing SDK-specific aspects, e.g., 'programmatic translation via Azure Cognitive Services REST API or Python/JS SDK integration.'

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 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', '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 in applications' is broad enough to overlap with other translation tools or general i18n skills. Could conflict with other translation-related skills.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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: 9431b67

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.