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

Readme I18n

by Y80 in 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…

MITAuto-check passedFrontend & Design

Install Readme I18n

skills CLI
$ npx skills add Y80/bmm --skill readme-i18n -a claude-code

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

GitHub CLI
$ gh skill install Y80/bmm readme-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/Y80/bmm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/readme-i18n .claude/skills/readme-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
readme-i18n
GitHub stars
344
Used in
2 other repos
Token cost
~1.9k tokens
SKILL.md length
1,042 words
Files
3 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 8 steps: Establish the source README and languages → Audit the Markdown structure before… → Translate only the prose layer → …
  • The user wants to translate a repository README
  • SKILL.md covers Inputs, Defaults And Decision Rules, Workflow and Output, plus 3 more sections
  • Calls make; needs OPENAI_API_KEY

What it does

Readme I18n is an agent skill from Y80/bmm. Use 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 README variants in a GitHub-style repository.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/language-selector-reference.md` and `references/preservation-checklist.md`).

It sits in Frontend & Design, covering Technical documentation, Internationalization and Translation. It works with GitHub, Next.js and React. The repository describes itself as: 🤵 BMM - Your Personal Bookmark Manager | 你的专属书签管家. The licence is MIT.

When your agent uses it

  • The user wants to translate a repository README
  • Make a repo multilingual
  • Add a language switcher
  • Internationalize the README

Example prompts

  • “/readme-i18n”

Requirements

  • A credential in OPENAI_API_KEY

Workflow steps

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

  1. Establish the source README and languages
  2. Audit the Markdown structure before translating
  3. Translate only the prose layer
  4. Preserve structure while writing the localized README
  5. Rewrite localized anchors and anchor-dependent links
  6. Write sibling files using the repo's naming pattern
  7. Insert or update the language selector
  8. Final verification

What it can do on your machine

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

    • make

    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

Readme I18n loads about 1.9k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 1,042 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.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 Y80/bmm at commit f8d4bbe, republished under its MIT licence (© Y80). 1,042 words, ~1,933 tokens.

Download SKILL.mdSave it as .claude/skills/readme-i18n/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
readme-i18n
description
Use 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 README variants in a GitHub-style repository.

Localize a repository README.md without breaking the repo mechanics around it.

The default job is translate + wire-up:

  • read the source-of-truth README
  • create localized sibling files such as README.zh.md
  • preserve GitHub-flavored Markdown structure and repo-specific tokens
  • add or update a shared language selector near the top of every variant

This skill is for multilingual README workflows, not general website/app i18n.

Inputs

Expect these inputs when available:

  • source README path, default README.md
  • source language, default inferred or English
  • one or more target languages
  • optional glossary or do-not-translate list
  • optional filename override if the repo already uses a different multilingual naming pattern

If target languages are not named, inspect existing translated files, selectors, filenames, issues, or prior repo conventions. If that still leaves the target languages unclear, ask once. Do not invent target languages.

Defaults And Decision Rules

  • Treat the root README.md as the source-of-truth unless the user explicitly says otherwise.
  • If the source language is ambiguous, ask once. Otherwise assume English.
  • Keep section order aligned with the source README. Only make a small heading wording adjustment when needed to produce a valid localized anchor.
  • Output localized siblings with README.<bcp47-tag>.md naming unless the repo already has a different established pattern that should be preserved.
  • Update an existing language selector in place. Do not duplicate it.
  • Translate only human-language content.
  • Preserve project names, package names, commands, CLI flags, option names, environment variables, URLs, file paths, inline code, code fences, HTML attributes, and badge/image URLs.
  • Badge alt text or visible labels may be translated only when the change does not require changing the badge URL, query params, or image source.
  • If a glossary or do-not-translate list is provided, apply it consistently across every target language.

Workflow

1. Establish the source README and languages
  • Confirm the source README path. Default to README.md.
  • Identify the source language from the file contents and repo context.
  • Determine target languages from the request or existing repo pattern.
  • Note any glossary terms, product names, or phrases that must stay untranslated.
2. Audit the Markdown structure before translating

Read the source README once as structure, not prose. Open references/preservation-checklist.md and inventory the elements most likely to break:

  • headings and heading levels
  • badge rows, shields URLs, and image links
  • tables and alignment rows
  • raw HTML blocks and inline HTML
  • GitHub alerts or admonitions such as > [!NOTE]
  • code fences, inline code, commands, and config snippets
  • intra-document anchors such as (#installation)
  • relative links to files, docs, screenshots, or other README variants

If the README already has localized siblings, inspect them too before choosing filenames or selector style.

3. Translate only the prose layer

Translate:

  • paragraph text
  • list item prose
  • table cell prose
  • visible text inside HTML blocks
  • image alt text when safe
  • selector labels and other human-facing labels

Do not translate:

  • fenced code blocks
  • inline code spans
  • shell commands
  • flags such as --help
  • env vars such as OPENAI_API_KEY
  • URLs
  • file paths
  • repo/package/project identifiers
  • badge and image URLs

When in doubt, preserve the literal token and translate the surrounding sentence instead.

4. Preserve structure while writing the localized README
  • Keep the same heading hierarchy and section order as the source.
  • Keep the same number of code fences unless the user explicitly asks to rewrite examples.
  • Preserve table shape, list nesting, HTML wrappers, and Markdown comments.
  • Preserve relative links unless a link intentionally needs to point at a localized sibling README.

When a translated heading changes, GitHub will generate a different heading ID. After translating headings:

  • rewrite every same-file (#...) link so it matches the localized heading slug in that file
  • preserve custom explicit anchors such as <a id="..."> unless the file already uses localized explicit IDs
  • verify that every intra-document anchor target resolves to an existing heading or explicit anchor

Prefer a small heading wording adjustment over a broken anchor. The section order should still match the source README.

Show full SKILL.md (403 more words)Show less
6. Write sibling files using the repo's naming pattern

Default to sibling filenames like:

  • README.zh.md
  • README.es.md
  • README.fr.md

If the repo already uses a different multilingual naming pattern, keep using it consistently rather than forcing the default pattern.

7. Insert or update the language selector

Open references/language-selector-reference.md before editing selectors.

Placement:

  • keep the selector near the top of the file
  • if the README starts with a title, badges, hero image, or short intro block, place the selector immediately after that opening cluster

Behavior:

  • update an existing selector block in place if one already exists
  • if you add a new selector, use the canonical marker comments from the reference file so later runs can update it deterministically
  • emphasize the current language and link the other variants
  • keep selector order and labels consistent across every README variant
8. Final verification

Before finishing, verify:

  • localized filenames follow the chosen pattern
  • every README variant contains exactly one selector block
  • code fence counts are preserved
  • badge/image URLs and relative file links still point to the original targets unless intentionally localized
  • every (#...) link resolves inside its own file
  • the localized README still feels structurally identical to the source

Output

Produce:

  • one localized sibling README per target language
  • an updated selector block in every README variant
  • a brief note to the user covering created or updated files, any assumptions, and any terms intentionally left untranslated

Maintenance Note

Keep README.md as the canonical source unless the user says otherwise. When the source README changes later, update each localized sibling by diffing the changed prose, then re-check selectors, filenames, and anchor links instead of reformatting the whole file from scratch.

Example Prompts

Example 1

Translate this README into Chinese and add a language switcher. Keep badge URLs, code fences, and all commands exactly as they are.

Example 2

Make the repo multilingual. Add Spanish and Chinese README variants, keep the internal anchor links working, and wire the selector into every file.

Example 3

We already have README.zh.md. Add README.es.md and update the existing selector in place instead of adding a second one.

Common Mistakes

  • Translating fenced code blocks or inline code instead of only the prose around them
  • Duplicating the language selector instead of updating the existing block
  • Translating a heading but forgetting to rewrite same-file (#...) links
  • Changing badge URLs or image sources while trying to translate visible labels
  • Reordering sections in the localized README even though the source README is the authority

© Y80, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/readme-i18n of Y80/bmm.

  • SKILL.md
  • references/language-selector-reference.md
  • references/preservation-checklist.md

Open the folder on GitHubat commit f8d4bbe

Used in 2 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in Y80/bmm, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Readme I18n 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.

Readme I18n compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Readme I18n this skillY80/bmm3442 repos~1.9kAutomated safety check: PassMIT
Builder UI I18nChatbotXIO/ChatbotX885—~2.1kAutomated safety check: PassCustom licence
Frontend I18nlangflow-ai/langflow155k—~1kAutomated safety check: PassMIT
Lingui Best PracticesB0und/WikiSpeedrun1332 repos~4.2kAutomated safety check: PassMIT
I18next Localizationi18next/i18next-cli241—~1.6kAutomated safety check: PassMIT
Nextjs Nextra Starter Distillpdsuwwz/nextjs-nextra-starter318—~596Automated safety check: PassMIT

Similar skills

  • Builder UI I18n

    ChatbotXIO/ChatbotX

    Build or modify ChatbotX builder UI components, forms, tables, dialogs, shared UI usage, and translations.

    885 GitHub stars~2.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • 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

  • 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…

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

  • Nextjs Nextra Starter Distill

    pdsuwwz/nextjs-nextra-starter

    Distill and apply this repository's Next.js Nextra starter architecture, implemented features, extension points, and migration patterns.

    318 GitHub stars~596 tokensUpdated 23 days ago
    Frontend & DesignAuto-check passed

  • Add Language

    ZoneMinder/zmNinjaNg

    A skill your agent uses when adding a new interface language (locale) to the app, or when asked to translate the UI into another language.

    111 GitHub stars~1.1k tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

More from Y80/bmm

  • Bmm Bookmark Form

    Y80/bmm

    Guide for modifying BMM bookmark create/edit pages and related icon workflows.

    344 GitHub stars~683 tokensUpdated 4 mo ago
    Auto-check passed

  • Bmm Iconify Icons

    Y80/bmm

    Guide for updating Iconify icons and IconNames conventions in BMM.

    344 GitHub stars~810 tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Readme I18n

What does Readme I18n do?

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…. Readme I18n is an agent skill from Y80/bmm. Use 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 README variants in a GitHub-style repository.

When should I use Readme I18n?

Readme I18n fits situations like: the user wants to translate a repository README; make a repo multilingual; add a language switcher; internationalize the README.

How do I install Readme I18n in Claude Code?

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

How do I install Readme I18n in Codex?

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

Can I use Readme I18n 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 Y80/bmm --skill readme-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/readme-i18n, .gemini/skills/readme-i18n, .github/skills/readme-i18n and .opencode/skills/readme-i18n in your project.

What does Readme I18n need to run?

Going by SKILL.md and its folder, Readme I18n needs the command-line tools its instructions call (make) and credentials named OPENAI_API_KEY. Our summary lists: A credential in OPENAI_API_KEY.

Does Readme I18n 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 Readme I18n 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 Readme I18n use?

Readme I18n 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 Readme I18n use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Readme I18n?

Skills that share tags, products or a category with Readme I18n: Builder UI I18n (ChatbotXIO/ChatbotX, 885 stars), Frontend I18n (langflow-ai/langflow, 155k stars), Lingui Best Practices (B0und/WikiSpeedrun, 133 stars) and I18next Localization (i18next/i18next-cli, 241 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Readme I18n?

Y80 (a GitHub user) maintains it in Y80/bmm, which has 344 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on June 8, 2026.

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