azure-ai-translation-ts

Text and document translation with REST-style clients.

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-ai-translation-ts/SKILL.md

The canonical home for this skill is azure-ai-translation-ts in sickn33/agentic-awesome-skills

Quality

Content

64%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 operation has complete, executable TypeScript examples with proper imports and error handling. However, it's somewhat long for a single SKILL.md file and could benefit from better progressive disclosure by splitting text and document translation into separate reference files. The batch document translation workflow would be stronger with explicit validation/retry steps.

Suggestions

Add explicit error recovery and retry logic for the batch document translation workflow (e.g., poll status in a loop, handle partial failures).

Split the detailed API examples into separate reference files (e.g., TEXT_TRANSLATION.md, DOCUMENT_TRANSLATION.md) and keep SKILL.md as a concise overview with links.

Remove the 'When to Use' section which adds no value, and trim unnecessary inline comments that explain obvious concepts.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some unnecessary content like the 'When to Use' section which is a meaningless tautology, and some explanatory comments that Claude wouldn't need (e.g., 'uses global endpoint'). The overall length is substantial for what is essentially an API reference.	2 / 3
Actionability	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 has a clear sequence (generate SAS URLs → start batch → get status), but lacks explicit validation checkpoints and error recovery steps. For batch/destructive operations like document translation, there's no feedback loop for handling failures or retrying.	2 / 3
Progressive Disclosure	Content is well-structured with clear headers separating text vs document translation, but it's a monolithic file with ~200 lines of API reference that could benefit from splitting into separate files (e.g., text translation reference, document translation reference). No references to external files for advanced topics.	2 / 3
	Total	9 / 12 Passed

Description

22%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.

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 in bulk, parses translated responses.'

Include natural trigger terms users would say, such as 'translate', 'localization', 'language pair', '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, which per the rubric should cap completeness at 2 at best—and since the 'what' is also vague, it scores a 1.	1 / 3
Trigger Term Quality	Contains some relevant keywords like 'translation', 'text', 'document', and 'REST' that users might mention, but misses common variations like specific languages, 'translate', 'localization', 'API', or file format terms.	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 generic REST API skills.	2 / 3
	Total	6 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/azure-ai-translation-ts/SKILL.md
Commit: 7520423

Reviewed: ~9 hours 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.