localization-assistant

Validate Bethesda Game Studio modpack translations for consistency and untranslated strings.

11|3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill localization-assistant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: localization-assistant
Source: https://github.com/BB-84C/bgs-modding-superpowers/tree/main/docs/internal/future-skills/localization-assistant
Command: npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill localization-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Modpack creators and localizers struggle with inconsistent translations, untranslated strings, and unaddressed UI/font compatibility issues when adapting Bethesda Game Studio modpacks for new languages, leading to broken user experiences and wasted rework.

Core Features & Use Cases

  • Glossary & Precedence Checks: Enforces consistent terminology by validating translations against a defined glossary and source precedence rules.
  • Gap Identification: Scans modpack content to find untranslated or inconsistently translated strings across all assets.
  • Workflow Timing Guidance: Clarifies whether translation work should be completed before or after mod patching to avoid redundant effort.
  • Risk Flagging: Alerts users to potential UI, font, and string-table issues that could break localized modpack functionality.
  • Use Case: When localizing a large, complex Bethesda modpack to Spanish, this skill ensures all in-game strings use consistent terminology, catches untranslated UI elements, and warns about font compatibility issues with accented characters.

Quick Start

Use the localization-assistant skill to review your current modpack's translation consistency, identify all untranslated strings, and flag any localization-related risks before release.

Frequently Asked Questions about localization-assistant

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

FAQPage Schema
How do I check for untranslated strings and translation consistency in a Bethesda modpack?

To check translation consistency in a Bethesda modpack, you can automate validation and gap identification to scan all assets for untranslated strings and terminology deviations against a defined glossary.

What is the best way to enforce glossary terminology during modpack localization?

The best way to enforce glossary terminology during modpack localization is applying automated precedence checks that validate translated string tables against your defined source terminology rules.

When should I localize strings in a modpack relative to mod patching?

You should localize strings based on workflow timing guidance that determines whether translation work must be completed before or after mod patching to prevent redundant rework.

Can I automatically detect UI and font compatibility risks for localized Bethesda modpacks?

Yes, you can automatically detect UI and font compatibility risks for localized Bethesda modpacks through risk flagging that alerts you to string-table issues and broken accented characters.

What causes terminology inconsistencies across translated modpack string tables?

Terminology inconsistencies across translated modpack string tables are caused by unvalidated translations that bypass glossary precedence rules, leaving in-game UI elements with divergent localized terms.