CtrlK
BlogDocsLog inGet started
Tessl Logo

i18n-expert

This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.

87

1.00x
Quality

81%

Does it follow best practices?

Impact

98%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

This is a solid intermediate-quality skill with a well-structured workflow and clear validation loop, but it falls short on actionability by lacking executable code examples for key setup steps (config files, provider wiring, language switcher). The content is moderately concise but includes some sections that explain concepts Claude already knows or that add marginal value. The referenced audit script is not provided in the bundle, which weakens both actionability and progressive disclosure.

Suggestions

Add a concrete, executable code example for i18n setup (e.g., a complete react-i18next config file and provider wiring snippet) to improve actionability.

Include the referenced `scripts/i18n_audit.py` in the bundle or provide its implementation inline, since the workflow depends on it.

Trim or remove sections like 'Core Capabilities' and 'Performance Notes' that describe concepts Claude already knows, to improve conciseness.

Move 'Architecture Guidance', 'Failure Modes', and 'Validation Checklist' into a separate reference file to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some sections that over-explain or list things Claude already knows (e.g., 'Core Capabilities' listing generic concepts, 'Architecture Guidance' covering basics like 'use Intl helpers for date formatting'). The 'Scope Inputs' section is useful but could be tighter. Some sections like 'Failure Modes' and 'Performance Notes' add marginal value.

2 / 3

Actionability

The skill provides concrete commands (ripgrep patterns, json validation, audit script invocation) and specific patterns like `t('namespace.key')` and `_one/_other` plural keys, which is good. However, it lacks executable code examples for the setup steps (no actual i18n config file example, no provider wiring code, no language switcher snippet). The audit script is referenced but not provided in the bundle, reducing actionability.

2 / 3

Workflow Clarity

The 8-step workflow is clearly sequenced with an explicit audit-fix-validate loop. Step 8 explicitly requires re-running the audit until issues are zero, and JSON validation is included. The workflow has clear checkpoints (step 3 treats parity gaps as blockers, step 8 validates before completion). The feedback loop pattern is well-defined for this type of batch string replacement operation.

3 / 3

Progressive Disclosure

The skill references `scripts/i18n_audit.py` but no bundle files are provided, so the reference is unverifiable. The content is somewhat monolithic—sections like 'Architecture Guidance', 'Failure Modes', 'Performance Notes', and 'Validation Checklist' could be split into a reference file. However, the section headers provide reasonable navigation within the single file.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines its scope, lists concrete actions, and provides explicit trigger conditions. It covers both the 'what' and 'when' effectively, includes natural trigger terms users would use, and occupies a distinct niche that minimizes conflict risk with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: installing/configuring i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, validating key parity, pluralization, and formatting.

3 / 3

Completeness

Clearly answers both 'what' (installing/configuring i18n, replacing hard-coded strings, ensuring locale coverage, mapping error codes, validating key parity) and 'when' ('when setting up, auditing, or enforcing internationalization/localization in UI codebases') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'internationalization', 'localization', 'i18n', 'i18next', 'hard-coded strings', 'JSON locales', 'React/TS', 'en-US', 'zh-CN', 'pluralization'. Good coverage of both full terms and abbreviations.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused on i18n/localization in React/TS codebases with i18next. The combination of specific framework references, locale pairs, and concrete tasks like key parity validation makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
daymade/claude-code-skills
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.