- Home
- Skills
- Translation & Localization
- Chrome Extension i18n: Add Keys to Every Locale at Once
Chrome Extension i18n: Add Keys to Every Locale at Once
Add, change or remove a string in every `_locales/*/messages.json` of your Chrome extension in one command, and lint all locales for missing keys and mismatched placeholders.
Free
Works with the AI Agents you already use
Chrome Extension i18n: Add Keys to Every Locale at Once
Example session with this skill installed
Add a new message 'settingsTitle' after 'headerTitle' for English and German. English is 'Extension Settings', German is 'Erweiterungseinstellungen'. Description is 'The title of the settings page'.
- Read your context and instructions
- Compiled the chrome extension i18n
I have added the settingsTitle key to both the English and German locale files. I placed it immediately after headerTitle to keep the settings-related strings grouped together.
Translation Update
# Executing the atomic update across locales
node scripts/add-message.mjs settingsTitle --after headerTitle \
--en "Extension Settings" \
--de "Erweiterungseinstellungen" \
--description "The title of the settings page"
# Verification output
# [OK] Found 2 locales: en, de
# [OK] All locales stay consistent.
# [OK] Key 'settingsTitle' added successfully.
The _locales/en/messages.json and _locales/de/messages.json files have been updated. The formatting of the existing entries remains unchanged.
Next steps
- Run
chrome.i18n.getMessage('settingsTitle')in your settings page script to verify the text renders correctly. - Check the git diff to confirm the key order matches your expectations.
- If you plan to support more languages, run the check command again to identify any missing translations for this new key.
Connects securely to your tools. The creator never sees your data.
About this skill
A missing key in one locale, a dash in a key name or a placeholder declared in English only: these are the classic ways to ship a broken Chrome extension. This skill keeps every locale in sync.
What you get
- A zero-dependency Node script (18+) that adds a key after a neighbour, changes it or removes it in all locales at once, and leaves the rest of each file byte for byte untouched, so your diffs stay tiny.
- A
--checklint: same keys everywhere, valid key names, same placeholders in every locale, undeclared$NAME$references. - Auto-detects your
_localesfolder and your languages. - Writing rules for short UI strings (length, tone, formal vs informal, which texts need a native review).
- Works with any build setup (WXT, Vite, CRXJS, Plasmo, plain).
Example prompts
- "Add a new string 'Sort tabs A to Z' to all locales"
- "Check that my locales are consistent"
- "Remove the unused key panelReadOnly"
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Translation & Localization.
Requires Node 18+. Does not sync with Chrome Web Store dashboard listings. Keys must follow ^[A-Za-z0-9_]+$ format.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 17 days ago
- Free with an Agensi account