internationalization
Plan and run a multi-language or multi-region site. Use this skill when adding new locales, choosing URL structure for languages (subfolders vs subdomains vs ccTLDs), implementing hreflang, planning translation workflow, handling currency and date formats, designing for RTL languages, or auditing a stalled internationalization rollout. Triggers on internationalization, i18n, localization, l10n, hreflang, multi-language, translation workflow, RTL, locale, ccTLD, subfolder vs subdomain, language switcher. Also triggers when international audiences underperform or translations are stale.
63
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/internationalization/SKILL.mdQuality
Discovery
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 an excellent skill description that clearly defines its scope around internationalization/localization, lists concrete actions, provides explicit trigger guidance with both a 'Use this skill when' clause and a dedicated trigger term list, and occupies a distinct niche. The description is comprehensive without being padded, and uses appropriate third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: adding new locales, choosing URL structure, implementing hreflang, planning translation workflow, handling currency/date formats, designing for RTL languages, and auditing internationalization rollouts. | 3 / 3 |
Completeness | Clearly answers both 'what' (plan and run multi-language/multi-region sites with specific sub-tasks listed) and 'when' (explicit 'Use this skill when...' clause plus a dedicated 'Triggers on' section with comprehensive trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both full words and abbreviations (internationalization/i18n, localization/l10n), technical terms (hreflang, ccTLD), and natural user phrases ('international audiences underperform', 'translations are stale', 'subfolder vs subdomain'). | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a very clear niche around internationalization and localization with highly specific triggers like hreflang, ccTLD, RTL, and i18n that are unlikely to conflict with other skills such as general SEO or web development. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive internationalization guide with good structural organization and useful decision frameworks (URL structure table, content patterns A/B/C, failure patterns). However, it leans toward being a reference document rather than an actionable skill—it's verbose in places, lacks executable examples beyond one HTML snippet, and misses explicit validation checkpoints in its workflow. The content would benefit from being more concise and splitting detailed reference material into separate files.
Suggestions
Add explicit validation checkpoints in the workflow, e.g., 'Validate hreflang with a tool like hreflang.org before proceeding' and 'If reciprocal links are missing, fix before launching the locale.'
Provide more executable examples: a complete hreflang sitemap XML snippet, a CSS logical properties example for RTL, and a sample locale configuration object or template.
Move the lengthy failure patterns section and the detailed Layer 5 (locale-aware UX) content into separate reference files to reduce the main skill's token footprint.
Condense explanatory content Claude already knows (e.g., what RTL languages are, basic date format differences across locales) into brief reminders or remove entirely.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content Claude already knows (e.g., explaining what RTL languages are, basic date format differences, what E.164 is). The failure patterns section, while useful, is verbose and could be condensed into a table. Several sections explain concepts rather than just instructing. | 2 / 3 |
Actionability | The skill provides structured guidance with decision tables and clear patterns, but lacks executable code examples beyond a single HTML snippet. The workflow steps are directional rather than concrete—e.g., 'Set up hreflang and canonicals' without providing a template or script. The hreflang HTML example is good but most other guidance is descriptive rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | The 10-step workflow is clearly sequenced and logically ordered, and Step 8 includes a testing checklist. However, there are no explicit validation checkpoints or feedback loops within the workflow—e.g., no 'validate hreflang before proceeding to next step' or 'if reciprocal links fail, fix before launch.' For a multi-step process involving SEO-critical tags, missing validation gates cap this at 2. | 2 / 3 |
Progressive Disclosure | The skill references one external file (references/locale-checklist.md) which is appropriate, but the main body is quite long (~300+ lines) with substantial inline detail that could be split into reference files (e.g., failure patterns, locale-aware UX details, translation workflow details). The structure within the file is good with clear headers, but the content-to-reference ratio is heavy on inline. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- rampstackco/claude-skills
- Commit
8e70d03
- 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.