Agent skill

Translate Strings

TRIGGER when user asks to externalize, internationalize, or translate user-facing strings.

Apache-2.0Auto-check passedFrontend & Design

Install Translate Strings

skills CLI

$ npx skills add microbus-io/fabric --skill translate-strings -a claude-code

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

GitHub CLI

$ gh skill install microbus-io/fabric translate-strings --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/microbus-io/fabric.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/microbus/translate-strings .claude/skills/translate-strings && 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/

Paste into Claude Code

Install the "translate-strings" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings into .claude/skills/translate-strings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "translate-strings", 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

$skill-installer install https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings

Type 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.

skills CLI

$ npx skills add microbus-io/fabric --skill translate-strings -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install microbus-io/fabric translate-strings --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/microbus/translate-strings .agents/skills/translate-strings && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "translate-strings" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings into .agents/skills/translate-strings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "translate-strings", 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.

skills CLI

$ npx skills add microbus-io/fabric --skill translate-strings -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install microbus-io/fabric translate-strings --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/microbus/translate-strings .cursor/skills/translate-strings && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "translate-strings" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings into .cursor/skills/translate-strings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "translate-strings", 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

$ gemini skills install https://github.com/microbus-io/fabric.git --path .claude/skills/microbus/translate-strings

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add microbus-io/fabric --skill translate-strings -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install microbus-io/fabric translate-strings --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/microbus/translate-strings .gemini/skills/translate-strings && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "translate-strings" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings into .gemini/skills/translate-strings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "translate-strings", 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.

GitHub CLI

$ gh skill install microbus-io/fabric translate-strings

Installs 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).

skills CLI

$ npx skills add microbus-io/fabric --skill translate-strings -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/microbus/translate-strings .github/skills/translate-strings && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "translate-strings" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings into .github/skills/translate-strings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "translate-strings", 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.

skills CLI

$ npx skills add microbus-io/fabric --skill translate-strings -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install microbus-io/fabric translate-strings --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microbus-io/fabric.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/microbus/translate-strings .opencode/skills/translate-strings && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "translate-strings" agent skill from https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/translate-strings into .opencode/skills/translate-strings/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "translate-strings", 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.

Facts

Skill name: translate-strings
GitHub stars: 172
Token cost: ~879 tokens
SKILL.md length: 260 words
Files: 1
Skills in repo: 32
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

TRIGGER when user asks to externalize, internationalize, or translate user-facing strings.

Works in 6 steps: Create String Bundle → Transfer Strings → Translate Strings for Requested Languages → …
User asks to externalize
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Internationalize

What it does

Translate Strings is an agent skill from microbus-io/fabric. TRIGGER when user asks to externalize, internationalize, or translate user-facing strings. Moves hardcoded display text into a text.yaml resource bundle for i18n support.

Its SKILL.md is about 880 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 and Microservices. The repository describes itself as: Microbus is the only fabric where every agentic workflow runs on a true microservice substrate - giving your workflows security, scale, observability, and prompt-driven authoring. The licence is Apache-2.0.

When your agent uses it

User asks to externalize
Internationalize
Translate user-facing strings

Example prompts

“/translate-strings”

Workflow steps

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

Create String Bundle
Transfer Strings
Translate Strings for Requested Languages
Update References in Go Files
Update References in Templates
Housekeeping

What it can do on your machine

Read from SKILL.md and the folder at commit fb98098. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are go, yaml and html).
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 no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Translate Strings loads about 879 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 260 words of instructions outside code blocks.

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

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 microbus-io/fabric at commit fb98098, republished under its Apache-2.0 licence (© microbus-io). 260 words, ~879 tokens.

