language-config

Configure multilingual brand settings and translation preferences via YAML frontmatter.

726|123|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill language-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: language-config
Source: https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/language-config
Command: npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill language-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configure and manage multilingual settings for the active brand to ensure consistent translation workflows across markets.

Core Features & Use Cases

  • Manage the primary language for content and translation routing.
  • Add or remove secondary languages and corresponding content targets.
  • Maintain do-not-translate terms to preserve brand names and technical terms.
  • Set per-language translation preferences and locale formatting.

Quick Start

Set the primary language to en-US and add fr-FR as a secondary language to begin multilingual content routing.

Frequently Asked Questions about language-config

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

FAQPage Schema
How do I configure multilingual settings for a brand to manage translation workflows across markets?

Configure multilingual settings by setting a primary language, adding or removing secondary languages, and applying locale formatting to ensure consistent translation routing across brand campaigns and markets.

How do I add a secondary language like fr-FR to my brand profile for content routing?

Add fr-FR as a secondary language to your brand profile's language object to begin multilingual content routing, enabling targeted translation workflows alongside your primary locale.

Can I preserve specific brand names and technical terms so they are not translated automatically?

Yes, you can maintain a do-not-translate terms list within your language configuration to preserve brand names and technical terms from being altered during automatic translation routing.

How do translation preferences override automatic language routing for specific content?

Explicit translation preferences can be set per language to override automatic routing, giving you manual control over how content is localized instead of relying solely on default brand profile settings.

Does this multilingual configuration tool support YAML frontmatter for language discovery?

Yes, the configuration supports YAML frontmatter-based discovery to automatically detect and apply language settings, updating the brand profile's language object for consistent locale formatting across campaigns.

What is the best way to manage locale formatting and do-not-translate terms for multiple campaign markets?

The best approach is centralizing locale formatting and do-not-translate terms in the active brand profile's language object, ensuring all downstream campaigns inherit consistent multilingual rules.