Translation

This one bridges the gap between "we need this in five languages" and actually shipping quality translations. It walks you through the full workflow from translator briefs to QA, tells you when to use human translation versus machine (product UI and marketing copy get humans, high-volume docs might get MT plus post-editing), and includes practical stuff like glossary structure and market-specific terminology examples. The Chinese market terminology table alone is worth it. Pairs with localization-strategy for the technical implementation side like hreflang, but this handles the actual translation work, terminology management, and style guides per language. Useful if you're scaling beyond Google Translate and need a repeatable process.

skills.sh installs: 2.4K
GitHub stars: 1.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add kostja94/marketing-skills --skill translation --agent claude-code

Installs into .claude/skills of the current project.

Files

Translation

Own the language-production lifecycle. Deliver natural, accurate target-language content without changing product facts, inventing market claims, or treating translated words as proof that a locale is ready to launch.

Boundaries

This skill owns translation, transcreation, terminology, style, linguistic review, and keeping translations current.
localization-strategy owns locale selection, page coverage, URL architecture, routing, rollout, and release verification.
keyword-research owns target-market queries. Never translate a source keyword list and call it localized research.
Project positioning, feature availability, legal facts, and approved terminology remain in their project SSOTs.