/multilingual-score

name: multilingual-score
description: "Score translated or localized content into one composite quality verdict — technical translation scoring (length ratio, formatting, do-not-translate terms, placeholders), content quality in the target language, brand voice consistency, and target-market compliance — classified as Publish Ready (85+), Native Speaker Review (70-84), or Re-translate (below 70) with specific, located fix suggestions per issue. Triggers on \"/digital-marketing-pro:multilingual-score\", \"is this German translation ready to publish\", \"score this localized landing page\", \"did the translation keep our brand voice\", \"check compliance on the Japanese version\". Runs the language-router, eval-runner, and brand-voice-scorer scripts, reads the brand profile's language config and do-not-translate list, and compares against the brand's multilingual baseline when past runs exist."

/digital-marketing-pro:multilingual-score

Purpose

Score translated or localized content across multiple quality dimensions to determine whether it is ready for publishing, needs native speaker review, or requires re-translation. Combines technical translation scoring (length ratios, formatting preservation, placeholder integrity, key term consistency) with content quality evaluation, brand voice consistency checking, and market-specific compliance verification into a single composite multilingual quality score.

Use this command after any translation or localization workflow to validate quality before content goes live. It replaces subjective "looks good" assessments with a structured, repeatable scoring methodology that catches issues automated translation often introduces — brand voice drift, formatting damage, missing do-not-translate terms, compliance gaps in the target market, and length distortion that signals missing or added content. The composite score provides a clear publish/review/re-translate classification so the team knows exactly what action to take.

Input Required

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

• **Original content**: The source text that was translated — provided as inline text, a file path, or a URL to the source content. This serves as the reference for translation accuracy scoring. Required for technical translation scoring; if omitted, only content quality, brand voice, and compliance dimensions are scored
• **Translated content**: The translated or localized text to score — provided as inline text, a file path, or a URL. This is the primary content being evaluated. Required
• **Source language**: The language code of the original content (e.g., `en-US`, `en-GB`, `de-DE`). Defaults to the brand's primary language from the language configuration if not specified
• **Target language**: The language code of the translated content (e.g., `de-DE`, `fr-FR`, `hi-IN`, `ja-JP`). Required — determines which compliance rules apply and which translation service benchmarks to reference
• **Do-not-translate terms** (optional): Specific terms that must appear unchanged in the translation. Defaults to the brand profile's `language.do_not_translate` list. Additional terms can be provided to supplement the brand list for this specific scoring run
• **Content type** (optional): The type of content being scored — `blog`, `email`, `ad`, `landing_page`, `social`, `product_description`, `legal`, `technical`. Affects content quality scoring weights and brand voice expectations. Defaults to auto-detection based on content structure

Process

1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply brand voice dimensions, compliance rules for target markets (`skills/context-engine/compliance-rules.md`), and industry context. Load the language configuration — specifically the do-not-translate terms from `language.do_not_translate` and any translation quality baselines from past scoring runs. Also check for guidelines at `~/.claude-marketing/brands/{slug}/guidelines/_manifest.json` — if present, load restrictions and voice-and-tone rules that apply across all languages. Check for agency SOPs at `~/.claude-marketing/sops/`. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. 2. **Run technical translation scoring**: Execute `language-router.py --action score` with the original content, translated content, source language, target language, and do-not-translate terms. This produces four sub-scores: **length ratio** (translated content length versus expected length for the language pair — e.g., German typically runs 10-35% longer than English, Japanese typically runs 20-50% shorter, per the `EXPANSION_RATIOS` table in `language-router.py` (the source of truth for expected ranges); deviations beyond expected ranges indicate missing or added content), **formatting preservation** (markdown structure, HTML tags, merge tags like {{first_name}}, UTM parameters, and link structures survived translation intact), **key term consistency** (every do-not-translate term from the brand profile and any additional specified terms appears exactly as specified in the translation), and **placeholder integrity** (all variables, template tokens, and dynamic content markers are present and correctly positioned in the translated version). 3. **Run content quality evaluation**: Execute `eval-runner.py --action run-quick` on the translated content alone, scoring it as standalone content in the target language. This assesses structural quality, readability for the target audience, completeness, and coherence — catching cases where a translation is technically accurate but reads poorly as native content. The eval-runner scores content against the plugin's standard quality dimensions regardless of whether it was translated or originally authored. 4. **Run brand voice consistency check**: Execute `brand-voice-scorer.py --brand