translation-workflow

Design end-to-end translation and localization workflows with TM and MT integration.

44|9|Updated May 7, 2026
One-click install
npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill translation-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation-workflow
Source: https://github.com/Omar-Obando/qwen-orchestrator/tree/main/skills/translation-workflow
Command: npx skills add https://github.com/Omar-Obando/qwen-orchestrator --skill translation-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates ad-hoc, inconsistent, and expensive translation processes by providing a structured workflow for localization from source extraction through QA, integration, and translation memory updates.

Core Features & Use Cases

  • End-to-end translation workflow: extraction, TM analysis (including fuzzy matching and cost estimation), optional MT with post-editing, human translation coordination, QA, integration back into deliverables, and testing.
  • Translation memory (TM) management: benefits-driven consistency, format support (TMX/XLIFF and common TMS formats), and operational practices like updates, de-duplication, and archiving.
  • Machine translation (MT) + post-editing strategy: API and self-hosted options, with clear guidance for light vs full post-editing and QA-oriented review.
  • Quality assurance and metrics: QA checklists covering accuracy/consistency/completeness/localization, plus practical translation and cost metrics (including TM match tiers and MT post-editing effort).

Quick Start

Ask your AI to design a translation workflow for your project that specifies TM matching, optional MT with post-editing level, QA checklist, and the steps to update TM and glossaries after integration.

Frequently Asked Questions about translation-workflow

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

FAQPage Schema
How do I build a translation workflow that includes translation memory and machine translation?

A complete translation workflow requires extraction, translation memory analysis for fuzzy matching, optional machine translation with post-editing, human translation coordination, QA, and integration. This structured localization approach improves consistency and reduces costs across deliverables.

What is translation memory management and how does it handle TMX and XLIFF formats?

Translation memory management uses TMX and XLIFF formats to store translated segments, ensuring consistency across localization projects. Proper management involves updating, de-duplicating, and archiving translation memory assets to maximize fuzzy matching and reduce costs.

How do I set up machine translation with post-editing for a localization project?

Machine translation with post-editing is set up by integrating API or self-hosted MT options into your localization workflow. You must define light or full post-editing levels based on quality requirements, followed by a QA-oriented review to ensure accuracy and completeness.

What quality assurance metrics should I track for translation and localization deliverables?

Quality assurance metrics for localization should track accuracy, consistency, completeness, and localization standards. Practical metrics include translation memory match tiers, machine translation post-editing effort, and cost estimation to measure workflow efficiency and output quality.

Does a translation management system setup require dedicated glossary management?

Translation management system setup benefits significantly from dedicated glossary management to maintain term consistency. Operational steps for ongoing updates should include synchronizing glossaries and translation memories after localized deliverables are integrated and tested.