CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visa-doc-translate

Translate visa application documents (images) to English and create a bilingual PDF with original and translation

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is visa-doc-translate in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 lays out a clear, well-sequenced workflow with useful fallback guidance and concrete setup commands, but the core OCR and PDF-generation steps stop short of executable code, and two sections largely duplicate the main instructions. Removing redundancy and supplying (or referencing) a working OCR/PDF script would lift it substantially.

Suggestions

Remove the redundant "Important Guidelines" and "Output Example" sections, whose points are already covered by the numbered Instructions, and drop the marketing-style closing line about destination countries.

Provide an executable OCR helper (or a scripts/ file) instead of bare `import Vision` snippets, and a runnable PDF-generation script or template rather than a description of what it should create.

Add a final validation step, e.g. verify the generated PDF opens, contains both pages, and the numbers/dates in the translation match the OCR output before reporting the file location.

DimensionReasoningScore

Conciseness

The core instructions are tight, but the "Important Guidelines" section repeats the Instructions section (no-confirmation, OCR fallback, number accuracy), "Output Example" re-narrates the entire workflow, and the closing "Perfect for visa applications to Australia, USA, Canada, UK..." line is padding.

3 / 5

Actionability

Install commands and the HEIC conversion command are concrete, but the two most critical steps lack executable code: OCR shows only `import Vision` import snippets with no invocation, and PDF generation is described ("Create a Python script using PIL and reportlab libraries") rather than provided.

3 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with specifics (EXIF orientation 6 -> rotate 90 degrees counterclockwise, OCR fallback order, test 180 degrees if upside down), but there is no final verification that the generated PDF is correct.

4 / 5

Progressive Disclosure

A single well-sectioned file with no bundle files and appropriately inline install details; at ~113 lines it exceeds the under-50-lines exception, and the OCR setup and PDF layout detail could live in a reference file, keeping it at good rather than excellent structure.

4 / 5

Total

14

/

20

Passed

Description

61%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 concise, concrete, and clearly scoped to a distinct niche, with a good set of natural trigger terms. Its main weaknesses are the complete absence of a "when to use" clause and unstated core capabilities like OCR of document images.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user provides a photo or scan of a visa application document (bank statement, employment certificate, ID card, etc.) and needs a certified English translation."

Mention the OCR capability explicitly (e.g. "extracts text from document images via OCR") so the image-to-text step is not left implicit.

Include one or two file extensions users actually have (.jpg, .png, .heic) to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

States two concrete actions in third person ("Translate visa application documents (images) to English and create a bilingual PDF with original and translation") but does not explicitly mention OCR/text extraction, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (translate visa document images to English, produce a bilingual PDF), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains natural terms users would say ("visa application documents", "translate", "bilingual", "PDF", "images"), but misses common document-type synonyms (bank statement, deposit certificate) and file extensions (.jpg, .heic, .png).

4 / 5

Distinctiveness Conflict Risk

"visa application documents" carves out a clear niche with distinct triggers, with only minor overlap risk against generic translation or PDF-manipulation skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

valeriibeck-star/claude-skills

Path

skills/visa-doc-translate/SKILL.md

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.