Translation
Run brief-to-review translation workflows with glossaries, style guides, and human-vs-MT choices for multilingual marketing and product copy.
Overview
Translation is an agent skill most often used in Grow (also Launch, Build) that guides multilingual copy workflows, terminology, and quality for solo builders shipping localized content.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill translationWhat is this skill?
- Brief → translate → review workflow with terminology and market-specific variants
- Glossary creation and style-guide voice, tone, and formatting per language
- Human translation vs machine translation guidance with post-editing
- Quality checks for consistency, QA, and SEO considerations on translated copy
- Reads project-context.md when present for brand voice and product terminology
- Workflow scope covers brief, translate, and review phases
- Metadata version 1.0.1 in SKILL frontmatter
Adoption & trust: 1.1k installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need consistent, on-brand copy in multiple languages but lack a repeatable workflow, glossary, or clear rules for human versus machine translation.
Who is it for?
Indie founders and small teams expanding into new languages who already have source copy and want controlled terminology plus review gates before publishing.
Skip if: Teams that only need hreflang, routing, or TMS integration architecture without copy workflow—use localization-strategy from the same repo instead.
When should I use this skill?
User wants to translate content, create translation workflows, manage terminology, optimize translation quality, or mentions translate, localization copy, glossary, TMS, or multilingual content.
What do I get? / Deliverables
You get a structured translation brief, glossary and style guidance, QA steps, and market-specific terminology choices ready to hand off to translators or post-editors—or to pair with localization-strategy for technical
- Translation brief and workflow plan
- Glossary and per-language style guidance
- QA and consistency checklist for reviewed copy
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because solo builders most often invoke this when scaling localized content, lifecycle copy, and SEO-aware strings—not when first wiring i18n code. Content subphase matches glossary management, voice/tone per language, and QA on multilingual assets rather than hreflang or URL architecture.
Where it fits
Localize onboarding emails and help articles while keeping a shared glossary for product feature names.
Prepare market-specific terminology and tone before publishing regional landing variants.
Align UI string terminology in docs before handing strings to translators.
Translate a validation landing page with review QA before paid traffic in a new locale.
How it compares
Copy-and-workflow skill for translators and marketers, not an i18n implementation or hreflang configuration playbook.
Common Questions / FAQ
Who is translation for?
Solo builders and tiny marketing teams localizing landing pages, lifecycle emails, docs snippets, or product UI strings who need glossaries, style consistency, and human-vs-MT decisions.
When should I use translation?
Use it when you mention translate, glossary, terminology, style guide translation, TMS workflows, or multilingual SEO copy—in Grow when scaling content, at Launch when preparing regional messaging, or in Build when documenting terms before wider localization.
Is translation safe to install?
Review the Security Audits panel on this Prism page for install counts and audit status; the skill is procedural copy guidance and does not require shell or network access by default.
Workflow Chain
Then invoke: localization strategy
SKILL.md
READMESKILL.md - Translation
# Content: Translation Guides translation workflow, terminology, style, and quality for multilingual content. Covers when to use human vs machine translation, glossary and style guide creation, and SEO considerations. For i18n implementation, hreflang, and URL structure, see **localization-strategy**. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **Workflow**: Brief → translate → review - **Terminology**: Glossary creation and management - **Style guide**: Voice, tone, formatting per language - **Human vs MT**: When to use each; post-editing - **Quality**: QA, consistency, SEO - **Market-specific**: Terminology by region ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand voice, target markets, and product terminology. Identify: 1. **Content type**: Product UI, marketing copy, blog, landing page, docs 2. **Target language(s)**: Priority locales 3. **Existing assets**: Glossary, style guide, translation memory (TM) --- ## 1. Translation Workflow ### Brief → Translate → Review | Phase | Purpose | Output | |-------|---------|--------| | **Brief** | Context, audience, tone, glossary reference, style guide | Translator brief document | | **Translate** | First pass; use glossary + TM when available | Draft translation | | **Review** | Native speaker review; consistency, brand voice, SEO | Final translation | ### Translator Brief Include in every project: - **Context**: What the content is for (landing page, product UI, blog) - **Audience**: Target market, user persona - **Tone**: Formal, casual, technical - **Glossary**: Link or attach; mandatory terms - **Style guide**: Reference or key rules - **Constraints**: Character limits (UI), SEO keywords to include naturally ### Content-Type Workflow | Content Type | Approach | Notes | |--------------|----------|-------| | **Product UI** | Glossary-critical; short strings; consistency | Use TM; avoid machine translation | | **Marketing copy** | Brand voice; cultural adaptation | Human translation; see terminology | | **Blog / Article** | SEO; natural keyword placement | Re-research keywords in target language; don't translate keyword lists | | **Landing page** | Conversion-focused; CTA clarity | Human; test localized CTAs | | **Technical docs** | Precision; glossary | TM + glossary; consider MT + post-edit for high volume | --- ## 2. Glossary & Terminology ### Glossary Purpose - **Consistency**: Same term translated the same way across all content - **Brand**: Product names, feature names, approved phrasing - **Compliance**: Safety, legal, regulated terms - **Cost**: Reduces rework; accelerates review ### Glossary Structure | Field | Purpose | |-------|---------| | **Source term** | Original (e.g., English) | | **Target term** | Approved translation | | **Context** | Where it appears; usage note | | **Do not translate** | Brand names, product names (when applicable) | ### Market-Specific Terminology | Term | English | Chinese | Notes | |------|---------|---------|------| | **Generative AI** | Generative AI, GenAI | AIGC (人工智能生成内容) | Use "AIGC" for China; "Generative AI" for English | | **Influencer** | Influencer | KOL (关键意见领袖) | "KOL" common in Chinese marketing | | **User** | User | 用户 | Context-dependent | | **Dashboard** | Dashboard |