CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills/skills/azure-ai-translation-text-py/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Scale 1-3

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 contains executable, well-structured Python code covering the full SDK surface. The main weaknesses are moderate verbosity (generic boilerplate sections, some unnecessary inline comments) and the monolithic structure that could benefit from progressive disclosure via bundle files. Overall it serves as an effective quick-reference for the Azure AI Text Translation SDK.

Suggestions

Remove the generic 'When to Use' and 'Limitations' boilerplate sections — they add no SDK-specific value and waste tokens.

Consider splitting advanced topics (dictionary operations, translation options, async client) into a separate REFERENCE.md to keep SKILL.md as a concise quick-start guide.

DimensionReasoningScore

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 (e.g., '# Spanish') explain things Claude already knows. 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 calls, and result handling. The code covers all major SDK operations (translate, transliterate, dictionary lookup, async, etc.) with concrete examples and proper parameter usage.

3 / 3

Workflow Clarity

This is primarily an API reference skill rather than a multi-step destructive workflow, so validation checkpoints are less critical. The content is clearly sequenced from setup (install → env vars → auth) through basic to advanced operations, and the methods table provides a clear summary. Each operation is self-contained and unambiguous.

3 / 3

Progressive Disclosure

The content is well-organized with clear section headers, but it's a long monolithic file (~200+ lines) that could benefit from splitting detailed sections (dictionary operations, translation options, async usage) into separate reference files. No bundle files exist to offload content, and no references to external files are provided.

2 / 3

Total

10

/

12

Passed

Description

60%Scale 1-3

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 trigger terms could be expanded to include common variations users would naturally say.

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 trigger term variations such as 'translate', 'convert language', 'Azure Translator', 'multi-language', 'foreign language', or specific language pairs users might mention.

DimensionReasoningScore

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

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-skills
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.