Prepare ecommerce translation that preserves product meaning and reads naturally for the target audience. Give your assistant the source text, target locale, approved terminology and placement limits; this Skill builds a translation brief, creates localized drafts and organizes language checks for product pages, store messages or marketing content.
Translation work becomes harder when the same product name, promise or instruction is expressed differently across pages. This Skill separates the brief, translation and review stages, keeping terminology, audience and brand voice visible throughout the process.
Use it for a defined set of customer-facing text rather than an unspecified request to translate the whole business. The output can include a glossary, localized copy and a QA workflow. Website language routing, hreflang and translation-management integrations are separate implementation tasks.
A translation brief captures locale, audience, tone and character constraints before drafting begins. A shared glossary then gives product names and important terms a consistent treatment across the material you are translating.
Review is a distinct step, with special attention to terminology that affects product use or customer expectations. The workflow makes it easier to hand localized drafts to a native reviewer and record the corrections that should carry into later pages.
Source text, target locale, audience, glossary, voice guide, character limits, and review owner.
Use a compatible agent that can discover the installed Skill and read its supporting files. Any external service or creative runtime must be configured separately.
It does not connect a translation-management system or implement hreflang and URL routing. Native review and sensitive terminology checks remain necessary.
Send this request to the OpenClaw agent that will use the Skill. It installs the named publisher’s release and checks the workspace configuration.
Install @kostja94/translation version 1.0.1 in my active OpenClaw workspace. Use the original ClawHub release, not a same-named substitute. First check whether it is already installed; do not force-overwrite local changes. Run:
openclaw skills install @kostja94/translation --version 1.0.1
openclaw skills info translation
Read SKILL.md and all setup references, identify required tools, dependencies and credentials, and report the actual version, path and readiness. Start a new session if needed. Do not describe package installation as a successful business-task test.This is the unchanged source SKILL.md for the reviewed version. Install the complete package to retain referenced scripts, assets, and instructions. Starter prompts below are EcomAgentTools examples.
---
name: translation
description: When the user wants to translate content, create translation workflows, manage terminology, or optimize translation quality. Also use when the user mentions "translate," "translation," "localization copy," "glossary," "terminology," "style guide translation," "machine translation," "human translation," "TMS," or "multilingual content." For strategy, use localization-strategy.
metadata:
version: 1.0.1
---
# 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 | 控制台, 仪表盘 | Choose one; document in glossary |
**Principle**: Don't translate terminology lists; research how target market searches and speaks. See **keyword-research** for multi-language keyword research.
---
## 3. Style Guide (Translation)
### Elements to Define
| Element | Purpose |
|---------|---------|
| **Voice** | Brand personality; formal vs casual |
| **Tone** | Varies by content type (support = helpful; marketing = persuasive) |
| **Register** | Formal (您) vs informal (你) in languages that distinguish |
| **Punctuation** | Quotation marks, spacing (e.g., no space before colon in French) |
| **Formatting** | Dates, numbers, units; locale-specific |
| **Forbidden** | Terms or phrases to avoid |
### Per-Language Considerations
- **Chinese**: Simplified vs Traditional; measure word usage
- **German**: Formal (Sie) vs informal (du); compound nouns
- **Japanese**: Honorifics; keigo for formal contexts
- **Arabic**: RTL; formal vs dialect
---
## 4. Human vs Machine Translation
### When to Use Human Translation
| Scenario | Reason |
|----------|--------|
| **Product UI** | Terminology, UX clarity, brand |
| **Marketing copy** | Persuasion, cultural nuance, CTAs |
| **Landing pages** | Conversion; tested copy |
| **Legal, compliance** | Accuracy, liability |
| **Brand-critical** | Taglines, campaign copy |
### When Machine Translation (MT) May Be Acceptable
| Scenario | Condition |
|----------|-----------|
| **High-volume, low-stakes** | Internal docs, user-generated content |
| **Draft / triage** | MT + human post-edit (MTPE) |
| **Real-time** | Chat, support; with disclaimer |
### Avoid
- **Raw MT for product/marketing**: Terminology errors, cultural misfires, poor SEO
- **MT without post-edit** for customer-facing content
- **Translating keyword lists** instead of re-researching in target language
---
## 5. Translation Memory (TM) & TMS
### Translation Memory
- **What**: Stores approved source↔target sentence pairs
- **Benefit**: Consistency; reuse; lower cost per word; faster turnaround
- **Best practice**: Maintain TM; clean duplicates; align with glossary
### Translation Management System (TMS)
- **Use for**: Centralized workflow; glossary + TM integration; vendor management
- **When**: Multiple languages; ongoing translation; team collaboration
---
## 6. Quality & SEO
### Quality Checklist
- [ ] Glossary terms used correctly
- [ ] Style guide followed
- [ ] No untranslated strings
- [ ] Numbers, dates, units localized
- [ ] Character limits respected (UI)
- [ ] Native speaker review completed
### SEO for Translated Content
- **Keywords**: Re-research in target language; don't translate from source
- **Metadata**: Title, description translated; see **title-tag**, **meta-description**
- **Hreflang**: Technical implementation in **localization-strategy**; translation produces the content
- **Thin content**: Avoid publishing many low-quality translated pages at once; can trigger penalties. See **localization-strategy** Multilingual Risks.
---
## 7. Integration with Localization
| Topic | Skill |
|-------|-------|
| **i18n implementation** | localization-strategy |
| **URL structure, hreflang** | localization-strategy |
| **Translation workflow, glossary, style** | This skill (translation) |
| **Keyword research by market** | keyword-research; localization-strategy |
When adding a new locale: create glossary, style guide, then translate. See **localization-strategy** for technical checklist (hreflang, sitemap, metadata).
---
## Output Format
- **Translator brief** (context, audience, glossary, style)
- **Glossary** additions or updates
- **Style guide** notes for target language
- **Human vs MT** recommendation
- **Quality** checklist
## Related Skills
### Strategy & Technical
- **localization-strategy**: i18n, hreflang, URL structure, pricing by market; translation produces content for localized pages
- **content-strategy**: Multilingual content planning; avoid thin translations
- **content-marketing**: Content types and formats; translation as one channel adaptation
### SEO & Content
- **keyword-research**: Multi-language keyword research; don't translate keyword lists
- **page-metadata**: Hreflang implementation
- **title-tag, meta-description**: Translate metadata per locale
- **copywriting**: Source copy to translate; brand voice
- **image-optimization**: Localize image filenames for translated pages
### Pages
- **article-page-generator**: Article structure; translate with SEO in mind
- **landing-page-generator**: Landing page copy; human translation for conversion
Starter prompts for the main use cases—copy and use them directly.
Create a product-copy translation brief Use for: Create a product-copy translation brief. Prepare: Source text, target locale, audience, glossary, voice guide, character limits, and review owner.
Use the installed translation Skill. Task: Create a product-copy translation brief. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. It does not connect a translation-management system or implement hreflang and URL routing. Native review and sensitive terminology checks remain necessary.[INPUT][CONSTRAINTS]Build a bilingual terminology glossary Use for: Build a bilingual terminology glossary. Prepare: Source text, target locale, audience, glossary, voice guide, character limits, and review owner.
Use the installed translation Skill. Task: Build a bilingual terminology glossary. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. It does not connect a translation-management system or implement hreflang and URL routing. Native review and sensitive terminology checks remain necessary.[INPUT][CONSTRAINTS]Review localized copy against tone and character limits Use for: Review localized copy against tone and character limits. Prepare: Source text, target locale, audience, glossary, voice guide, character limits, and review owner.
Use the installed translation Skill. Task: Review localized copy against tone and character limits. Inputs: [INPUT]. Constraints: [CONSTRAINTS]. Check missing information first. Produce a reviewable result with evidence, assumptions, and next steps. It does not connect a translation-management system or implement hreflang and URL routing. Native review and sensitive terminology checks remain necessary.[INPUT][CONSTRAINTS]English product copy and an A100 support reply must retain the SKU, USD amounts, capacity, business-day timings and refund approval without changing store policy.
Case input files: business-inputs.zip
Use the translation Skill.
Translate the supplied English product copy and customer-service reply into natural Simplified Chinese. Establish a compact glossary and tone guide, preserve SKU, currency, measurements, business-day timings and refund conditions, and deliver the complete translations with a factual consistency checklist for review.
The attached business materials are:
- inputs/brief.json
- inputs/source-en.txt
Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.The primary file produced by this prompt is shown below in its original language.
Audience: US-based Simplified Chinese readers. Delivery geography and prices remain US/USD; this is not a China-market launch. The two complete customer-facing passages follow.
SKU：HM-BLUE-001。这款不锈钢保温杯容量为 500 ml，售价为 24.00 美元（USD）。重量为 0.35 kg，尺寸为 9 × 9 × 19 cm。仅可手洗，不可放入微波炉。
美国境内订单将在 2 个工作日内发货。发货后，配送通常需要 3–5 个工作日。订单金额低于 50.00 美元（USD）时，运费为 5.00 美元（USD）；订单金额达到 50.00 美元（USD）及以上免运费。不提供国际配送。
我们接受自送达之日起 30 天内的未使用商品退货。最终退款须经商家批准。
您好，感谢您就订单 A100 联系 HarborMug。您的订单于 2026 年 10 月 20 日送达，您于 2026 年 11 月 3 日申请退货。您尚未拆封的商品仍在我们规定的 30 天未使用商品退货期限内。Mia 会协助您办理后续手续；需要升级处理的问题由 Alex 负责。最终退款仍须经商家批准。
| English | Simplified Chinese | Rule |
|---|---|---|
| insulated mug | 保温杯 | Do not add an hours-of-insulation claim |
| business days | 工作日 | Never substitute calendar days |
| dispatch | 发货 | Separate from delivery / 送达 |
| unused returns | 未使用商品退货 | Keep the condition and 30-day window |
| merchant approval | 商家批准 | Eligibility is not a refund guarantee |
| USD | 美元（USD） | No currency conversion |
| HarborMug / HM-BLUE-001 / A100 | unchanged | Brand and identifiers remain exact |
Use 您 for support; product copy is factual and direct. Use Chinese punctuation, retain decimal precision, and keep spaces between numbers and Latin units. Mia and Alex are fictional role names supplied in the exercise. No translation memory was provided, so the glossary above is the reusable asset for the next revision.
The translation preserves 500 ml, $24.00 USD, 0.35 kg, 9 × 9 × 19 cm, hand-washing and the microwave prohibition. It preserves the two-business-day dispatch window separately from three-to-five-business-day delivery, the below-$50 fee and equality at the free-shipping boundary, US-only coverage, unused condition, 30 days and merchant refund approval.
The delivery and request dates are 14 calendar days apart; the customer reply correctly says the unopened item is within the eligibility window. It does not promise that a refund has been approved. No exchange rate, China shipping, new return postage rule or SEO demand claim has been added.
This execution includes an AI translation and a separate factual consistency pass. An independent human native-speaker review was not performed and is not represented as completed. Before publishing regulated or brand-critical text, the merchant's reviewer can use the glossary and source alongside this draft.
Merchant business data is synthetic. Website observations, when present, come from the public URLs listed in the report.
It does not connect a translation-management system or implement hreflang and URL routing. Native review and sensitive terminology checks remain necessary.
Source and package files reviewed: ClawHub 1.0.1. This is a static review, not an installation or business-outcome test.
Use authorized inputs and keep secrets out of prompts. Review customer-facing claims, calculations, code changes, and any proposed external action before applying them.
Prepare translation briefs, glossaries, localized drafts, and language QA workflows. The workflow separates briefing, translation, and review and treats terminology and audience context explicitly.
Choose the method for your agent and install the complete package, not just the displayed SKILL.md. Source text, target locale, audience, glossary, voice guide, character limits, and review owner. Start a new agent session and explicitly ask to use translation. Try one use case below with a small sample and review the output.
Create a product-copy translation brief; Build a bilingual terminology glossary; Review localized copy against tone and character limits
It does not connect a translation-management system or implement hreflang and URL routing. Native review and sensitive terminology checks remain necessary.
Source and package files reviewed: ClawHub 1.0.1. This is a static review, not an installation or business-outcome test.
Source and package files reviewed: ClawHub 1.0.1. This is a static review, not an installation or business-outcome test.
Source and package files reviewed: ClawHub 1.0.1. This is a static review, not an installation or business-outcome test.
No reviews yet.