azure-ai-translation-ts

Text and document translation with REST-style clients.

Quality

43%

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, and natural user-facing 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 between languages using a REST translation API.'

List specific concrete actions such as 'Translates text strings, documents, and files between languages by calling REST translation endpoints, handles language detection, and formats translated output.'

Include natural trigger terms users would say, such as 'translate', 'language', 'localization', 'i18n', 'translation API', and specific service 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, handle language pairs, parse API responses). 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. The missing 'Use when...' clause would cap this at 2 regardless, but the weak 'what' brings it 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', 'API', 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

64%

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, executable code examples covering both text and document translation clients. Its main weaknesses are the monolithic structure (all content inline rather than split across files), missing validation/feedback loops for the batch document translation workflow, and some boilerplate filler content ('When to Use', 'Limitations') that wastes tokens without adding value.

Suggestions

Add explicit validation checkpoints and a polling/retry loop for the batch document translation workflow (e.g., poll status until complete, handle failures).

Remove the generic 'When to Use' and 'Limitations' sections—they add no actionable information and waste tokens.

Consider splitting into a concise SKILL.md overview with quick-start examples, and separate reference files for text translation API details and document translation API details.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some unnecessary sections like 'When to Use' ('This skill is applicable to execute the workflow or actions described in the overview' is vacuous), the generic 'Limitations' boilerplate, and some explanatory comments that Claude wouldn't need. The 'Best Practices' section contains some obvious advice like 'Handle errors'.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples for every operation—authentication, text translation, document translation, transliteration, language detection, batch operations, and status checking. All examples are copy-paste ready with proper imports and error handling.	3 / 3
Workflow Clarity	The batch document translation workflow involves multiple steps (SAS URL generation, starting translation, polling status) but lacks explicit validation checkpoints or a feedback loop for error recovery. The steps are presented as separate code blocks without a clear sequential workflow with verification gates.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and logical grouping, but it's a long monolithic file (~200 lines of code examples) that could benefit from splitting detailed API references into separate files. No external references are provided for advanced topics like batch operation monitoring patterns or error handling strategies.	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: 76cbde3

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.