Skip to content

Skill for coding agents

Updated: September 15, 2026

A skill is a set of instructions your coding agent loads when a task needs it. The AZbox skill teaches Claude Code, Cursor, Codex, Gemini CLI and other agents how to integrate AZbox into a project without guessing: which package to install, which methods exist, how to pull translations into files, and what to do with new strings. It is open source (GitHub) and follows the Agent Skills standard.

Why it helps

Agents are good at writing code and bad at knowing the details of a product they have never seen. Without the skill they tend to install packages that do not exist, call methods that were never written, or try to create keys through an API that does not accept them. The skill gives them the facts, checked against the published packages and the live API.

Install

Any agent

npx skills add azbox-io/azbox-skills

It detects the agents you have installed and adds the skill to each one.

Claude Code, as a plugin

/plugin marketplace add azbox-io/azbox-skills
/plugin install azbox@azbox

By hand

Copy the skills/azbox/ folder from the repository into your project, under .claude/skills/, .cursor/skills/ or .agents/skills/. Commit it and everyone on the team gets it.

Use

You do not need to call it. Ask for the task and the agent loads the skill when AZbox or localization comes up:

  • “Localize the settings screen with AZbox”
  • “Set up AZbox in this Flutter app”
  • “Pull the Spanish and French translations into locales/ in CI”
  • “Replace the hard-coded strings in the checkout flow”

What the agent will do

  • Use the integration that fits the stack: the Flutter SDK, files pulled with the CLI for anything with its own i18n library, or the REST API from a server.
  • Keep your existing i18n library and feed it from AZbox, instead of replacing it.
  • Look for an existing key before inventing a new one.
  • Add new strings to your source file (ARB, JSON…) and tell you which file to import. Keys are created in the dashboard or by importing a file; the API does not write them.
  • Keep API keys out of the repository.

Pair it with the MCP server

The skill tells the agent how to work with AZbox. The MCP server lets it read your project: search for the key behind a string, or list what is untranslated. With both, the agent reuses your real keys instead of creating duplicates.

Call to action background

Start Global Growth Today

Upload your language files, get them translated, and keep every locale in sync as your product keeps changing.

Get Started - It's Free