Agent skill

Generate Translations

by payloadcms in payloadcms/payload

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

MITAuto-check passedWriting & Content

Install Generate Translations

skills CLI
$ npx skills add payloadcms/payload --skill generate-translations -a claude-code

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

GitHub CLI
$ gh skill install payloadcms/payload generate-translations --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/payloadcms/payload.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/generate-translations .claude/skills/generate-translations && 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
generate-translations
GitHub stars
45k
Token cost
~1.1k tokens
SKILL.md length
389 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 2 steps: Core Translations → Plugin Translations
  • New translation keys are added to packages to generate new translations strings
  • SKILL.md covers Table of Contents, 1. Core Translations, 2. Plugin Translations and Important Notes
  • Calls pnpm; needs OPENAI_KEY

What it does

Generate Translations is an agent skill from payloadcms/payload. Use when new translation keys are added to packages to generate new translations strings

Its SKILL.md is about 1.1k 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 Payload CMS and pnpm. The repository describes itself as: Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a… The licence is MIT.

When your agent uses it

  • New translation keys are added to packages to generate new translations strings
  • Tasks that involve Translation

Example prompts

  • “/generate-translations”

Requirements

  • A credential in OPENAI_KEY
  • Pre-approved tools (allowed-tools): Write, Bash(date:*), Bash(mkdir -p *)

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Core Translations
  2. Plugin Translations

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Write
    • Bash(date:*)
    • Bash(mkdir -p *)

    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 these keys or tokens, usually read from environment variables:

    • OPENAI_KEY

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

Context cost

Generate Translations loads about 1.1k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 389 words of instructions outside code blocks.

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

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 payloadcms/payload at commit 58fe765, republished under its MIT licence (© payloadcms). 389 words, ~1,077 tokens.

