azure-ai-translation-ts
Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliter...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-ai-translation-ts74
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
57%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 demonstrates good structure with specific Azure SDK package names and a 'Use when' clause, but is severely hampered by truncation that cuts off critical information. The specificity to Azure Translation services provides clear distinctiveness, but the incomplete trigger terms and capabilities list reduce its effectiveness for skill selection.
Suggestions
Complete the truncated description to fully list all capabilities (e.g., 'transliteration, document translation, language detection')
Add natural trigger terms users would say like 'translate', 'language conversion', 'localization', 'multi-language'
Finish the 'Use when' clause with complete trigger scenarios (e.g., 'Use when implementing text translation, transliteration, document batch translation, or language detection with Azure services')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Translation SDKs) and mentions specific packages (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document), but the description is truncated and only partially lists actions like 'text translation, transliter...' without completing the list of concrete capabilities. | 2 / 3 |
Completeness | Has a 'Use when' clause which is good, but the description is truncated mid-word ('transliter...'), leaving both the 'what' and 'when' sections incomplete. The explicit trigger guidance exists but is cut off. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Azure Translation', 'JavaScript', 'text translation', and specific SDK package names, but the truncation cuts off what could be additional trigger terms. Missing common variations like 'translate', 'language conversion', 'localization'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Azure Translation SDKs with exact package names (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document), making it clearly distinguishable from generic translation skills or other cloud provider translation services. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality SDK reference skill with excellent actionability and conciseness. The code examples are production-ready with proper error handling patterns. The main weaknesses are the lack of explicit validation/polling loops for async operations and the monolithic structure that could benefit from progressive disclosure to separate files.
Suggestions
Add a complete polling loop example for batch translation that shows waiting for completion with timeout handling
Consider splitting into SKILL.md (quick start + overview) and REFERENCE.md (detailed API examples) to improve progressive disclosure
Add validation checkpoint after batch translation submission to verify the operation was accepted before polling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing code examples without explaining basic concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | All code examples are fully executable TypeScript with proper imports, error handling patterns, and realistic usage. Copy-paste ready with clear variable names and complete function calls. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but the batch document translation workflow lacks explicit validation checkpoints. The status polling pattern is shown but without a complete retry/wait loop for production use. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~200 lines) and could benefit from splitting detailed API examples into separate reference files while keeping SKILL.md as a quick-start overview. | 2 / 3 |
Total | 10 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.