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…
Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo.
$ npx skills add Opentrons/opentrons --skill locize-sync -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Opentrons/opentrons locize-sync --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/locize-sync .claude/skills/locize-sync && rm -rf skills-srcUse ~/.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/
Install the "locize-sync" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-sync into .claude/skills/locize-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locize-sync", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-syncType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Opentrons/opentrons --skill locize-sync -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Opentrons/opentrons locize-sync --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/locize-sync .agents/skills/locize-sync && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "locize-sync" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-sync into .agents/skills/locize-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locize-sync", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Opentrons/opentrons --skill locize-sync -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Opentrons/opentrons locize-sync --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/locize-sync .cursor/skills/locize-sync && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "locize-sync" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-sync into .cursor/skills/locize-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locize-sync", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Opentrons/opentrons.git --path .cursor/skills/locize-sync--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Opentrons/opentrons --skill locize-sync -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Opentrons/opentrons locize-sync --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/locize-sync .gemini/skills/locize-sync && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "locize-sync" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-sync into .gemini/skills/locize-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locize-sync", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Opentrons/opentrons locize-syncInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Opentrons/opentrons --skill locize-sync -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/locize-sync .github/skills/locize-sync && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "locize-sync" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-sync into .github/skills/locize-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locize-sync", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Opentrons/opentrons --skill locize-sync -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Opentrons/opentrons locize-sync --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Opentrons/opentrons.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/locize-sync .opencode/skills/locize-sync && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "locize-sync" agent skill from https://github.com/Opentrons/opentrons/tree/edge/.cursor/skills/locize-sync into .opencode/skills/locize-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "locize-sync", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
locize-syncLocize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo.
Locize Sync is an agent skill from Opentrons/opentrons. Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo. Use when working with locizesync.py, localization files in app/src/assets/localization/ or components/src/assets/localization/, or syncing translations.
Its SKILL.md is about 730 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 Frontend & Design, covering Internationalization, Translation and Monorepo tooling. The repository describes itself as: Software for writing protocols and running them on the Opentrons Flex and Opentrons OT-2. The licence is Apache-2.0.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit adb4970. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
uvuvxmakeFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comlocize.appFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
LOCIZE_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Locize Sync loads about 728 tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 259 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
and `LOCIZE_PROJECT_ID` env vars (local `.env` or GitHub Actions secrets)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.
The full file from Opentrons/opentrons at commit adb4970, republished under its Apache-2.0 licence (© Opentrons). 259 words, ~728 tokens.
.claude/skills/locize-sync/SKILL.md (or your agent's skills folder).The Locize synchronization system manages internationalization (i18n) for the Opentrons monorepo. A unified Python script syncs localization files between the codebase and Locize cloud service.
Dry-Run Mode: All commands support --dry-run to preview actions without making changes.
Sync Script (scripts/locize_sync.py) — Python script executed via uv run, two actions:
push-local: Upload local English and Chinese translations to Locizedownload-remote: Download English and Chinese translations from LocizeLocalization Files
app/src/assets/localization/ — main application translationscomponents/src/assets/localization/ — shared component translationsen) is the source of truth; Chinese (zh) is downloaded from Locize. Chinese (zh) files may be invisible to agents because of the repo's ignore rules.components/ into app/ before syncing, then unconsolidates backAuthentication — LOCIZE_API_KEY and LOCIZE_PROJECT_ID env vars (local .env or GitHub Actions secrets)
uv run scripts/locize_sync.py push-localPushes English translations from repo to Locize. The script consolidates components/ JSON into app/, runs locize-cli sync, then unconsolidates and formats with make format-js.
When to use: After updating local English/Chinese strings, before handing to translators, to resolve drift.
uv run scripts/locize_sync.py download-remoteDownloads English and Chinese translations from Locize, overwriting local files. Consolidates, downloads, unconsolidates, and formats.
When to use: After translators finish work, prior to release, to align with remote content.
uv run scripts/locize_sync.py push-local --dry-run
uv run scripts/locize_sync.py download-remote --dry-runPerforms consolidation/unconsolidation to validate workspace, displays exact commands, but makes no remote changes.
uvx ruff check --fix scripts/locize_sync.py && uvx ruff format scripts/locize_sync.pyStore credentials in repository secrets: LOCIZE_API_KEY, LOCIZE_PROJECT_ID.
scripts/locize_sync.py© Opentrons, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .cursor/skills/locize-sync of Opentrons/opentrons.
Open the folder on GitHubat commit adb4970
Locize Sync 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Locize Sync this skillOpentrons/opentrons | 523 | — | ~728 | Automated safety check: Notes | Apache-2.0 | |
| Readme I18nY80/bmm | 344 | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| I18n Lang FilesMes-Open/OpenMes | 153 | — | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Docs I18n TranslateComfy-Org/docs | 299 | — | ~3.2k | Automated safety check: Notes | GPL-3.0 | |
| Chatbox i18n Translatorchatboxai/chatbox | 42k | — | ~508 | Automated safety check: Pass | GPL-3.0 | |
| Internationalization Workflow with i18niOfficeAI/AionUi | 33k | 1 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 |
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…
Mes-Open/OpenMes
Editing or merging backend/lang/en.json and pl.json. An agent skill from Mes-Open/OpenMes.
Comfy-Org/docs
Translate ComfyUI Mintlify docs from English MDX to ja/zh/ko using translate-i18n.ts.
chatboxai/chatbox
Translates new or changed i18n keys from a Chatbox Pro diff, staged changes or a commit range, writing the locale JSON files directly with a built-in glossary.
iOfficeAI/AionUi
Standards for keeping all user-facing text translatable: read the i18n config first, use namespaced keys, reuse shared strings and follow the key naming rules.
moeru-ai/airi
Review pending AIRI translations on Crowdin in a batch, then sync them into the repository.
Opentrons/opentrons
Conventions for the opentrons-ai-client React/TypeScript frontend — project structure, API integration, state management (Jotai), feature flags, types, and testing.
Opentrons/opentrons
Conventions for the opentrons-ai-server FastAPI service — project structure, uv dependency management, settings, testing, Docker, and deployment.
Opentrons/opentrons
Conventions for the analyses snapshot testing framework in analyses-snapshot-testing/.
Opentrons/opentrons
CSS Modules conventions, Stylelint rules, design tokens (spacing, colors, typography, border-radius), and patterns for the Opentrons monorepo.
Opentrons/opentrons
Authoring and styling guidelines for the Opentrons /docs MkDocs project.
Opentrons/opentrons
E2E testing conventions for Protocol Designer and Labware Library using Playwright + pytest in e2e-testing/.
Categories
Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo. Locize Sync is an agent skill from Opentrons/opentrons. Locize i18n synchronization workflow for pushing and downloading translations in the Opentrons monorepo.
Locize Sync fits situations like: working with locizesync.py; localization files in app/src/assets/localization/; components/src/assets/localization/; syncing translations.
Run `npx skills add Opentrons/opentrons --skill locize-sync -a claude-code`. Or copy the skill folder (.cursor/skills/locize-sync in Opentrons/opentrons) into .claude/skills/locize-sync in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Opentrons/opentrons --skill locize-sync -a codex`. Or copy the skill folder (.cursor/skills/locize-sync in Opentrons/opentrons) into .agents/skills/locize-sync in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Opentrons/opentrons --skill locize-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/locize-sync, .gemini/skills/locize-sync, .github/skills/locize-sync and .opencode/skills/locize-sync in your project.
Going by SKILL.md and its folder, Locize Sync needs the command-line tools its instructions call (uv, uvx and make) and credentials named LOCIZE_API_KEY. Our summary lists: Python 3; A credential in LOCIZE_API_KEY.
SKILL.md names 2 domains. As links in the text: github.com and locize.app. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Locize Sync is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 728 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Locize Sync: Readme I18n (Y80/bmm, 344 stars), I18n Lang Files (Mes-Open/OpenMes, 153 stars), Docs I18n Translate (Comfy-Org/docs, 299 stars) and Chatbox i18n Translator (chatboxai/chatbox, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Opentrons (a GitHub organization) maintains it in Opentrons/opentrons, which has 523 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.
Source: Opentrons/opentrons on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.