i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill i18n-localizationOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 identifies a clear domain (internationalization/localization) and lists relevant capabilities, but lacks explicit trigger guidance for when Claude should select this skill. The trigger terms are decent but miss common abbreviations and user phrasings. Adding a 'Use when...' clause would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions i18n, l10n, translating an app, adding language support, or working with locale/translation files'
Include common abbreviations and file types users might mention: 'i18n', 'l10n', '.po files', '.xliff', 'gettext', 'react-intl'
Make actions more specific: instead of 'managing translations', specify 'extracting translatable strings, creating translation keys, updating locale JSON/YAML files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (internationalization/localization) and lists some actions (detecting hardcoded strings, managing translations), but the actions are somewhat general and not fully comprehensive - 'managing translations' and 'RTL support' are vague about what specific operations are performed. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'internationalization', 'localization', 'translations', 'locale files', 'RTL' but misses common variations users might say like 'i18n', 'l10n', 'multi-language', 'language support', 'translate app', or file extensions like '.po', '.json'. | 2 / 3 |
Distinctiveness Conflict Risk | The i18n/l10n domain is fairly specific and unlikely to conflict with most skills, but 'managing translations' and 'locale files' could potentially overlap with general file management or text processing skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized reference skill with good conciseness and useful code examples across multiple frameworks. The main weaknesses are incomplete actionability (script referenced but not provided) and lack of a clear implementation workflow. The content serves well as a quick reference but could better guide Claude through actual i18n implementation tasks.
Suggestions
Include the actual i18n_checker.py script content or provide a concrete example of its output and how to act on findings
Add a step-by-step workflow for adding i18n to an existing project, with validation checkpoints
Link to or include detailed guidance for complex topics mentioned (ICU message format, pluralization rules)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized with tables and code snippets. No unnecessary explanations of concepts Claude already knows - it jumps straight to actionable patterns and examples. | 3 / 3 |
Actionability | Provides concrete code examples for React, Next.js, Python, and CSS that are executable. However, the script reference at the end lacks the actual script content or usage examples, and some guidance remains at the checklist/best-practices level rather than fully executable. | 2 / 3 |
Workflow Clarity | The checklist provides a clear sequence for pre-shipping validation, but there's no explicit workflow for implementing i18n from scratch. Missing validation steps for detecting issues during development beyond mentioning a script that isn't shown. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and tables, but everything is in one file. The script reference at the end suggests external tooling exists but doesn't link to it or explain where to find it. Could benefit from linking to detailed guides for complex topics like ICU message format. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.