visa-doc-translate

Translate visa application documents (images) to English and create a bilingual PDF with original and translation. Use when visa application document images must be translated to English as a bilingual PDF.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/visa-doc-translate/SKILL.md

Quality

Content

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

The body gives a clear, mostly actionable six-step pipeline with concrete commands, but suffers from redundant sections, a missing executable PDF-generation script, and an absence of validation checkpoints in an automated batch workflow. It also keeps everything inline rather than splitting detailed reference material into bundle files.

Suggestions

Add validation checkpoints to the workflow (e.g., verify OCR text is non-empty, confirm rotation looks correct, confirm the PDF was written) so workflow_clarity can exceed the batch-operation cap of 3.

Provide a concrete, copy-paste-ready Python script for the PDF generation step rather than describing Page 1/Page 2 in prose.

Remove the redundant 'Important Guidelines' and 'Output Example' restatements, and move detailed OCR install instructions into a reference file to improve conciseness and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but contains redundant restatement: the 'Important Guidelines' and 'Output Example' sections repeat earlier steps, and the opener 'You are helping translate visa application documents for visa applications' is padded; not a 4 because the duplication is more than minor.	3 / 5
Actionability	Provides executable commands (`sips -s format png`, pip installs) and code imports for most steps; falls short of 5 because the core deliverable — the PDF generation script — is described in prose ('Page 1: ... Page 2: ...') rather than as copy-paste-ready code.	4 / 5
Workflow Clarity	Steps 1-6 are clearly sequenced, but there are no validation checkpoints (no verify-OCR-succeeded, verify-rotation, or verify-PDF steps); per the rubric, a batch/auto operation without validation is capped at 3, and the skill additionally directs executing 'WITHOUT asking for confirmation'.	3 / 5
Progressive Disclosure	Has clear section headers, but at ~117 lines with no bundle files, content that could live in separate references (detailed OCR install instructions, supported-doc list) is inlined and no one-level-deep references are signaled; the over-50-lines simple-skill exception does not apply.	3 / 5
	Total	13 / 20 Passed

Description

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

The description is clear, specific, and well-structured with an explicit 'Use when' trigger, occupying a distinct niche. Its main weakness is limited action variety and a 'when' clause that duplicates the 'what' rather than broadening trigger coverage.

Suggestions

Add a couple more concrete actions (e.g., OCR extraction, EXIF-based image rotation) so specificity reaches the 'several specific actions' anchor.

Expand the 'Use when' clause with distinct trigger variations and file extensions (e.g., .jpg, .heic, .png) to lift trigger term quality and completeness.

Dimension	Reasoning	Score
Specificity	Names the domain (visa application document images) and two concrete actions ('Translate...to English' and 'create a bilingual PDF with original and translation'), but does not list several distinct actions, so it stops at the 1-2 concrete actions anchor rather than reaching 4.	3 / 5
Completeness	Explicitly answers both 'what' (translate to English, produce bilingual PDF) and 'when' ('Use when visa application document images must be translated...'); not a 5 because the 'when' clause merely restates the 'what' rather than offering distinct concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes natural user-facing phrases ('visa application documents', 'images', 'translated to English', 'bilingual PDF') that a user would plausibly say; falls short of 5 because it lacks synonyms and common file extensions like .jpg/.heic/.png.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (visa application document images -> bilingual English PDF) with distinctive triggers unlikely to collide with other skills, matching the clear-niche/minimal-conflict anchor.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: skills/visa-doc-translate/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.