azure-ai-translation-ts

Text and document translation with REST-style clients.

Quality

40%

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-ts/SKILL.md

Quality

Discovery

22%

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 description is too terse and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and sufficient natural keywords. The combination of translation and REST clients hints at a niche but is not developed enough to be reliably distinguishable or actionable.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to translate text or documents via a REST translation API, mentions localization, or needs multilingual content.'

List specific concrete actions such as 'Sends text to translation APIs, handles language detection, translates documents between languages, parses translated responses.'

Include natural trigger terms users would say, such as 'translate', 'language', 'localization', 'multilingual', specific API names, or file formats like '.docx', '.txt'.

Dimension	Reasoning	Score
Specificity	The description mentions 'translation' and 'REST-style clients' but does not list any concrete actions (e.g., translate documents, handle language pairs, parse API responses). It remains vague about what specific operations are performed.	1 / 3
Completeness	The description weakly addresses 'what' (translation with REST clients) but completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also too vague to merit a 2.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'translation', 'text', 'document', and 'REST' that users might mention, but misses common variations like 'translate', 'language', 'API', 'localization', or specific file formats.	2 / 3
Distinctiveness Conflict Risk	The combination of 'translation' and 'REST-style clients' provides some specificity, but 'text and document' is broad enough to overlap with general document processing or general REST API skills.	2 / 3
	Total	6 / 12 Passed

Implementation

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides highly actionable, executable TypeScript code examples covering both text and document translation APIs comprehensively. However, it reads more like a complete API reference dumped into a single file rather than a well-structured skill with progressive disclosure. The batch translation workflow lacks explicit validation/polling loops, and the content could be significantly more concise by splitting detailed examples into referenced files.

Suggestions

Split the document into a concise SKILL.md overview with quick-start examples, and move detailed API examples (transliterate, detect, batch translation, formats) into separate reference files like TEXT_TRANSLATION.md and DOCUMENT_TRANSLATION.md.

Add an explicit polling loop with validation for batch document translation (e.g., poll status until 'Succeeded'/'Failed', handle partial failures, include retry logic).

Remove the generic 'When to Use' and 'Limitations' boilerplate sections that add no skill-specific value.

Trim the 'Best Practices' section to only non-obvious guidance that Claude wouldn't already know from the code examples.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with executable code examples, but includes some unnecessary sections like 'When to Use' and 'Limitations' that are generic boilerplate adding no value. The 'Best Practices' section contains some tips Claude would already know (e.g., 'handle errors'). The overall length is substantial for what is essentially an API reference.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples for every operation—authentication, translation, transliteration, detection, document translation, batch operations, and status checking. Code is copy-paste ready with proper imports and error handling patterns.	3 / 3
Workflow Clarity	The batch document translation workflow involves multiple steps (SAS URL generation, batch submission, status polling) but lacks explicit validation checkpoints and a feedback loop for error recovery. There's no clear guidance on what to do if batch translation fails or how to poll until completion. For a multi-step destructive/batch operation, this caps the score at 2.	2 / 3
Progressive Disclosure	The content is a monolithic wall of text with no references to external files and no layered structure. All API reference material, examples, and type definitions are inlined in a single long document. The Key Types section and detailed examples for every endpoint could be split into separate reference files.	1 / 3
	Total	8 / 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: 76aea27

Reviewed: 23 minutes 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.