multilingual-score

Installation
SKILL.md

/dm: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
Related skills
Installs
36
GitHub Stars
100
First Seen
Feb 27, 2026