Best fit
Language-agnostic QA on translation files: placeholder mismatches, untranslated strings, length overflow, terminology drift.
// localization
Localization QA Auditor
Run structural QA on your translation files across locales: placeholder mismatches, untranslated strings, length overflow, terminology drift, and missing keys. It checks form, not meaning, so you do not need to speak the language.
What it flags
- Placeholder mismatches.
- Untranslated strings.
- Length overflow.
- Terminology drift.
- Missing keys.
- Across JSON, gettext .po, and .properties files.
How to run
Point it at JSON, gettext .po, or .properties locale files. Read-only.
Good to know
Language-agnostic structural QA; it does not judge fluency, tone, or cultural fit.
// choose with context
Is Localization QA Auditor the right skill?
It returns
Language-agnostic QA on translation files: placeholder mismatches, untranslated strings, length overflow, terminology drift.
Do not use it as
Do not treat a successful run as proof beyond the supplied files, declared scope, and evidence the skill actually checked.
Compatibility, access, version, and licence
- Reads or accesses
- Only the files or context you deliberately provide; review the listing before granting additional access.
- Compatibility
- Agents that read the open SKILL.md format. Verify runtime and service requirements at the purchase or install destination.
- Version
- Verify the current package version at the linked destination.
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
How is this different from the i18n auditor?
That one scans source for hardcoded strings; this does cross-locale translation QA across formats.
Does it change anything?
No. It is read-only and flags issues for you to act on.
QA the translations without speaking the language.
Current price and purchase option are shown on Agensi. Instant download. Works with any agent that reads SKILL.md.
Get Localization QA Auditor on Agensi