orbit-i18n-translator-currency

Audit .po file translation currency against the latest .pot file.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-i18n-translator-currency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orbit-i18n-translator-currency
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-i18n-translator-currency
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-i18n-translator-currency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill detects translation currency issues in .po files, preventing silent-fallback bugs where new strings are missing after updates.

Core Features & Use Cases

  • Currency Audit: Checks .po files against the latest .pot file to ensure all msgids are accounted for.
  • Translation Drift: Measures translation drift to identify outdated translations.
  • Cross-Checking: Validates .mo file freshness, charset correctness, and Plural-Forms headers.
  • Contact and List Consistency: Ensures translator contact information is up-to-date and checks for consistency with the plugin's supported languages list.
  • Plugin-Agnostic: Works with any plugin that ships translated .po files.

Quick Start

Run the skill to audit the currency of your translations in the 'my-plugin' directory.

Frequently Asked Questions about orbit-i18n-translator-currency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect translation drift in .po files against a .pot template?

To detect translation drift in .po files, compare them against the latest .pot file to verify all msgids are accounted for and identify outdated translations. This prevents silent-fallback bugs where new strings are missing after updates.

What causes silent-fallback issues in plugin translations after an update?

Silent-fallback issues in plugin translations occur when .po files lack new msgids present in the updated .pot file. This causes the system to silently fall back to the base language instead of displaying the new translated strings.

Does this translation currency audit work with any plugin's .po files?

Yes, the translation currency audit is plugin-agnostic and works with any plugin that ships translated .po files. It validates headers, charset correctness, and translator contact information regardless of the specific plugin.

How do I validate .mo file freshness and Plural-Forms headers in a translator workflow?

You validate .mo file freshness and Plural-Forms headers by running an audit that cross-checks the compiled binary files against their source .po files, ensuring charset correctness and verifying that plural-form rules are properly configured.

Why are my updated .po translations not showing up in my plugin?

Updated .po translations may not show up if the files lack currency, meaning they are not properly synced with the latest .pot template. Missing msgids cause the plugin to silently fall back to the default language strings.