Agent skill

Translation Feedback

by vexl-it in vexl-it/vexl

Record translation-quality feedback as a durable rule in the brand narrative.

GPL-3.0Auto-check passedWriting & Content

Install Translation Feedback

skills CLI
$ npx skills add vexl-it/vexl --skill translation-feedback -a claude-code

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

GitHub CLI
$ gh skill install vexl-it/vexl translation-feedback --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/vexl-it/vexl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/translation-feedback .claude/skills/translation-feedback && 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/

Facts

Skill name
translation-feedback
GitHub stars
125
Token cost
~496 tokens
SKILL.md length
255 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
GPL-3.0

At a glance

Record translation-quality feedback as a durable rule in the brand narrative.

  • Works in 5 steps: Pin the rule down. Interview the user… → Place it.… → Mirror where needed. Update… → …
  • The user reports a wrong
  • Calls pnpm
  • Unnatural translation

What it does

Translation Feedback is an agent skill from vexl-it/vexl. Record translation-quality feedback as a durable rule in the brand narrative. Use when the user reports a wrong or unnatural translation, or a preferred rendering of a term in some locale.

Its SKILL.md is about 500 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 Writing & Content, covering Translation. The licence is GPL-3.0.

When your agent uses it

  • The user reports a wrong
  • Unnatural translation
  • A preferred rendering of a term in some locale

Example prompts

  • “/translation-feedback”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Pin the rule down. Interview the user until you can state the rule in one sentence carrying: the English source term or string, the wrong…
  2. Place it. docs/brand-narrative/translator-brief.md is the canonical home: a locale-specific directive for locale-scoped rules, a glossary…
  3. Mirror where needed. Update terminology-and-glossary.md when English-side writers or copy auditors need to know the sanctioned rendering…
  4. Sweep existing strings. Grep packages/localization/locales// for the wrong rendering, report the hits, and fix them if the user wants: a…
  5. Finish. Run pnpm exec prettier --write on the touched docs and show the user the final rule text as written.

What it can do on your machine

Read from SKILL.md and the folder at commit d2d8b1e. 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

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    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

Translation Feedback loads about 496 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 255 words of instructions outside code blocks.

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

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 vexl-it/vexl at commit d2d8b1e, republished under its GPL-3.0 licence (© vexl-it). 255 words, ~496 tokens.

