CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

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.

A well-structured, actionable internationalization planning skill with a clear layered framework, a sequenced workflow with validation, and a properly separated checklist reference. Its only meaningful weakness is conciseness: several sections restate general knowledge Claude already has.

Suggestions

Trim general-knowledge asides in the Locale-aware UX section that Claude already knows — e.g. 'Most of the world is metric; the US is imperial', 'Arabic, Hebrew, Persian, Urdu', and 'Avoid hand gestures in product imagery' — keeping only the actionable rule.

Drop parenthetical tutoring of familiar concepts, such as '(avoids retranslating reused phrases)' for translation memory and 'E.164 international format universally', stating the rule without the explanation.

In Failure patterns, cut restated consequences Claude can infer ('Frustrating.', 'Doesn't adapt.', 'Inconsistent.') and keep just the anti-pattern plus its fix, tightening the section.

DimensionReasoningScore

Conciseness

The body is mostly lean and actionable, but it pads several points with general knowledge Claude already has, e.g. 'Most of the world is metric; the US is imperial', 'Arabic, Hebrew, Persian, Urdu', 'Avoid hand gestures in product imagery', and the parenthetical '(avoids retranslating reused phrases)' for translation memory.

2 / 3

Actionability

Concrete executable guidance throughout: a copy-paste hreflang HTML block, specific CSS ('margin-inline-start instead of margin-left'), a URL-pattern comparison table, a 10-step workflow, and an explicit output-format template. Per the scoring note, an instruction-only planning skill is not penalized for lacking runnable code when the guidance is this specific.

3 / 3

Workflow Clarity

A clearly sequenced 10-step workflow with an explicit validation checkpoint (Step 8 Test, a per-locale checklist) and ongoing monitoring (Step 9), plus a dedicated checklist reference for complex processes. Validation steps are present, so the destructive/batch cap does not apply.

3 / 3

Progressive Disclosure

The body is a well-organized overview (When to use, 5 layers, Workflow, Failure patterns, Output format) that points to one real, well-signaled one-level-deep reference, references/locale-checklist.md (verified to exist), with content appropriately split rather than inlined.

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.

An exemplary description: specific actions, broad and natural trigger terms, explicit what-and-when guidance, and a distinct niche with no conflict risk. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: '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'. Not a 2, which only names a domain and some actions without this breadth.

3 / 3

Completeness

Explicitly answers both what ('Plan and run a multi-language or multi-region site') and when via an explicit 'Use this skill when...' clause plus 'Triggers on...' and 'Also triggers when international audiences underperform or translations are stale.' The 'Use when' clause is present, so completeness is not capped at 2.

3 / 3

Trigger Term Quality

Strong, natural coverage in 'Triggers on internationalization, i18n, localization, l10n, hreflang, multi-language, translation workflow, RTL, locale, ccTLD, subfolder vs subdomain, language switcher' — terms users would actually say, including common shorthand variations.

3 / 3

Distinctiveness Conflict Risk

A clear niche (multi-language/multi-region sites) with distinct, domain-specific triggers (hreflang, RTL, ccTLD, i18n) unlikely to fire for unrelated skills, and correct third-person voice with no first/second-person phrasing.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-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.