Download SKILL.mdSave it as .claude/skills/generate-translations/SKILL.md (or your agent's skills folder).
name
generate-translations
description
Use when new translation keys are added to packages to generate new translations strings
allowed-tools
Write, Bash(date:*), Bash(mkdir -p *)

Translation Generation Guide

Payload has two separate translation systems:

  1. Core Translations - for core Payload packages (packages/ui, packages/payload, packages/next)
  2. Plugin Translations - for plugins (packages/plugin-*)

Table of Contents


1. Core Translations

When to use: Adding translations to core Payload packages (packages/ui, packages/payload, packages/next)

Steps:
  1. Add the English translation to packages/translations/src/languages/en.ts

    • Add your new key/value to the appropriate section (e.g., authentication, general, fields, etc.)
    • Use nested objects for organization
    • Example:
      typescript
      export const enTranslations = {
        authentication: {
          // ... existing keys
          newFeature: 'New Feature Text',
        },
      }
  2. Add client key (if needed for client-side usage) to packages/translations/src/clientKeys.ts

    • Add the translation key path using colon notation
    • Example: 'authentication:newFeature'
    • Client keys are used for translations that need to be available in the browser
  3. Generate translations for all languages

    • Change directory: cd tools/scripts
    • Run: pnpm generateTranslations:core
    • This auto-translates your new English keys to all other supported languages

2. Plugin Translations

When to use: Adding translations to any plugin package (packages/plugin-*)

Steps:
  1. Verify plugin has translations folder

    • Check if packages/plugin-{name}/src/translations exists
    • If it doesn't exist, see "Scaffolding New Plugin Translations" below
  2. Add the English translation to the plugin's packages/plugin-{name}/src/translations/languages/en.ts

    • Plugin translations are namespaced under the plugin name
    • Example for plugin-multi-tenant:
      typescript
      export const enTranslations = {
        'plugin-multi-tenant': {
          'new-feature-label': 'New Feature',
        },
      }
  3. Generate translations for all languages

    • Change directory: cd tools/scripts
    • Run the plugin-specific script: pnpm generateTranslations:plugin-{name}
    • Examples:
      • pnpm generateTranslations:plugin-multi-tenant
      • pnpm generateTranslations:plugin-ecommerce
      • pnpm generateTranslations:plugin-import-export
Show full SKILL.md (159 more words)Show less
Scaffolding New Plugin Translations

If a plugin doesn't have a translations folder yet, ask the user if they want to scaffold one.

Structure to create:
packages/plugin-{name}/src/translations/
├── index.ts
├── types.ts
└── languages/
    ├── en.ts
    ├── es.ts
    └── ... (all other language files)
Files to create:
  1. types.ts - Define the plugin's translation types
  2. index.ts - Export all translations and re-export types
  3. languages/en.ts - English translations (the source for generation)
  4. languages/*.ts - Other language files (initially empty, will be generated)
Generation script to create:
  1. Create tools/scripts/src/generateTranslations/plugin-{name}.ts

    • Use plugin-multi-tenant.ts as a template
    • Update the import paths to point to the new plugin
    • Update the targetFolder path
  2. Add script to tools/scripts/package.json:

    json
    "generateTranslations:plugin-{name}": "node --no-deprecation --import @swc-node/register/esm-register src/generateTranslations/plugin-{name}.ts"

Important Notes

  • All translation generation requires OPENAI_KEY environment variable to be set
  • The generation scripts use OpenAI to translate from English to other languages
  • Always add translations to English first - it's the source of truth
  • Core translations: Client keys are only needed for translations used in the browser/admin UI
  • Plugin translations: Automatically namespaced under the plugin name to avoid conflicts

© payloadcms, MIT. 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/generate-translations of payloadcms/payload.

Open the folder on GitHubat commit 58fe765

Compare with similar skills

Generate Translations 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.

Generate Translations compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Generate Translations this skillpayloadcms/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
Adding Translation Keyvexl-it/vexl125—~632Automated safety check: PassGPL-3.0
Translation Auditvexl-it/vexl125—~693Automated safety check: PassGPL-3.0

Similar skills

  • 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 yesterday
    Writing & ContentAuto-check passed
  • How to add or change a user-facing string in the Vexl app and translate it into all shipped locales.

    125 GitHub stars~632 tokensUpdated yesterday
    Writing & ContentAuto-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
    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 9 days ago
    Writing & ContentAuto-check passed

More from payloadcms/payload

All 9 skills in this repo
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Payload

    payloadcms/payload

    A skill your agent uses when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API).

    45k GitHub starsUsed in 5 repos~6.2k tokens
    Auto-check passed
  • Audit Dependencies

    payloadcms/payload

    A skill your agent uses when fixing dependency vulnerabilities, running pnpm audit, or when the audit-dependencies CI check fails

    45k GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed
  • Triage CI Flake

    payloadcms/payload

    A skill your agent uses when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests

    45k GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • Ui4 Convert Tests

    payloadcms/payload

    A skill your agent uses when UI changes are complete and e2e tests need updating.

    45k GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • Payload Accessibility

    payloadcms/payload

    A skill your agent uses when changing or reviewing rendered Payload UI, interaction or focus behavior, semantic markup, accessibility tests, or WCAG/VPAT evidence.

    45k GitHub stars~808 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Generate Translations

What does Generate Translations do?

A skill your agent uses when new translation keys are added to packages to generate new translations strings. Generate Translations is an agent skill from payloadcms/payload.

When should I use Generate Translations?

Generate Translations fits situations like: new translation keys are added to packages to generate new translations strings; tasks that involve Translation.

How do I install Generate Translations in Claude Code?

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

How do I install Generate Translations in Codex?

Run `npx skills add payloadcms/payload --skill generate-translations -a codex`. Or copy the skill folder (.agents/skills/generate-translations in payloadcms/payload) into .agents/skills/generate-translations in your project. Codex loads it when a task matches its description.

Can I use Generate Translations 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 payloadcms/payload --skill generate-translations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-translations, .gemini/skills/generate-translations, .github/skills/generate-translations and .opencode/skills/generate-translations in your project.

What does Generate Translations need to run?

Going by SKILL.md and its folder, Generate Translations needs the command-line tools its instructions call (pnpm) and credentials named OPENAI_KEY. Our summary lists: A credential in OPENAI_KEY. Its frontmatter pre-approves these tools: Write, Bash(date:*), Bash(mkdir -p *).

Does Generate Translations 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 Generate Translations 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 Generate Translations use?

Generate Translations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Generate Translations use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Generate Translations?

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

Who maintains Generate Translations?

payloadcms (a GitHub organization) maintains it in payloadcms/payload, which has 45,161 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.

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