azure-ai-translation-ts

Text and document translation with REST-style clients.

Quality

32%

Does it follow best practices?

Impact

Pending

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 ('Use when...'), and sufficient natural keywords. The mention of 'REST-style clients' adds some distinctiveness but is not enough to compensate for the overall lack of detail.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks to translate text or documents between languages, or needs to call a translation API.'

List specific concrete actions such as 'Translates text between languages, translates document files, detects source language, supports batch translation via REST API calls.'

Include natural trigger terms users would say, such as 'translate', 'language', 'localization', 'i18n', 'multilingual', and specific API names if applicable.

Dimension	Reasoning	Score
Specificity	The description mentions 'translation' and 'REST-style clients' but does not list any concrete actions (e.g., translate documents, detect language, batch translate). It remains vague about what specific operations are performed.	1 / 3
Completeness	The 'what' is only weakly stated (translation with REST clients) and there is no 'when' clause or explicit trigger guidance at all. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the weak 'what' brings it down to 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 'translate', 'language', 'localization', 'i18n', or specific API names.	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

Implementation

42%

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

This skill provides a broad API reference for Azure Translation SDKs with numerous code examples, but suffers from being a monolithic document that tries to cover too much inline. Some code examples may not accurately reflect the actual SDK API surface, which undermines actionability. The skill would benefit from splitting into focused sub-files and adding validation/error recovery workflows for batch operations.

Suggestions

Split the content into separate files (e.g., TEXT_TRANSLATION.md, DOCUMENT_TRANSLATION.md, TYPES.md) with SKILL.md serving as a concise overview with links to each.

Verify all code examples against the actual @azure-rest/ai-translation-text SDK API—the translate endpoint body structure appears incorrect and should match the real REST client interface.

Add explicit validation and error recovery steps for batch document translation (e.g., poll status until complete, handle partial failures, retry logic).

Remove the meaningless 'When to Use' section and trim 'Best Practices' to only non-obvious, SDK-specific guidance.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary verbosity. The 'When to Use' section is a meaningless tautology. Some sections like 'Best Practices' contain tips Claude would already know (e.g., 'handle errors'). The overall length (~200 lines) is substantial for what is essentially API reference documentation that could be more tightly organized.	2 / 3
Actionability	The code examples are mostly concrete and executable, but several have issues: the Translate Text example uses a non-standard API shape (inputs with nested targets) that doesn't match the actual Azure REST client SDK—the real API uses query parameters for target languages and a simpler body format. This could lead Claude to generate incorrect code. The batch document translation example is incomplete (missing container initialization).	2 / 3
Workflow Clarity	The batch document translation workflow has a reasonable sequence (generate SAS → start batch → check status → list documents), but lacks explicit validation checkpoints or error recovery steps. For batch/destructive operations like document translation, there's no feedback loop for handling failures, retries, or verifying translated output quality.	2 / 3
Progressive Disclosure	The entire skill is a monolithic document with all API reference content inline. The text translation and document translation sections, key types, and best practices could be split into separate referenced files. There are no references to external files for advanced topics, and the content reads as a wall of code examples without clear navigation hierarchy.	1 / 3
	Total	7 / 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: 33fc69f

Reviewed: 4 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.