CtrlK
BlogDocsLog inGet started
Tessl Logo

translator

Translate content across languages while preserving brand voice and cultural nuance.

58

Quality

66%

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 ./apps/desktop/electron/default-skills/translator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is a tight, well-structured instruction-only skill: it gives concrete, example-backed localization guidance and a clear sequenced workflow with an explicit output format. It is held out of the top band only by minor concision trim, the absence of a worked before/after example, and a lack of an explicit final verification step.

Suggestions

Tighten the opening framing ('Translate like a localization professional, not a dictionary...') to one line to reclaim tokens without losing the core principle.

Add a short worked before/after example (e.g., an English idiom and its localized equivalent) to make the localization guidance immediately copy-pasteable.

Add an explicit final QA checkpoint in 'How to work', e.g. 'Re-read the translation in the target language to confirm it reads naturally and fits any length limits before shipping.'

DimensionReasoningScore

Conciseness

Sections are lean and purposeful (idioms, formality, units, platform limits, how-to-work, output) with only mild framing prose ('Translate like a localization professional, not a dictionary...') that could be trimmed, fitting 'efficient; minor instances of over-explanation.'

4 / 5

Actionability

Concrete directives with specific examples ('{name}', '%s', HTML tags; es-MX vs. es-ES; tú/usted, T-V, honorifics) give mostly executable guidance; a worked before/after example would push it to a 5.

4 / 5

Workflow Clarity

The 'How to work' steps give a clear, unambiguous four-step sequence; because translation is non-destructive the missing-validation cap does not apply, though no explicit final QA/read-through checkpoint keeps it just below 5.

4 / 5

Progressive Disclosure

At ~35 lines with well-organized section headers and no need for external references, this meets the simple-skill exception where progressive disclosure scores 5 with just well-organized sections; no bundle files exist to verify.

5 / 5

Total

17

/

20

Passed

Description

53%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, third-person, and on-niche but generic: it states what the skill does without listing several concrete actions or any explicit trigger guidance. Adding a 'Use when...' clause and concrete localization actions (localize idioms, convert units/currency, adapt UI strings) would lift it toward the top anchors.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to translate or localize content between languages, adapt marketing copy/UI strings/support docs for another locale, or preserve brand voice across languages.'

Add concrete localization actions to the description, e.g. 'Translate and localize content — adapt idioms, cultural references, formality, units/dates/currency, and UI string lengths — across 50+ languages.'

Include the natural synonym 'localize/localization' so the description matches the vocabulary users actually say.

DimensionReasoningScore

Specificity

Names the translation domain plus two concrete preservation goals ('brand voice', 'cultural nuance') but offers only a single action ('Translate content'), so it lands at the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the multi-action level 4.

3 / 5

Completeness

It gives a clear 'what' (translate across languages preserving voice/nuance) but no 'Use when...' trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'Translate content across languages' supplies the core natural terms ('translate', 'languages') but omits the major synonym 'localize/localization' and any language names, matching 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The cross-language translation niche is clearly distinct with minimal overlap risk; it is 'mostly distinct' rather than a fully fleshed-out 5 because trigger phrases are thin.

4 / 5

Total

13

/

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
holaboss-ai/holaOS
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.