translation

Translate and localize content across languages with glossary and style guidelines.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit --skill translation-getfresh-ventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: translation
Source: https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit/tree/main/skills/gfv-content-translation
Command: npx skills add https://github.com/GetFresh-Ventures/gxd-ceo-ai-kit --skill translation-getfresh-ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translation, terminology, and style-management workflows to ensure consistent, brand-aligned multilingual content across channels, reducing drift and rework.

Core Features & Use Cases

  • Workflow: end-to-end translation pipeline from briefs to reviewed content, including glossary alignment and post-edit steps.
  • Glossary & Terminology: centralized terms, context notes, and style rules to maintain consistency across locales.
  • Style Guide & QA: voice, formatting, SEO considerations, and native reviewer checks to preserve brand.
  • Human vs MT decisioning: guidelines on when to use human translation vs machine translation and post-editing.
  • Localization integration: i18n considerations, hreflang, URL structure, and localized metadata.

Quick Start

Provide a source document and target language to generate a translated draft following glossary and style guidelines.

Frequently Asked Questions about translation

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

FAQPage Schema
How do I maintain brand voice during multilingual translation of marketing and support content?

To maintain brand voice during multilingual translation, enforce centralized style guides and glossary terminology across all locales. This ensures consistent tone, formatting, and SEO considerations across product docs, marketing pages, and support content.

What is the best way to manage a translation workflow with glossary alignment and post-editing?

The best way to manage a translation workflow is using an end-to-end pipeline from briefs to reviewed content. This pipeline includes glossary alignment, human versus machine translation decisioning, and post-edit steps to reduce drift and rework.

When should I use human translation versus machine translation for localized content?

Use human translation versus machine translation based on specific content guidelines for quality assurance. Establishing clear human versus MT decisioning rules ensures native reviewer checks and post-editing preserve brand voice where MT falls short.

How does localization integration handle hreflang, URL structure, and localized metadata?

Localization integration handles hreflang, URL structure, and localized metadata by applying i18n considerations to the translated content. This ensures search engines correctly index and serve the appropriate locale-specific pages for SEO.

Can I use a centralized glossary to maintain terminology consistency across multiple locales?

Yes, you can use a centralized glossary to maintain terminology consistency across multiple locales. Centralized terms, context notes, and style rules prevent brand drift and ensure uniform multilingual content across all translation channels.