translator

Translate JSON dictionaries and MDX files while preserving structure and SEO relevance.

14|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/syedsaif666/LGTM --skill translator-syedsaif666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translator
Source: https://github.com/syedsaif666/LGTM/tree/main/skills/translator
Command: npx skills add https://github.com/syedsaif666/LGTM --skill translator-syedsaif666

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translating web content between locales often breaks file structure, loses SEO keyword relevance, or produces awkward, non-native text that harms user experience and search rankings. This Skill eliminates those risks by enforcing strict structural preservation, SEO-aware keyword adaptation, and native-quality output for all translated content.

Core Features & Use Cases

  • JSON Dictionary Translation: Preserves all keys, nesting, URLs, interpolation variables, and value types while translating only human-readable string leaf values, with automated structural validation to catch errors.
  • MDX Content Translation: Maintains frontmatter integrity, heading hierarchy, link syntax, and code block formatting while translating prose, alt text, and visible link text, with SEO optimization for title and description fields.
  • Use Case: A B2B SaaS company launching in Germany can use this Skill to translate their English UI JSON dictionaries and product blog MDX files to German, ensuring all content reads naturally to native speakers, ranks for relevant German search terms, and integrates seamlessly with their existing i18n framework.

Quick Start

Use the translator skill to translate all English product page MDX files and UI JSON dictionaries to German for the upcoming European market launch.

Frequently Asked Questions about translator

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

FAQPage Schema
How do I translate JSON dictionaries for i18n without breaking file structure or keys?

To translate JSON dictionaries without breaking structure, only translate human-readable string leaf values while preserving all keys, nesting, URLs, and interpolation variables. Automated structural validation catches errors to ensure your i18n workflow remains fully intact.

What is the best way to translate MDX files while preserving frontmatter and SEO keywords?

The best way to translate MDX files is by maintaining frontmatter integrity, heading hierarchy, and code block formatting while translating prose and optimizing title and description fields for SEO keyword relevance in the target locale.

Does content localization affect SEO and GEO keyword relevance in different locales?

Content localization directly affects SEO by requiring native-quality translation that adapts GEO keyword relevance. This ensures your translated service pages and blog posts rank naturally for relevant search terms in the target locale.

Can I use automated translation for SaaS UI strings without altering interpolation variables?

Yes, you can translate SaaS UI strings safely by preserving interpolation variables and value types. The process enforces strict structural validation and anti-fabrication rules to prevent content invention, omission, or factual alteration across locales.

Why does translating markdown content often result in broken link syntax and formatting?

Translating markdown content breaks formatting when tools alter link syntax or heading hierarchy. Proper MDX content translation maintains exact structural formatting while translating only prose, alt text, and visible link text for native speakers.