Goman Translation Skill Guide

Install and Use the Goman Translation Skill

Use this page when you prefer an installable skill with command-based localization workflows, from language discovery to bulk translation updates.

🧩

Installable Skill

Install the Goman translations skill with one command and run workflows directly from local scripts.

🛠️

Command-Based Automation

Use focused commands for languages, namespaces, get, search, create, and delete operations.

📝

Context for Translators

Create or update translations with context so translators and AI systems receive clearer intent.

🚀

Workflow-Ready

Run practical workflows for audits, bulk import, and key lifecycle management.

Who is it for?

Developers and localization managers who prefer scriptable skill workflows and explicit command control in repository-local tooling.

Get started

Install the skill, configure environment credentials, then use command workflows to create, search, update, and clean up translations.

Skill Setup and Usage Examples

Below is a practical guide for installing the goman-translations skill, setting credentials, and running command-based localization workflows.

1
Install and setup

github.com/bel-frontend/goman-live-skills ↗

Copy the skill to your agent (all agents detected on your machine):

npx skills add bel-frontend/goman-live-skills

Or for a specific agent / globally:

npx skills add bel-frontend/goman-live-skills -a github-copilot
npx skills add bel-frontend/goman-live-skills -a claude-code
npx skills add bel-frontend/goman-live-skills -g

Set up credentials (run once from your project root):

npx github:bel-frontend/goman-live-skills

Open .agents/skills/goman-translations/.env and fill in your credentials (from goman.live dashboard → Settings → API Keys):

GOMAN_API_KEY=your_api_key
GOMAN_APP_ID=your_application_id

2
Usage

Just ask your agent in natural language:

- localize my LoginScreen component
- add key auth.login.button with "Log In" in English
- check if screens.home.title exists
- audit missing translations in the auth namespace
- search all keys containing "button"

Scripts the agent runs automatically (can also run manually from .agents/skills/goman-translations/scripts/):

node goman-languages.js
node goman-namespaces.js
node goman-get.js auth.login.button
node goman-search.js --namespace auth --query button
node goman-create.js auth.login.button '{"en":"Log in"}' "Login button"
node goman-delete.js auth.login.button

3
Recommendations

Use dotted full keys so namespace extraction works (e.g., auth.login.button).

Always run languages and namespaces checks before creating new keys.

Pass translator context when creating or updating keys for higher translation quality.

Treat delete as irreversible and verify with goman-get.js first.

4
Troubleshooting

Missing credentials: fill .env with GOMAN_API_KEY / GOMAN_APP_ID from your goman.live dashboard.

Validation errors: ensure fullKey includes at least one dot (namespace.key).

Unexpected overwrite: call get first and only create missing translations when needed.

For more details and advanced workflows (audit, localize folder, bulk import), use the complete goman-translations skill references.