i18n-localization

Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/i18n-localization/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The body is well-organized with executable examples and a real referenced script, but it carries some unnecessary concept explanation and lacks an explicit multi-step workflow with validation feedback loops for the batch checker.

Suggestions

Replace the "Core Concepts" glossary and project-type table with a brief pointer, since Claude already knows these concepts, to tighten conciseness.

Turn the checker into an explicit workflow (run it, review high-severity findings, fix, re-run) with a validation checkpoint so workflow_clarity can exceed 3.

Add a short concrete example for ICU message format and Intl date/number formatting to close the actionability gap toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly compact tables and code, but the "Core Concepts" glossary (i18n/L10n/Locale/RTL) and the "When to Use i18n" project-type table explain concepts Claude already knows, matching the anchor for mostly-efficient content with some unnecessary explanation.	3 / 5
Actionability	It provides executable React/Next.js/Python/CSS snippets plus a runnable checker script, but ICU pluralization and Intl date/number formatting are named without concrete examples, leaving minor gaps that keep it below 5.	4 / 5
Workflow Clarity	There is no sequenced procedure; a flat shipping checklist and a referenced checker script stand in for a workflow, and the batch checker is not tied into an explicit validate-fix-re-run feedback loop, which the rubric caps at 3 for batch operations.	3 / 5
Progressive Disclosure	Numbered sections give good structure and the single bundle reference (scripts/i18n_checker.py, a real file) is clearly signaled in a command table, matching the anchor for good structure with minor organization gaps; it is not 5 because there is only one external reference and no deeper topic files.	4 / 5
	Total	14 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 is specific and well-targeted to the i18n/L10n niche with concrete actions and natural trigger terms, but it lacks an explicit "Use when..." clause, capping its completeness.

Suggestions

Add an explicit trigger clause such as "Use when internationalizing an app, managing translations, or adding RTL support" to lift completeness above 3.

Include common synonyms and file extensions (i18n, L10n, .po, .json) to broaden natural trigger-term coverage toward a 5.

Lead with concrete verbs for every listed item so the specificity reaches the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	The description names the domain plus several concrete actions ("Detecting hardcoded strings, managing translations") alongside topic nouns ("locale files, RTL support"), matching the anchor that lists several specific actions with minor gaps; it stops short of 5 because not every item is a concrete verb.	4 / 5
Completeness	It clearly answers "what" the skill does but provides no "Use when..." trigger clause in the description field, which per the rubric guidelines caps completeness at 3 even though the what is well stated.	3 / 5
Trigger Term Quality	It includes natural terms users would say ("Internationalization and localization", "hardcoded strings", "translations", "locale", "RTL") but omits common synonyms and file extensions like i18n, L10n, .po, or .json, so it falls just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	The triggers (translations, RTL support, locale files, hardcoded strings) carve out a clear niche with minimal overlap against other skills, matching the anchor for a distinct niche with low conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/i18n-localization/SKILL.md
Commit: 211561c

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.