Download SKILL.mdSave it as .claude/skills/translation-feedback/SKILL.md (or your agent's skills folder).
name
translation-feedback
description
Record translation-quality feedback as a durable rule in the brand narrative. Use when the user reports a wrong or unnatural translation, or a preferred rendering of a term in some locale.

Translation feedback

Turns "this translation is wrong" into a durable rule, so every future translator subagent gets it right. The docs are the translators' only memory — a rule that isn't written down is lost by the next audit.

Steps

  1. Pin the rule down. Interview the user until you can state the rule in one sentence carrying: the English source term or string, the wrong rendering, the correct rendering, the affected locale(s), and the reason (naturalness, terminology, tone). Ask focused questions with your best-guess recommendation attached; keep going until nothing is ambiguous. Done means the user confirms your one-sentence statement of the rule — not before.
  2. Place it. docs/brand-narrative/translator-brief.md is the canonical home: a locale-specific directive for locale-scoped rules, a glossary entry for term-wide ones — always with the wrong→right example. Before writing, check existing entries for contradictions: when the new rule is an exception to a standing rule (e.g. a global term ban), state the exception explicitly in both places instead of leaving them contradicting.
  3. Mirror where needed. Update terminology-and-glossary.md when English-side writers or copy auditors need to know the sanctioned rendering, and audit-checklist.md when one of its checkboxes would now false-positive on it.
  4. Sweep existing strings. Grep packages/localization/locales/<locale>/ for the wrong rendering, report the hits, and fix them if the user wants: a plain term swap is a direct edit; anything needing real rephrasing goes to a translator subagent per docs/translating.md.
  5. Finish. Run pnpm exec prettier --write on the touched docs and show the user the final rule text as written.

© vexl-it, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/translation-feedback of vexl-it/vexl.

Open the folder on GitHubat commit d2d8b1e

Compare with similar skills

Translation Feedback 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.

Translation Feedback compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Translation Feedback this skillvexl-it/vexl125—~496Automated safety check: PassGPL-3.0
Translation Diff ExportDevolutions/UniGetUI26k—~1.1kAutomated safety check: PassMIT
Sync Translationssymfony/symfony31k—~1.9kAutomated safety check: PassMIT
Translation Diff ImportDevolutions/UniGetUI26k—~750Automated safety check: PassMIT
Translation Diff TranslateDevolutions/UniGetUI26k—~934Automated safety check: PassMIT
Generate Translationspayloadcms/payload45k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Translation Diff Export

    Devolutions/UniGetUI

    Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.

    26k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed
  • Sync Translations

    symfony/symfony

    Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…

    31k GitHub stars~1.9k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Translation Diff Import

    Devolutions/UniGetUI

    Merges translated key-value pairs from a UniGetUI JSON localization patch back into the full language file and validates the merged result.

    26k GitHub stars~750 tokensUpdated today
    Writing & ContentAuto-check passed
  • Translation Diff Translate

    Devolutions/UniGetUI

    Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back.

    26k GitHub stars~934 tokensUpdated today
    Writing & ContentAuto-check passed
  • Generate Translations

    payloadcms/payload

    A skill your agent uses when new translation keys are added to packages to generate new translations strings

    45k GitHub stars~1.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed

More from vexl-it/vexl

  • How to add or change a user-facing string in the Vexl app and translate it into all shipped locales.

    125 GitHub stars~632 tokensUpdated yesterday
    Auto-check passed
  • Translation Audit

    vexl-it/vexl

    Translations audit — fill missing keys in every shipped locale, re-translate keys whose English changed, delete stale ones, flag suspicious values.

    125 GitHub stars~693 tokensUpdated yesterday
    Auto-check passed

Questions about Translation Feedback

What does Translation Feedback do?

Record translation-quality feedback as a durable rule in the brand narrative. Translation Feedback is an agent skill from vexl-it/vexl. Record translation-quality feedback as a durable rule in the brand narrative.

When should I use Translation Feedback?

Translation Feedback fits situations like: the user reports a wrong; unnatural translation; A preferred rendering of a term in some locale.

How do I install Translation Feedback in Claude Code?

Run `npx skills add vexl-it/vexl --skill translation-feedback -a claude-code`. Or copy the skill folder (.agents/skills/translation-feedback in vexl-it/vexl) into .claude/skills/translation-feedback in your project. Claude Code loads it when a task matches its description.

How do I install Translation Feedback in Codex?

Run `npx skills add vexl-it/vexl --skill translation-feedback -a codex`. Or copy the skill folder (.agents/skills/translation-feedback in vexl-it/vexl) into .agents/skills/translation-feedback in your project. Codex loads it when a task matches its description.

Can I use Translation Feedback 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 vexl-it/vexl --skill translation-feedback -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/translation-feedback, .gemini/skills/translation-feedback, .github/skills/translation-feedback and .opencode/skills/translation-feedback in your project.

What does Translation Feedback need to run?

Going by SKILL.md and its folder, Translation Feedback needs the command-line tools its instructions call (pnpm).

Does Translation Feedback 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 Translation Feedback 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 Translation Feedback use?

Translation Feedback is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Translation Feedback use?

About 496 tokens (SKILL.md is roughly 2k 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 Translation Feedback?

Skills that share tags, products or a category with Translation Feedback: Translation Diff Export (Devolutions/UniGetUI, 26k stars), Sync Translations (symfony/symfony, 31k stars), Translation Diff Import (Devolutions/UniGetUI, 26k stars) and Translation Diff Translate (Devolutions/UniGetUI, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Translation Feedback?

vexl-it (a GitHub organization) maintains it in vexl-it/vexl, which has 125 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.

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