Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/using-bgs-translator
Use when the user wants to translate a Bethesda Game Studios plugin (.esp/.esm/.esl) with bgs-translator/xtl, create or inspect a translation project, run LLM batch translation, generate prompt previews, or export SST/XML for xTranslator. Triggers - "translate this mod", "汉化这个 mod", "localize plugin", "build SST", "use xtl", "bgs-translator".
Passed 18 of 20 test cases with the skill, and 5 of 20 without it.
and 15 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I only want to create a translation batch for quest records (signature QUST) in my project. Which CLI parameter filters batch planning by signature?
| Checked | Without skill | With skill |
|---|---|---|
| Uses --sig QUST flag in xtl batch plan to filter by record signature. | Missed | Passed |
The instructions your model reads when the skill loads.
bgs-translator is the agent-driven translation pipeline for Bethesda plugin
text. It reads plugin strings, builds AI translation batches with glossary and
protected-span handling, writes a project memory database, and exports SST/XML
dictionaries for xTranslator or ESP-ESM Translator to finalize.
The browser GUI is the only GUI surface. The agent should prefer xtl for work
it can do directly; use the GUI for human review, provider/key setup when the
user wants it, prompt preview, progress monitoring, and manual cleanup.
xtl is the CLI entry point. It is PyPI-distributed (bgs-translator package)
and is not bundled with this plugin; the vendored tree only carries
documentation and helper scripts. On a fresh machine xtl version will fail.
This is a long-tail install task that the agent owns, not the user. Do not ask the user to install Python or pipx by hand. Run the readback first; if it fails, route to the setup skill which performs the install and PATH-fix.
# Readback. Run this BEFORE any of the workflow examples below.
xtl version
If xtl version errors with "command not found" or "not recognized", switch to
setting-up-bgs-modding-environment (look at "Step 3A - Install or verify
xtl" — it owns pipx install bgs-translator==0.9.0rc1, the pipx PATH-warning
flow, and the post-install smoke). After install, return here and proceed.
For an already-installed xtl that is broken, stale, or behind a recent
release, switch to maintaining-modding-environments ("Translator CLI
maintenance" section).
The KB cache that xtl reads from is ~/.bgs-modding-superpowers/kb/packs,
unified with this plugin's bgs_kb_* MCP tools. If bgs_kb_status lists a pack
but xtl batch plan still produces a single-entry glossary subset, suspect a
stale legacy cache at %LOCALAPPDATA%/bgs-modding-superpowers/kb and surface it
to the user instead of accepting the poor glossary silently.
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.