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

LobeHub Internationalization

by lobehub in lobehub/lobehub

Rules for adding and editing LobeHub's user-facing strings with react-i18next: flat dot-notation keys, the default locale folder, namespaces and when to run bun run i18n.

Custom licenceAuto-check passedFrontend & Design

Install LobeHub Internationalization

skills CLI
$ npx skills add lobehub/lobehub --skill i18n -a claude-code

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

GitHub CLI
$ gh skill install lobehub/lobehub i18n --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/lobehub/lobehub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/i18n .claude/skills/i18n && 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
i18n
GitHub stars
83k
Token cost
~569 tokens
SKILL.md length
153 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
Custom licence

At a glance

Rules for adding and editing LobeHub's user-facing strings with react-i18next: flat dot-notation keys, the default locale folder, namespaces and when to run bun run i18n.

  • Works in 5 steps: Add keys to… → Export new namespace in… → For dev preview: manually translate… → …
  • Adding a new user-facing string to the app
  • SKILL.md covers Key Naming Convention, Workflow, Usage and Common Namespaces
  • Calls bun; needs OPENAI_API_KEY

What it does

The skill sets the internationalization conventions for the LobeHub app, which uses react-i18next with English (en-US) as the default language. Only the files in packages/locales/src/default should be edited, and generated locale JSON is left alone apart from hand-written en-US and zh-CN previews. Keys are flat with dot notation following a feature, context and action or status pattern, parameters use double-brace syntax, and a key must not collide with a longer key that shares its prefix.

The workflow adds keys to a namespace file, exports any new namespace from the default index, hand-translates the zh-CN and en-US preview JSON for development, and leaves every other locale to the daily auto-i18n workflow, which opens a translation PR. Running bun run i18n manually is slow and needs an OPENAI_API_KEY, so it is only for when a branch needs the translations right away. Common namespaces include common, chat and setting.

When your agent uses it

  • Adding a new user-facing string to the app
  • Creating a locale namespace and exporting it
  • Deciding whether to run the manual translation script or wait for the daily job

Example prompts

  • “Add the strings for the new cloud banner with a credit parameter.”
  • “Create a new locale namespace for the memory feature and export it from the default index.”
  • “Two of my keys conflict because one is a prefix of the other. Rename them.”

Requirements

  • Bun, and an OPENAI_API_KEY only for the manual translation run

Workflow steps

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

  1. Add keys to packages/locales/src/default/{namespace}.ts
  2. Export new namespace in packages/locales/src/default/index.ts
  3. For dev preview: manually translate locales/zh-CN/{namespace}.json and locales/en-US/{namespace}.json
  4. Leave all other locales to .github/workflows/auto-i18n.yml, which runs daily and opens an automated translation PR
  5. Run bun run i18n manually only when the branch needs those translations immediately; it is slow and requires OPENAI_API_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 35d442e. 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:

    • bun

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

  • Network

    No URLs in SKILL.md.

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY

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

Context cost

LobeHub Internationalization loads about 569 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 153 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 153 words (~569 tokens).

“Flat keys with dot notation (not nested objects):”

— opening of SKILL.md by lobehub, Custom licence
name
i18n
user-invocable
false

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .agents/skills/i18n of lobehub/lobehub.

Open the folder on GitHubat commit 35d442e

Compare with similar skills

LobeHub Internationalization 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.

LobeHub Internationalization compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LobeHub Internationalization this skilllobehub/lobehub83k—~569Automated safety check: PassCustom licence
Frontend I18nlangflow-ai/langflow155k—~1kAutomated safety check: PassMIT
Readme I18nY80/bmm3442 repos~1.9kAutomated safety check: PassMIT
Frontend DevelopmentOpenHands/OpenHands90k—~324Automated safety check: PassMIT
Lingui Best PracticesB0und/WikiSpeedrun1332 repos~4.2kAutomated safety check: PassMIT
I18next Localizationi18next/i18next-cli242—~1.6kAutomated safety check: PassMIT

