CtrlK
BlogDocsLog inGet started
Tessl Logo

visa-doc-translate

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

49

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

The canonical home for this skill is tdg-personal/visa-doc-translate

SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

The content delivers a clear, sequenced workflow with concrete commands, but it lacks executable PDF-generation code, validation checkpoints, and any progressive-disclosure split, with some redundant restatement across sections.

Suggestions

Provide an executable Python template (PIL + reportlab) for the bilingual PDF step instead of describing it in prose, so the guidance is copy-paste ready.

Add explicit validation checkpoints: verify OCR output is non-empty/plausible, confirm the PDF was written, and retry the next OCR method or rotation angle on failure before proceeding.

Consolidate the 'Output Example' and 'Important Guidelines' sections into 'Instructions' to remove redundant restatement, and consider moving OCR-method setup details into a references/ file to shorten the main body.

DimensionReasoningScore

Conciseness

The body is mostly actionable instruction, but the 'Output Example' and 'Important Guidelines' sections restate steps already covered in 'Instructions' (no-confirmation, rotation, OCR fallback, numeric accuracy), adding redundant tokens.

2 / 3

Actionability

Concrete commands are given (`sips -s format png`, `pip install easyocr/pillow/reportlab`) and OCR imports are shown, but the PDF-generation step only describes a script ('Create a Python script using PIL and reportlab') without an executable template or copy-paste code.

2 / 3

Workflow Clarity

A clear six-step sequence exists with an OCR-method fallback chain, but there are no validation/verification checkpoints (no OCR-output sanity check, no PDF-creation success check, no error-recovery loop) for an automated batch-style pipeline, capping this at 2.

2 / 3

Progressive Disclosure

The skill is a single ~118-line file with no bundle references; sections are well-organized, but it exceeds the 50-line simple-skill threshold and keeps OCR-method details and examples inline that could be split into reference files.

2 / 3

Total

8

/

12

Passed

Description

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 is specific and occupies a clear, low-conflict niche, but it omits any 'Use when...' trigger guidance and only partially enumerates the skill's concrete actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs visa application documents (deposit certificates, employment letters, IDs) translated into English as a bilingual PDF.'

Expand the action list to reflect the full workflow (OCR extraction, image rotation/normalization, bilingual PDF generation) so the description is comprehensive.

Include natural trigger variations users actually say, such as 'certified translation', 'visa translation', or 'translate certificate for visa'.

DimensionReasoningScore

Specificity

Names the domain ('visa application documents (images)') and two concrete actions ('Translate... to English' and 'create a bilingual PDF with original and translation'), but is not comprehensive — OCR, rotation, and formatting work are absent.

2 / 3

Completeness

It clearly answers what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

'visa application documents', 'translation', and 'bilingual PDF' are natural terms a user might say, but common variations like 'certified translation', 'visa translation', or 'translate certificate' are missing.

2 / 3

Distinctiveness Conflict Risk

The visa-document-to-bilingual-PDF niche is specific and unlikely to trigger for unrelated skills; it does not overlap meaningfully with general translation or PDF skills.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.