Download SKILL.mdSave it as .claude/skills/translate-strings/SKILL.md (or your agent's skills folder).

name: translate-strings
description: TRIGGER when user asks to externalize, internationalize, or translate user-facing strings. Moves hardcoded display text into a text.yaml resource bundle for i18n support.

CRITICAL: Read and analyze this microservice before starting. Do NOT explore or analyze other microservices. The instructions in this skill are self-contained to this microservice.

Workflow

Copy this checklist and track your progress:

Externalizing and translating strings:
- [ ] Step 1: Create string bundle
- [ ] Step 2: Transfer strings
- [ ] Step 3: Translate strings for requested languages
- [ ] Step 4: Update references in Go files
- [ ] Step 5: Update references in templates
- [ ] Step 6: Housekeeping

Step 1: Create String Bundle

Create resources/text.yaml, if one does not already exist.

Step 2: Transfer Strings

Locate static strings in the microservice that are ultimately shown to the end user. These are likely to be in service.go or in HTML or text templates in the resources directory.

For each string, create an entry in resources/text.yaml that maps a unique key to its localized value on a per language basis. Use PascalCase for the string key (e.g. MyString) and ISO 639 language codes for each language (e.g. en-US).

yaml

HelloWorld:
  en: Hello World

Step 3: Translate Strings for Requested Languages

Update resources/text.yaml and add a localized value for each explicitly requested language. Use the ISO 639 language code under the key of each localization.

yaml

HelloWorld:
  en: Hello World
  en-AU: G'day World
  fr: Bonjour le Monde
  es: Hola Mundo

The en or en-US localizations are used by default when no other language matches the request's context. If neither localization is included, a default value should be provided instead.

yaml

HolaMundo:
  fr: Bonjour le Monde
  es: Hola Mundo
  default: Hola Mundo

Step 4: Update References in Go Files

Use svc.MustLoadResString to load strings in Go files such as service.go.

Before:

func (svc *Service) HelloWorld(w http.ResponseWriter, r *http.Request) (err error) {
	w.Write([]byte("Hello World"))
	return err
}

After:

func (svc *Service) HelloWorld(w http.ResponseWriter, r *http.Request) (err error) {
	ctx := r.Context()
	textHelloWorld := svc.MustLoadResString(ctx, "HelloWorld")
	w.Write([]byte(textHelloWorld))
	return err
}

Step 5: Update References in Templates

To use localized strings in HTML templates, load all strings with svc.MustLoadResStrings into a map, pass the map as part of the data to the template, and use the map in the template to obtain the string by key, instead of the static string.

Before:

func (svc *Service) HelloWorld(w http.ResponseWriter, r *http.Request) (err error) {
	data := struct{
		OtherData int
	}{
		OtherData: 5,
	}
	err = svc.WriteResTemplate(w, "mytemplate.html", data)
	if err != nil {
		return errors.Trace(err)
	}
	return nil
}

html

<b>Hello World</b>

After:

func (svc *Service) HelloWorld(w http.ResponseWriter, r *http.Request) (err error) {
	ctx := r.Context()
	data := struct{
		OtherData int
		Text map[string]string
	}{
		OtherData: 5,
		Text: svc.MustLoadResStrings(ctx),
	}
	err = svc.WriteResTemplate(w, "mytemplate.html", data)
	if err != nil {
		return errors.Trace(err)
	}
	return nil
}

html

<b>{{ .Text.HelloWorld }}</b>

Step 6: Housekeeping

Follow the housekeeping skill.

Files

Just SKILL.md in .claude/skills/microbus/translate-strings of microbus-io/fabric.

Open the folder on GitHubat commit fb98098

Compare with similar skills

Translate Strings 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.

Translate Strings compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Translate Strings this skillmicrobus-io/fabric	172	—	~879	Automated safety check: Pass	Apache-2.0	10 days ago
Declarative Agent Developermicrosoft/work-iq	1k	—	~3.2k	Automated safety check: Pass	Custom licence	yesterday
Sanity Best Practicesrobotostudio/turbo-start-sanity	182	—	~940	Automated safety check: Pass	MIT	2 days ago
Email Template Builderalirezarezvani/claude-skills	28k	1 repos	~3.8k	Automated safety check: Pass	MIT	1 mo ago
Add Servicelbedner/aegis-stack	143	—	~5.2k	Automated safety check: Pass	MIT	today
Update Project Docshoangsonww/Claude-Code-Agent-Monitor	1.1k	—	~2.6k	Automated safety check: Pass	MIT	yesterday

Similar skills

Declarative Agent Developer
microsoft/work-iq
Official
Create, build, deploy, and localize declarative agents for M365 Copilot and Teams.
1k GitHub stars~3.2k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Sanity Best Practices
robotostudio/turbo-start-sanity
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and…
182 GitHub stars~940 tokensUpdated 2 days ago
Frontend & DesignAuto-check passed
Email Template Builder
alirezarezvani/claude-skills
Build complete transactional email systems: React Email templates, provider integration (Resend, Postmark, SendGrid, AWS SES), preview server, i18n support, dark mode, spam optimization, analytics…
28k GitHub starsUsed in 1 repo~3.8k tokens
Frontend & DesignAuto-check passed
Add Service
lbedner/aegis-stack
A skill your agent uses when adding a new service (a business capability like auth, AI, blog, or finance) to the Aegis Stack framework itself.
143 GitHub stars~5.2k tokensUpdated today
Frontend & DesignAuto-check passed
Update Project Docs
hoangsonww/Claude-Code-Agent-Monitor
MANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to behavior, configuration, interfaces, events, schema, or features.
1.1k GitHub stars~2.6k tokensUpdated yesterday
Frontend & DesignAuto-check passed
Maui Localization
davidortinau/maui-skills
Guidance for localizing .NET MAUI apps: multi-language support via .resx resource files, culture resolution and runtime switching, RTL layout, platform language declarations (iOS/Mac Catalyst…
174 GitHub stars~1.2k tokensUpdated 3 mo ago
Frontend & DesignAuto-check passed

Questions about Translate Strings

What does Translate Strings do?

TRIGGER when user asks to externalize, internationalize, or translate user-facing strings. Translate Strings is an agent skill from microbus-io/fabric. TRIGGER when user asks to externalize, internationalize, or translate user-facing strings.

When should I use Translate Strings?

Translate Strings fits situations like: user asks to externalize; internationalize; translate user-facing strings.

How do I install Translate Strings in Claude Code?

Run `npx skills add microbus-io/fabric --skill translate-strings -a claude-code`. Or copy the skill folder (.claude/skills/microbus/translate-strings in microbus-io/fabric) into .claude/skills/translate-strings in your project. Claude Code loads it when a task matches its description.

How do I install Translate Strings in Codex?

Run `npx skills add microbus-io/fabric --skill translate-strings -a codex`. Or copy the skill folder (.claude/skills/microbus/translate-strings in microbus-io/fabric) into .agents/skills/translate-strings in your project. Codex loads it when a task matches its description.

Can I use Translate Strings 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 microbus-io/fabric --skill translate-strings -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/translate-strings, .gemini/skills/translate-strings, .github/skills/translate-strings and .opencode/skills/translate-strings in your project.

What does Translate Strings need to run?

SKILL.md names no scripts, command-line tools or credentials: Translate Strings is instructions for the agent only.

Does Translate Strings 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 Translate Strings 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 Translate Strings use?

Translate Strings 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.

How many tokens does Translate Strings use?

About 879 tokens (SKILL.md is roughly 3.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 Translate Strings?

Skills that share tags, products or a category with Translate Strings: Declarative Agent Developer (microsoft/work-iq, 1k stars), Sanity Best Practices (robotostudio/turbo-start-sanity, 182 stars), Email Template Builder (alirezarezvani/claude-skills, 28k stars) and Add Service (lbedner/aegis-stack, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Translate Strings?

microbus-io (a GitHub organization) maintains it in microbus-io/fabric, which has 172 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on September 28, 2026.

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

Translate Strings

Install Translate Strings

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Workflow

Step 1: Create String Bundle

Step 2: Transfer Strings

Step 3: Translate Strings for Requested Languages

Step 4: Update References in Go Files

Step 5: Update References in Templates

Step 6: Housekeeping

Files

Compare with similar skills

Similar skills

Declarative Agent Developer

Sanity Best Practices

Email Template Builder

Add Service

Update Project Docs

Maui Localization

More from microbus-io/fabric

Add Config

Add Function

Add Inbound Event

Add Metric

Add Outbound Event

Add Python Function

Questions about Translate Strings

Install Translate Strings

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Workflow

Step 1: Create String Bundle

Step 2: Transfer Strings

Step 3: Translate Strings for Requested Languages

Step 4: Update References in Go Files

Step 5: Update References in Templates

Step 6: Housekeeping

Files

Compare with similar skills

Similar skills

More from microbus-io/fabric

Related

Questions about Translate Strings