skills.rest
BB-84C
BB-84CCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

using-bgs-translator

Automate LLM-powered batch translation of Bethesda plugin files with placeholder masking.

11|3|Updated Apr 15, 2026
Search Tags:#glossary enforcement#bethesda#mod translation#xtl#plugin localization#sst export#xtranslator
One-click install
npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill using-bgs-translator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: using-bgs-translator
Source: https://github.com/BB-84C/bgs-modding-superpowers/tree/main/plugins/bgs-modding-superpowers/skills/using-bgs-translator
Command: npx skills add https://github.com/BB-84C/bgs-modding-superpowers --skill using-bgs-translator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually translating Bethesda Game Studios plugin files (.esp/.esm/.esl) is error-prone, as it requires preserving protected placeholders like EditorIDs and FormIDs, maintaining consistent mod-specific glossary terms, and accounting for runtime string override chains from update and compatibility patches. This Skill automates the entire localization workflow while eliminating these common manual mistakes.

Core Features & Use Cases

  • LLM-Powered Batch Translation: Automates translation of plugin text with built-in placeholder masking, glossary enforcement, and game/mod context injection for accurate, consistent results.
  • End-to-End Workflow Management: Handles project initialization, batch planning, translation provider configuration, and SST/XML export for finalization in xTranslator or ESP-ESM Translator.
  • Use Case: Localize a Starfield quest mod to Simplified Chinese, ensuring all dialogue, item names, and UI text are translated correctly while preserving FormIDs, script keys, and existing mod terminology.

Quick Start

Use the using-bgs-translator skill to translate the attached Bethesda plugin file to your target language while preserving all protected placeholders and mod-specific glossary terms.

Frequently Asked Questions about using-bgs-translator

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

FAQPage Schema
How do I automate Bethesda plugin translation while preserving protected placeholders like FormIDs?▼

Bethesda plugin translation can be automated using LLM-powered batch processing with built-in placeholder masking to preserve EditorIDs and FormIDs. This workflow injects game and mod context for accurate localization of .esp, .esm, and .esl files.

What's the best way to translate Skyrim or Starfield mods with consistent glossary enforcement?▼

Translating Skyrim or Starfield mods consistently requires automated glossary enforcement during batch translation. This ensures mod-specific terminology remains uniform across dialogue, item names, and UI text while respecting runtime string override chains.

How does placeholder masking work when localizing Bethesda .esp and .esm files?▼

Placeholder masking protects critical structural identifiers like EditorIDs and FormIDs by isolating them before LLM text processing. This prevents accidental translation of game logic keys during the automated localization of Bethesda plugin files.

Can I export translated Bethesda plugin files to SST or XML for xTranslator finalization?▼

Yes, translated Bethesda plugin files can be exported to SST or XML formats for finalization in xTranslator or ESP-ESM Translator. This end-to-end workflow handles project initialization, batch planning, and provider configuration before the final export.

Does this batch translation workflow handle runtime string override chains from compatibility patches?▼

Yes, the batch translation workflow accounts for runtime string override chains originating from update and compatibility patches. It attributes override chains correctly to prevent translation conflicts and maintain mod stability across localized versions.

How do I configure translation provider API keys securely for Bethesda mod localization?▼

Translation provider API keys can be configured securely during the project initialization and provider configuration phase of the localization workflow. This ensures safe API key handling while connecting LLM services for batch text processing.

Related Skills

Explore More Content & Communication Skills→
BB-84CBB-84C
11

xedit-automation

Route xEdit operations on Bethesda plugin files through mandatory safety harnesses.

Community
Advanced
adzcsx2adzcsx2
1

adt:android-i18n

Detect hardcoded Chinese strings in Android XML and Kotlin/Java files and generate localized resources.

Community
Intermediate
intelli-verse-xintelli-verse-x
1

ivx-localization

Localize game text, assets, and store listings across multiple languages.

Official
Advanced
BB-84CBB-84C
11

Test Session Guide

Generate structured in-game testing checklists for Bethesda mods after installs, patches, or localization.

Community
Basic