Similar skills

  • Frontend I18n

    langflow-ai/langflow

    Add, change, or review user-facing text in the Langflow frontend using the i18n system (i18next / react-i18next).

    155k GitHub stars~1k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Readme I18n

    Y80/bmm

    A skill your agent uses when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized…

    344 GitHub starsUsed in 2 repos~1.9k tokens
    Frontend & DesignAuto-check passed

  • Frontend Development

    OpenHands/OpenHands

    This skill should be used when the user asks to "add UI copy", "add a translation", "optimize the frontend bundle", "change onboarding", "change conversation UI", "add a query key", "change MSW…

    90k GitHub stars~324 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Lingui Best Practices

    B0und/WikiSpeedrun

    Implement internationalization with Lingui in React and JavaScript applications.

    133 GitHub starsUsed in 2 repos~4.2k tokens
    Frontend & DesignAuto-check passed

  • I18next Localization

    i18next/i18next-cli

    Takes an app from hardcoded strings to a localized, continuously translated one with i18next (Locize optional): stack detection, config, wrapping strings in t(), key extraction, Locize sync, and AI…

    242 GitHub stars~1.6k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Jta

    ckanner/jta

    Translate JSON i18n files to multiple languages with AI-powered quality optimization.

    133 GitHub stars~2.4k tokensUpdated 11 mo ago
    Frontend & DesignAuto-check: notes

More from lobehub/lobehub

All 50 skills in this repo

  • LobeHub Interactive Prototype

    lobehub/lobehub

    Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Acceptance Evidence for Deliveries

    lobehub/lobehub

    Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.

    83k GitHub stars~9.7k tokensUpdated today
    Auto-check passed

  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • LobeHub Alint Rule Set Maintenance

    lobehub/lobehub

    Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.

    83k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • LobeHub Builtin Tool Authoring

    lobehub/lobehub

    Guides building LobeHub builtin agent tools, from the manifest and execution runtime to executors, chat UI renders and registry wiring.

    83k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • LobeHub Data Fetching Layers

    lobehub/lobehub

    Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.

    83k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about LobeHub Internationalization

What does LobeHub Internationalization do?

Rules for adding and editing LobeHub's user-facing strings with react-i18next: flat dot-notation keys, the default locale folder, namespaces and when to run bun run i18n. The skill sets the internationalization conventions for the LobeHub app, which uses react-i18next with English (en-US) as the default language. Only the files in packages/locales/src/default should be edited, and generated locale JSON is left alone apart from hand-written en-US and zh-CN previews.

When should I use LobeHub Internationalization?

LobeHub Internationalization fits situations like: adding a new user-facing string to the app; creating a locale namespace and exporting it; deciding whether to run the manual translation script or wait for the daily job.

How do I install LobeHub Internationalization in Claude Code?

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

How do I install LobeHub Internationalization in Codex?

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

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

What does LobeHub Internationalization need to run?

Going by SKILL.md and its folder, LobeHub Internationalization needs the command-line tools its instructions call (bun) and credentials named OPENAI_API_KEY. Our summary lists: Bun, and an OPENAI_API_KEY only for the manual translation run.

Does LobeHub Internationalization 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 LobeHub Internationalization 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 LobeHub Internationalization use?

LobeHub Internationalization has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does LobeHub Internationalization use?

About 569 tokens (SKILL.md is roughly 2.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 LobeHub Internationalization?

Skills that share tags, products or a category with LobeHub Internationalization: Frontend I18n (langflow-ai/langflow, 155k stars), Readme I18n (Y80/bmm, 344 stars), Frontend Development (OpenHands/OpenHands, 90k stars) and Lingui Best Practices (B0und/WikiSpeedrun, 133 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LobeHub Internationalization?

lobehub (a GitHub organization) maintains it in lobehub/lobehub, which has 83,074 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.

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