localize-campaign

Installation
SKILL.md

/digital-marketing-pro:localize-campaign

Purpose

Full campaign localization across multiple target markets. This command takes all campaign assets — emails, ads, social posts, landing pages, video scripts, push notifications — and adapts them for each target market. It goes far beyond translation: cultural references are adjusted, compliance elements are modified per region, SEO is localized, creative recommendations are adapted, and assets are prepared for multilingual publishing.

This is the comprehensive localization workflow for market expansion. Where /digital-marketing-pro:translate-content handles a single piece of content, /digital-marketing-pro:localize-campaign orchestrates the localization of an entire campaign across multiple markets simultaneously. It coordinates translation service routing per language, transcreation for emotional content, market-specific compliance additions, cultural adaptation based on Hofstede cultural dimensions, localized SEO, RTL formatting for applicable languages, and produces a deployment-ready package per market with quality scores and publishing checklists.

Input Required

The user must provide (or will be prompted for):

  • Campaign assets: Content for localization, provided as:
    • File paths per asset type (e.g., "emails: /campaign/email-welcome.html, /campaign/email-follow-up.html; ads: /campaign/fb-ad.txt, /campaign/google-ad.txt; social: /campaign/ig-post.txt")
    • A campaign directory (e.g., "/campaign-q1/") — all files will be categorized by type based on naming conventions or metadata
    • Inline content blocks with asset type labels
  • Target markets: One or more market codes in language-region format (e.g., hi-IN, de-DE, ja-JP, fr-FR, ar-SA, pt-BR, es-MX). Each code specifies both the language and the cultural/regulatory context
  • Campaign brief or strategy document: Optional — provides campaign objectives, messaging hierarchy, key themes, and audience segments. Used to inform transcreation decisions and ensure localized versions maintain strategic alignment
  • Market-specific compliance requirements: Optional — additional regulatory, legal, or industry requirements per market beyond what is already in the brand profile (e.g., "Germany requires Impressum link", "India requires MRP display", "Saudi Arabia prohibits alcohol imagery references")
Related skills
Installs
31
GitHub Stars
100
First Seen
Feb 27, 2026