I18n

Skill helderberto/agent-skills/skills/i18n

Audit internationalization coverage and find hardcoded strings. Use when user asks to "check i18n", "/i18n", "find hardcoded strings", "check translations", or wants to verify translation coverage. Don't use for backend string extraction, non-frontend code, or projects without an i18n library.From its SKILL.md

Install

npx -y skills add helderberto/agent-skills --skill i18n

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

i18n Audit

Detection

Read package.json for i18n library:

react-i18next / i18next
next-intl
vue-i18n
react-intl (FormatJS)

Read locale files to understand key structure (e.g. src/locales/en.json).

Workflow

Detect i18n library and locale file locations
Search JSX/TSX/Vue files for hardcoded user-facing strings (see patterns.md):
- String literals in JSX: <p>Hello world</p>
- String props: placeholder="Search...", label="Submit"
- aria-label="Close menu"
Compare locale files — find missing keys between locales
Report findings

Output format

Hardcoded strings (file:line):

src/components/Header.tsx:12  "Welcome back"  → suggest key: header.welcomeBack
src/components/Form.tsx:34    placeholder="Search..."  → suggest key: form.searchPlaceholder

Missing translations (key present in base locale but absent in others):

Key: dashboard.emptyState  missing in: pt-BR, es
Key: errors.networkTimeout  missing in: pt-BR

Rules

Only flag user-visible strings (skip internal IDs, CSS classes, URLs, enum values)
Suggest translation key names in camelCase matching project convention
Never auto-modify locale files — report only

Error Handling

If no i18n library detected → report project may not use i18n; still list any hardcoded strings found
If no locale files found → skip missing-key comparison; only report hardcoded strings
If locale files are not JSON (e.g. .po, .yaml) → read them anyway and adapt key comparison logic

What ships with it: 1 file

1013 B alongside SKILL.md

references/

patterns.md1013 B

Gives 0 of the 12 instructions most quality gates skills give in 402 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Said here and by no other author read

Detect i18n library in package.json
Read locale files to understand key structure
Search frontend files for hardcoded user-facing strings
Compare locale files for missing keys
Suggest camelCase translation keys

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.