translation

Guide multilingual translation workflows with glossary and style adherence.

Updated Apr 24, 2026

Search Tags:#localization #style guide #glossary #translation workflow #translation quality #machine translation

Ready to run

npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill translation-otto-poblysh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: translation
Source: https://github.com/otto-poblysh/pedagemy-early-access/tree/main/.agents/skills/translation
Command: npx skills add https://github.com/otto-poblysh/pedagemy-early-access --skill translation-otto-poblysh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you produce accurate, on-brand multilingual content by standardizing terminology and writing rules, reducing costly rework from inconsistent or low-quality translations.

Core Features & Use Cases

Workflow: Brief → translate → native review to ensure clarity and correctness across languages.
Terminology: Build and enforce a glossary so the same terms are used consistently (including market-specific variants).
Quality & SEO: Apply QA checks and handle translated metadata and hreflang so localized pages rank and behave correctly.

Quick Start

Use the translation skill to create a translator brief and quality checklist for translating a landing page into Spanish with consistent terminology and SEO-safe keyword handling.

Frequently Asked Questions about translation

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

FAQPage Schema

How do I create a translator brief for localized marketing copy?▼

To create a translator brief for localized marketing copy, define your target locale, required terminology, and style guidelines. This ensures the translation workflow produces consistent, on-brand content by standardizing language rules before the actual translation begins.

What is the best way to maintain glossary consistency across multilingual product UI?▼

The best way to maintain glossary consistency across multilingual product UI is to enforce a standardized glossary throughout the translation workflow. This prevents terminology drift and ensures the same terms are used consistently across all customer-facing interfaces.

How do I handle hreflang and translated metadata for SEO-safe landing pages?▼

To handle hreflang and translated metadata for SEO-safe landing pages, apply locale-aware quality checks during your translation workflow. This ensures localized pages rank correctly and function as expected in target regional search engines.

When should I use human translation instead of machine translation for technical docs?▼

You should use human translation instead of machine translation for technical docs when strict glossary adherence and style guide compliance are required. This approach reduces costly rework from inconsistent translations and ensures complex terminology is accurately localized.

Does standardizing terminology reduce translation rework for landing pages?▼

Standardizing terminology reduces translation rework for landing pages by enforcing consistent glossary and style rules upfront. This prevents costly revisions caused by inconsistent or low-quality translations across different languages and market-specific variants.

Can I run native review and QA checks in the same translation workflow?▼

Yes, you can run native review and QA checks within the same translation workflow. Moving from brief creation to translation and native review ensures clarity and correctness, while integrated quality checks verify glossary adherence and SEO metadata.