CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

i18n-localization

Planeja e implementa internacionalizacao e localizacao. Trigger em: "i18n", "internacionalizacao", "localizacao", "l10n", "traducao", "multi-idioma", "outro idioma", "RTL", "arabe", "hebraico", "direita para esquerda", "pseudolocale", "texto quebrou traduzido", "formato de data", "formato de moeda", "plural", "locale", "timezone", "fuso horario", "expansao de texto".

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

This is a strong, working skill: the audit protocol is immediately executable, the catalog maps each defect to a concrete fix, and the workflow includes genuine re-validation and scope-leak detection after changes. The only notable flaws are mild redundancy (the pipeline-integration section duplicates the handoff section) and inlining nearly 300 lines that a companion guide file could absorb.

DimensionReasoningScore

Conciseness

The body is dense and information-bearing — grep regexes, fix-mapping tables, and a tight problem/cause/fix catalog — with essentially no explanation of concepts Claude already knows. It is not 5 because the "Integracao com Pipeline" section repeats the "Handoff" section's skill 02/22/56 mappings almost verbatim, and "Quando Usar/Nao Usar" overlaps the frontmatter trigger list.

4 / 5

Actionability

Copy-paste grep commands per defect class and concrete fixes throughout: `t("home.greeting", { nome, count: n })`, `Intl.PluralRules`, `Intl.Collator`, the physical-to-logical CSS mapping table, and Tailwind `ms-*`/`me-*` substitutions. Minor gaps keep it below 5: pseudolocale generation has no runnable command (explicitly justified as technique-over-tool) and `t()` is left stack-generic.

4 / 5

Workflow Clarity

The five-phase protocol has explicit validation checkpoints — pseudolocale and `dir="rtl"` tests run before fixing, and Phase 5 re-runs both with a feedback loop that flags scope leaks ("Se algo que passava antes do fix quebrou agora, o fix vazou escopo — revisar"). Checklist and evidence-of-completion sections close the loop, matching the top anchor (sequence + validation + feedback loops + checklist).

5 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled one-level reference that names exactly what it defers ("tabelas de expansao por idioma, exemplos de formatter por plataforma e receitas de teste" in `docs/skill-guides/i18n-localization.md` "apenas quando necessario"). Not 5 because at ~290 lines the 9-item catalog, anti-patterns, and checklist are all inlined and part of that bulk could live in the referenced guide; not 3 because the reference is clearly signaled and the inline material is core working content.

4 / 5

Total

17

/

20

Passed

Description

76%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's trigger list is a standout — exhaustive, natural, with synonyms and real failure scenarios — and the niche is unmistakable. The weakness is the capability statement itself: two generic verbs ("planeja e implementa") that never tell the reader what concretely gets done, capping both specificity and completeness. Adding the skill's concrete deliverables to the one-line capability statement would lift it to top-tier.

Suggestions

Replace the generic "Planeja e implementa" opening with the skill's concrete actions, e.g. "Audita strings hardcoded, concatenacao e largura fixa, externaliza strings com interpolacao nomeada, aplica formatters de data/moeda/plural por locale e prepara suporte RTL" — this alone would move specificity from 2 to 4-5.

State the deliverables in the description so the 'what' matches the body's "Saidas Esperadas": audit report, externalized strings, pseudolocale/RTL test evidence — lifting completeness from 4 to 5.

Keep the trigger list unchanged; it is the strongest part of the description and needs no additions.

DimensionReasoningScore

Specificity

"Planeja e implementa internacionalizacao e localizacao" names the domain but relies solely on the generic verbs "planeja" and "implementa", matching the 'Processes PDF files' anchor; no concrete capability (string auditing, externalization, RTL prep, locale formatting) is stated in the description itself. It is not 3 because that anchor requires 1-2 concrete actions, and these verbs convey no specific operation.

2 / 5

Completeness

Both parts are explicit: what ("Planeja e implementa internacionalizacao e localizacao") and when ("Trigger em: ..." followed by concrete phrases). It is not 5 because the 'what' is minimal — the description omits the skill's actual deliverables (audit report, externalized strings, pseudolocale/RTL testing) that the body clearly defines, leaving the capability statement thinner than the trigger statement.

4 / 5

Trigger Term Quality

The trigger list is comprehensive with abbreviations, synonyms, and failure phrasings users naturally say: "i18n", "internacionalizacao", "l10n", "traducao", "RTL", "arabe", "hebraico", "pseudolocale", "texto quebrou traduzido", "formato de data", "formato de moeda", "plural", "timezone", "fuso horario", "expansao de texto". It clearly matches the top anchor including synonyms and paired technical/colloquial variants.

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear i18n-architecture niche, and triggers like "pseudolocale", "RTL", "expansao de texto", and "formato de moeda" would not plausibly fire a copywriting or responsive-layout skill. It is not 4 because the overlap risk is genuinely minimal rather than a minor concern.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/58-i18n-localization/SKILL.md

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.