CtrlK
BlogDocsLog inGet started
Tessl Logo

i18n-context

Add gettext context for ambiguous user-facing strings and repair affected PO translations.

64

Quality

76%

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 ./.agents/skills/i18n-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exceptionally lean, executable workflow with concrete commands and validation steps organized into clear sections; its only gap is the validation step being a flat list rather than an explicit validate-fix-retry feedback loop.

DimensionReasoningScore

Conciseness

The body is lean with no padding or basic-concept explanation; every line is task-specific (exact rg commands, pgettext/translate_marker_context snippets, validation commands), assuming Claude's competence throughout.

5 / 5

Actionability

Copy-paste-ready rg/grep commands, exact pgettext/translate_marker_context/JSON ctxt snippets, and concrete validation commands (extract_json_strings.py, msgfmt, check_po_printf_format.py, lint-json.sh) cover the common cases.

5 / 5

Workflow Clarity

The workflow is clearly sequenced (find shared msgids, split at source, update PO, validate) with explicit validation steps and a destructive-change gate, but the validation block is a flat command list rather than an explicit validate-fix-retry feedback loop with pass/fail branches.

4 / 5

Progressive Disclosure

Well-organized single-file skill under 50 lines with clear sections (Hard requirements, Workflow, PR references); the simple-skill exception applies and no external file references are needed.

5 / 5

Total

19

/

20

Passed

Description

58%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 clearly states what the skill does within a well-defined i18n niche, but it lacks an explicit 'Use when...' trigger and natural-language keywords a user would say, which caps completeness and trigger-term quality.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when a single English msgid has multiple meanings that need different translations per locale.'

Include natural user-facing terms such as 'translation context', 'disambiguate strings', or '.po files' rather than only gettext/msgctxt jargon.

Consider listing one or two more concrete actions (e.g. update PO entries, run msgfmt) to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the i18n/gettext domain and two concrete actions ("add gettext context" and "repair affected PO translations"), which is more than 1-2 actions but slightly short of comprehensive coverage with no clear trigger/scope phrasing beyond the two verbs.

4 / 5

Completeness

A clear 'what' is present (add gettext context, repair PO translations) but there is no explicit 'Use when...' trigger clause; the missing explicit 'when' caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Uses domain terms (gettext, msgid context, PO translations) but omits the natural user phrasing like "translation context", "disambiguate strings", or locale/PO file extensions a user would actually say; mostly technical jargon.

3 / 5

Distinctiveness Conflict Risk

The gettext/pgettext/PO-translation niche is fairly specific and unlikely to collide with unrelated skills, though a generic 'translation' skill could still partially overlap, leaving minor conflict risk.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cataclysmbn/Cataclysm-BN
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.