New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Adding Translation Key

by vexl-it in vexl-it/vexl

How to add or change a user-facing string in the Vexl app and translate it into all shipped locales.

GPL-3.0Auto-check passedWriting & Content

Install Adding Translation Key

skills CLI
$ npx skills add vexl-it/vexl --skill adding-translation-key -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vexl-it/vexl adding-translation-key --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vexl-it/vexl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-translation-key .claude/skills/adding-translation-key && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
adding-translation-key
GitHub stars
125
Token cost
~632 tokens
SKILL.md length
297 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
GPL-3.0

At a glance

How to add or change a user-facing string in the Vexl app and translate it into all shipped locales.

  • Works in 4 steps: Write the English copy in… → Run pnpm generate in… → Translate. Spawn one translator subagent… → …
  • Modifying user-facing strings in apps/mobile (any text passed to t()
  • SKILL.md covers Steps and Rules
  • Calls pnpm

What it does

Adding Translation Key is an agent skill from vexl-it/vexl. How to add or change a user-facing string in the Vexl app and translate it into all shipped locales. Use whenever adding or modifying user-facing strings in apps/mobile (any text passed to t(), Typography content, notification copy, etc.).

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering Translation. It works with pnpm. The licence is GPL-3.0.

When your agent uses it

  • Modifying user-facing strings in apps/mobile (any text passed to t()
  • Typography content
  • Notification copy

Example prompts

  • “/adding-translation-key”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Write the English copy in packages/localization/locales/en/.json.
  2. Run pnpm generate in packages/localization and commit the regenerated src/translations.ts together with the JSON — that makes the key…
  3. Translate. Spawn one translator subagent covering the new/changed keys across all shipped locales — model, prompt contents, and translator…
  4. Verify. Run pnpm check:translations in packages/localization; done means no error names one of your keys.

What it can do on your machine

Read from SKILL.md and the folder at commit 4f76966. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Adding Translation Key loads about 632 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 297 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~632

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vexl-it/vexl at commit 4f76966, republished under its GPL-3.0 licence (© vexl-it). 297 words, ~632 tokens.

Download SKILL.mdSave it as .claude/skills/adding-translation-key/SKILL.md (or your agent's skills folder).
name
adding-translation-key
description
How to add or change a user-facing string in the Vexl app and translate it into all shipped locales. Use whenever adding or modifying user-facing strings in apps/mobile (any text passed to t(), Typography content, notification copy, etc.).

Adding or changing a translation key

Translations live in packages/localization/locales/<locale>/<group>.json — flat JSON with literal dotted keys ("offerForm.next": "Next"), i18next {{variable}} interpolation. English is the source of truth for meaning, and agents write every shipped locale themselves: a PR that adds or changes copy carries its own translations, and CI blocks it otherwise.

Steps

  1. Write the English copy in packages/localization/locales/en/<group>.json.
    • New copy must follow the Vexl voice — docs/brand-narrative/ (start with voice-and-personality.md and terminology-and-glossary.md).
    • Reuse an existing key if the exact string already exists for the same meaning (search locales/en/ first).
    • Pick the file matching the feature area (offers.json, chat.json, settings.json, …); the key's first dot-segment should fit the file's existing key families. Only create a new group file for a genuinely new feature area, with no hyphens in the name. Place the key next to related keys, not at the end of the file.
  2. Run pnpm generate in packages/localization and commit the regenerated src/translations.ts together with the JSON — that makes the key available and type-checked at t() call sites.
  3. Translate. Spawn one translator subagent covering the new/changed keys across all shipped locales — model, prompt contents, and translator rules are in docs/translating.md. A changed English value counts exactly like a new key: the existing translations are now stale, re-translate them.
  4. Verify. Run pnpm check:translations in packages/localization; done means no error names one of your keys.

Rules

  • For countable strings, en gets key_one + key_other (never a bare key) with {count: n} at the call site; the translator subagent owes each locale its full CLDR plural set (docs/translating.md).
  • src/translations.ts and src/extraTranslations.ts are generated — only pnpm generate writes them.
  • The legal document groups (privacyPolicy, termsOfUse, childSafetyAndSexAbusePrevention) are exempt from agent translation. If you change one, say so in your summary — translating legal text is a human decision per locale.

© vexl-it, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/adding-translation-key of vexl-it/vexl.

Open the folder on GitHubat commit 4f76966

Compare with similar skills

Adding Translation Key next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Adding Translation Key compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Adding Translation Key this skillvexl-it/vexl125—~632Automated safety check: PassGPL-3.0
Generate Translationspayloadcms/payload45k—~1.1kAutomated safety check: PassMIT
Plane UI Translationmakeplane/plane61k—~16kAutomated safety check: PassAGPL-3.0
Fanyiafc163/fanyi1.6k—~766Automated safety check: PassMIT
Aholo Viewer Docsmanycoretech/aholo-viewer1.1k—~341Automated safety check: PassMIT
Docs Websitekurotu/VRCQuestTools373—~1.3kAutomated safety check: PassMIT

Similar skills

  • Generate Translations

    payloadcms/payload

    A skill your agent uses when new translation keys are added to packages to generate new translations strings

    45k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed

  • Plane UI Translation

    makeplane/plane

    Sets the rules for translating and updating Plane's UI strings across locales: do-not-translate terms, plural forms, placeholders and AI translation review.

    61k GitHub stars~16k tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Fanyi

    afc163/fanyi

    用命令行工具 fanyi(别名 fy)做中英互译与查词,一次返回词典(iciba、youdao)和大模型三方结果。适用于单词、短语、习语谚语、单句短句的中英翻译,以及查释义、音标、例句、相关词。触发场景如"翻译一下 xxx"、"xxx 是什么意思"、"xxx 用英语怎么说"、"和谐 翻译成英文"——即使没说"用 fanyi"也应优先用本…

    1.6k GitHub stars~766 tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • Aholo Viewer Docs

    manycoretech/aholo-viewer

    Guides writing and maintaining Aholo Viewer documentation: README, AGENTS.md, architecture notes, bilingual manual pages and AI collaboration guides.

    1.1k GitHub stars~341 tokensUpdated today
    Writing & ContentAuto-check passed

  • Docs Website

    kurotu/VRCQuestTools

    Use this skill FIRST for any task whose output lives in the Website/ directory — the VRCQuestTools user manual / docs site (Docusaurus, bilingual en/ja).

    373 GitHub stars~1.3k tokensUpdated 8 days ago
    Writing & ContentAuto-check passed

  • Translation Diff Export

    Devolutions/UniGetUI

    Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.

    26k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed

More from vexl-it/vexl

  • Translation Feedback

    vexl-it/vexl

    Record translation-quality feedback as a durable rule in the brand narrative.

    125 GitHub stars~496 tokensUpdated yesterday
    Auto-check passed

  • Translation Audit

    vexl-it/vexl

    Translations audit — fill missing keys in every shipped locale, re-translate keys whose English changed, delete stale ones, flag suspicious values.

    125 GitHub stars~693 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Adding Translation Key

What does Adding Translation Key do?

How to add or change a user-facing string in the Vexl app and translate it into all shipped locales. Adding Translation Key is an agent skill from vexl-it/vexl. How to add or change a user-facing string in the Vexl app and translate it into all shipped locales.

When should I use Adding Translation Key?

Adding Translation Key fits situations like: modifying user-facing strings in apps/mobile (any text passed to t(); typography content; notification copy.

How do I install Adding Translation Key in Claude Code?

Run `npx skills add vexl-it/vexl --skill adding-translation-key -a claude-code`. Or copy the skill folder (.agents/skills/adding-translation-key in vexl-it/vexl) into .claude/skills/adding-translation-key in your project. Claude Code loads it when a task matches its description.

How do I install Adding Translation Key in Codex?

Run `npx skills add vexl-it/vexl --skill adding-translation-key -a codex`. Or copy the skill folder (.agents/skills/adding-translation-key in vexl-it/vexl) into .agents/skills/adding-translation-key in your project. Codex loads it when a task matches its description.

Can I use Adding Translation Key in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vexl-it/vexl --skill adding-translation-key -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-translation-key, .gemini/skills/adding-translation-key, .github/skills/adding-translation-key and .opencode/skills/adding-translation-key in your project.

What does Adding Translation Key need to run?

Going by SKILL.md and its folder, Adding Translation Key needs the command-line tools its instructions call (pnpm).

Does Adding Translation Key access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Adding Translation Key safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Adding Translation Key use?

Adding Translation Key is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Adding Translation Key use?

About 632 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Adding Translation Key?

Skills that share tags, products or a category with Adding Translation Key: Generate Translations (payloadcms/payload, 45k stars), Plane UI Translation (makeplane/plane, 61k stars), Fanyi (afc163/fanyi, 1.6k stars) and Aholo Viewer Docs (manycoretech/aholo-viewer, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Adding Translation Key?

vexl-it (a GitHub organization) maintains it in vexl-it/vexl, which has 125 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.

Source: vexl-it/vexl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.