CtrlK
BlogDocsLog inGet started
Tessl Logo

localization-toolkit

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.

75

Quality

92%

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

The canonical home for this skill is i18n-expert in daymade/claude-code-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

Highly actionable with a clear validated workflow and clean progressive disclosure via a single real helper script. The main weakness is mild cross-section redundancy (RTL, pluralization) that adds tokens without new information.

Suggestions

Consolidate the RTL and pluralization guidance into one authoritative section to remove their recurrence across Core Capabilities, Workflow, Architecture Guidance, Failure Modes, and the Checklist.

Consider trimming or merging the short 'Performance Notes' and 'Failure Modes' sections, whose points partly overlap Guardrails and Architecture Guidance.

The 'Core Capabilities' bullet list largely restates the Workflow steps; either cut it or repurpose it as a one-line scope summary to save tokens.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but RTL and pluralization recur across Core Capabilities, Workflow, Architecture Guidance, Failure Modes, and the Validation Checklist, adding redundant tokens that could be tightened.

2 / 3

Actionability

Provides fully executable guidance — concrete commands (i18n_audit.py invocation, rg regexes, `python -m json.tool`), specific API patterns (`t('namespace.key')`, `t('key', { count })`), and named libraries (react-i18next, next-intl, vue-i18n).

3 / 3

Workflow Clarity

The 8-step Audit→Fix→Validate workflow has an explicit feedback loop ('Re-run the audit until missing/parity issues are zero') plus a validation checklist, satisfying the checkpoint requirement for batch/destructive operations.

3 / 3

Progressive Disclosure

A well-organized overview file backed by one real, clearly-signaled one-level-deep helper script (scripts/i18n_audit.py) referenced in both the workflow and the Resources section; content is appropriately kept inline rather than needlessly split.

3 / 3

Total

11

/

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.

A strong description: concrete, action-oriented, with an explicit use-when trigger and natural trigger terms in third person. It clearly distinguishes the skill's niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'installing/configuring the i18n framework, replacing hard-coded strings... mapping error codes to localized messages, and validating key parity, pluralization, and formatting' — matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what (the enumerated i18n actions) and when ('This skill should be used when setting up, auditing, or enforcing...'), in third person.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('internationalization/localization', 'i18n', 'i18next', 'locales', 'pluralization') with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear i18n/localization niche with distinct triggers ('UI codebases', 'JSON locales', 'key parity') unlikely to conflict with unrelated 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.