Skip to main content
Glama

globalization-skills

Agent skills for localizing software projects. Each skill is a self-contained set of instructions that an AI coding agent can follow to set up or modify i18n in a target project.

The repo follows the Agent Skills open standard, so every skill is a flat top-level directory under skills/ and installable via the standard tooling.

Installation

npx skills (recommended)

Install via the standard npx skills CLI:

# Install a single skill into the current project
npx skills add globalize-now/globalize-skills --skill globalize-guide -a claude-code

# Install all skills
npx skills add globalize-now/globalize-skills -a claude-code

Manual install

Copy a skill directly into your project:

cp -r skills/globalize-guide /path/to/your/project/.claude/skills/globalize-guide

The skill will be available next time you start a Claude Code conversation.

Lovable

lovable-i18n targets the Lovable platform agent rather than Claude Code. Lovable imports a skill reliably only from a repository root, so import it from globalize-now/lovable-i18n. The copy under this repo's skills/lovable-i18n is canonical: edit it here, and every merge to main that changes its SKILL.md is mirrored automatically to that repo's root (.github/workflows/mirror-lovable-i18n.yml). globalize-now/lovable-i18n takes no direct edits — the mirror overwrites its SKILL.md every time.

Related MCP server: tolgee-mcp

Available skills

Skill

Description

globalize-guide

Orchestrates the full i18n journey for a project: detect stack, recommend a library, install + configure, wrap existing strings, and connect Globalize.now for translation (on by default — account sign-in runs upfront, a Workflow for the GitHub repo and its first translation at the end). Drives the work through subagents with shared progress tracking.

globalize-now-account-setup

Install the Globalize CLI and authenticate (account sign-in), before setting up a Workflow.

globalize-now-project-setup

Set up a Globalize Workflow for a GitHub repository (preview, confirm, publish) and, driven by globalize-guide, start its first translation as a pull request. A repository a Project already translates, or a gitlab.com one, stays on a Project. Assumes the CLI is installed and authenticated.

globalize-now-cli-use

Set up a Workflow for a GitHub repository and start its translation, then manage Workflows, runs, glossaries, style guides, translation memories, team members and API keys. Covers a repository a Project already translates.

css-i18n

Audit and convert CSS to logical properties for RTL/bidirectional layout support. Library-agnostic — works with Tailwind, CSS Modules, vanilla CSS, CSS-in-JS.

lovable-i18n

Single-file i18n skill for the Lovable agent (not Claude Code): Lingui + PO setup for both Lovable stacks (Vite SPA and TanStack Start), string wrapping, coding rules in AGENTS.md, a GitHub Actions extraction workflow, and Globalize.now connect. Experimental. This copy is canonical, mirrored automatically to globalize-now/lovable-i18n for import, which takes no direct edits (see the Lovable install note above).

MCP server

The skills handle the i18n work inside your codebase. The Globalize MCP server is the other half: it connects your agent to the Globalize platform API to create translation projects, add languages, manage glossaries and style guides, connect repositories, and track translation jobs.

The production MCP server is built into the Globalize app as a remote Streamable HTTP endpoint — nothing to install:

https://api.globalize.now/mcp

Authenticate with OAuth (your MCP client will prompt) or an API key from the dashboard. Published on the official MCP registry as io.github.globalize-now/globalize. Works with Claude Code (claude mcp add --transport http globalize https://api.globalize.now/mcp), Claude custom connectors, Cursor, and any other MCP client.

Local package (this repo)

mcp-server/ contains the open-source TypeScript implementation, @globalize-now/mcp-server, which talks to the same Globalize API over stdio. See its README for installation and configuration. The hosted endpoint is the maintained production path.

Repository conventions

Each skill lives at skills/<skill-name>/ and contains:

  • SKILL.md — main skill file with name + description frontmatter (required)

  • metadata.json — skill metadata (optional, used by npx skills ecosystem)

  • references/ — supporting guides loaded by the skill (optional; internal nesting is fine)

  • scripts/ — helper scripts (optional)

Skill name = directory name = name: field, all lowercase-with-hyphens.

See CLAUDE.md for the full convention guide.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers