Gå til indhold

Crowdin Skills

Dette indhold er ikke tilgængeligt i dit sprog endnu.

Translate in Crowdin

Crowdin Skills are instruction packages that teach an AI coding agent how to work with Crowdin. Once they are installed, the agent knows the Crowdin CLI commands, the configuration file format, the API client, and the query languages, so you can describe a localization task in plain language instead of looking up the syntax yourself.

Skills do not connect the agent to your Crowdin account on their own. They work inside your development environment, next to your source code, unlike the Crowdin MCP Server. A few skills rely on the MCP Server for reading and changing project data, and the Crowdin plugin includes it.

Finding the right approach

  • how-to-crowdin – Answering “how do I do X in Crowdin” by mapping a localization problem to the cheapest thing that already solves it: a built-in feature, a few actions on your project data, an app from the Crowdin Store, or a custom app. The details then go to the skill that covers that route.

Setting up localization

  • i18n-setup – Taking a project from hardcoded strings to continuous translation, or connecting a project that is already internationalized. It also prepares translator context, a starting glossary, and screenshots, and hands off continuous sync to the github-action skill.

Syncing content

  • crowdin-cli – Syncing source files and translations between your project and Crowdin with Crowdin CLI, including crowdin.yml configuration, auto-translation, integrations driven through installed Crowdin apps, and migration from CLI v4.
  • github-action – Setting up and debugging the crowdin/github-action step in a GitHub workflow.

Preparing content for translators

  • context-extraction – Writing context for the source strings that need it, downloaded and uploaded back with the crowdin context commands.
  • glossary-terms-extraction – Building or expanding a glossary from your source strings and other content you provide, such as docs or websites. Terms are added only after you review them, and brand names are marked as non-translatable.
  • glossary-term-translations – Filling in glossary term translations from how your project already translated them. Translations are added as drafts for you to review, and a language with no clear counterpart stays empty. Requires the Crowdin MCP Server.
  • generate-screenshots – Capturing screenshots of your running web, mobile, or desktop app and uploading them to Crowdin, tagged to the strings they show, so translators see where each string appears. Strings without a screenshot are found first, and the capture definition stays in your repository for the next release.

Translating content

  • translate – Drafting translations of your app’s strings into your project’s resource files and uploading them to Crowdin as suggestions for review.

Working with project data

  • crowdin-api-client – Using the JavaScript and TypeScript API client, including pagination, uploads, and error handling.
  • croql – Writing and optimizing CroQL expressions for strings, translations, TM segments, and glossary terms.
  • graphql – Writing and debugging Crowdin GraphQL queries against the actual schema.

Building apps

  • create-app – Scaffolding, developing, and publishing a Crowdin app.

Sending feedback

  • feedback – Drafting feedback on Crowdin or its developer tools and sending it to the Crowdin team as a public GitHub issue after you approve the draft.

Skills work with Claude Code, Claude Cowork, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot, OpenCode, Cline, Windsurf, and other AI coding agents. Each client adds them in its own way, so follow the installation instructions in the repository.

Install Crowdin Skills

Once installed, the skills become available on their own when you work in a project that uses Crowdin or mention something they cover. You can also point your agent at them directly in a request.

Watch the i18n-setup skill take a project from hardcoded strings to a Crowdin project with continuous translation:

Play

Watch the create-app skill build and publish a Crowdin app that checks source text and translation consistency:

Play

Skills and the Crowdin MCP Server both help an AI agent work with Crowdin, in different places.

  • Crowdin Skills teach the agent how Crowdin’s developer tools work. The agent applies that knowledge in your repository, against your source code and your crowdin.yml.
  • Crowdin MCP Server connects the agent to your Crowdin account, so it can read and change project data directly.

You can use both: Skills to run the right command in your repository, and the MCP Server to check the result in your project. When you install Crowdin Skills as a plugin, the MCP Server comes with it. The how-to-crowdin skill is built around that combination – it describes each step as an action on your strings, files, or reports, which the agent can then perform through the MCP Server.

Read more about the Crowdin MCP Server.

Was this page helpful?