azure-ai-translation-document-py

Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.

Quality

71%

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

Quality

Content

65%Weight 40%Scale 1-5

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

A highly actionable, code-first reference that respects token budget and gives working examples for every major API surface. Its weaknesses are structural: a batch-oriented workflow without an explicit validate-and-retry loop, and a monolithic single-file layout that inlines content better split into reference files.

Suggestions

Add an explicit validation checkpoint to the translation workflow, e.g. after poller.result() iterate client.list_document_statuses(operation_id), inspect doc.error, resubmit or fix failed documents — currently error handling is only a best-practices bullet.

Move stable reference material (supported formats table, glossary/SAS details, async client, status-listing API) into a references/ file and keep SKILL.md as a lean quick-start overview.

Delete the boilerplate 'When to Use' and 'Limitations' sections that restate generic guidance without adding Azure-specific information.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code with no explanations of concepts Claude already knows, but '## When to Use / This skill is applicable to execute the workflow or actions described in the overview' and the generic '## Limitations' boilerplate are filler that could be trimmed.	4 / 5
Actionability	Concrete, mostly copy-paste-ready code covers install, env vars, auth, and the core translation flow; minor gaps remain — the multi-target example uses undefined variables (target_url_es/fr/de) and the single-document example reuses undefined endpoint/key.	4 / 5
Workflow Clarity	The skill drives batch translation jobs, but validation is limited to mentions ('Handle document-level errors by iterating document statuses') rather than an explicit check-failures-and-retry checkpoint sequence, so the batch-operation cap at 3 applies.	3 / 5
Progressive Disclosure	Sections are well-organized with headers, but there are no bundle files — the format tables, glossary usage, status-listing API, and async client are all inlined in a ~250-line SKILL.md where a leaner overview with one-level-deep references would fit the anchor-4/5 pattern.	3 / 5
	Total	14 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete domain naming, natural trigger terms covering the major document formats, and an explicit use-when clause. The main gap is specificity breadth — only two capabilities are named despite the skill covering more operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Azure AI Document Translation SDK') and two concrete actions ('batch translation of documents', 'format preservation'), but does not enumerate the broader operation set (glossaries, status monitoring, single-document translation), matching the 1-2-concrete-actions anchor rather than the several-actions anchor.	3 / 5
Completeness	Explicitly answers both what ('batch translation of documents with format preservation') and when ('Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale') with concrete trigger phrases, mirroring the anchor-5 example pattern; the when-clause is specific rather than merely present, so 4 does not fit.	5 / 5
Trigger Term Quality	'translating', 'Word, PDF, Excel, PowerPoint', 'document formats', 'at scale' are natural terms users would say, giving good keyword coverage; file extensions (.docx, .pdf) and common synonyms ('localize') are missing, so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	'Azure AI Document Translation', 'batch', 'format preservation' carve a mostly distinct niche with minor overlap risk against plain text-translation SDK skills; it lacks the fully distinct trigger phrasing of the anchor-5 example.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/azure-ai-translation-document-py/SKILL.md
Commit: 7b534bc

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