⚡AgentSkills
🌐 Localization & i18n · Linguistic Quality

Run linguistic QA that catches real errors

In-context review, error typology scoring, and vendor feedback loops improving over releases.

intermediate~35 minLocalization Engineersi18n DevelopersLocalization Managers

Steps

  1. 1Review IN CONTEXT on real builds, not spreadsheet columns
  2. 2Score errors by typology: accuracy, terminology, style, locale convention, typo
  3. 3Critical (misleading/damaging) blocks release; minor batches into next sprint
  4. 4Feedback to translators references error codes + suggested fix + why
  5. 5Maintain per-product glossary and termbase; enforce in tooling
  6. 6Track error density trend per locale/vendor as the quality metric

Common Pitfalls

  • ▲Reviewing strings in isolation missing truncation and gender clashes
  • ▲Subjective style nitpicks weighted like factual errors

Commands

Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill linguistic-quality-lqa-review-cycle
Install globally
$ npx skills add aniruddhaadak80/skills --skill linguistic-quality-lqa-review-cycle -g

Tags

#lqa#translation-quality#localization-i18n#linguistic-quality

Related skills

Get locale data right: dates, numbers, namesfoundation

ICU-driven formatting, name ordering, address forms, and timezone correctness per locale.

🌐 Localization & i18n·~25m
Open →