Before sending docs for translation into other languages.
When NOT to use
Do not use before docs are final. Use only on published or near-published content.
Instructions
Identify translatable strings (headings, body text, examples, alerts).
Mark strings with context for translators:
Section name (e.g., "API Reference: Parameters")
Purpose (e.g., "User instruction" vs. "Code comment")
Special handling (e.g., "keep as-is" for variable names)
Extract glossary:
Product-specific terms (should not be translated)
Technical terms (may need regional variants)
Common phrases (standardize translation across docs)
Flag untranslatable elements (code blocks, URLs, file paths).
Return translatable text file + context guide for translators.
Identify languages and regional variants (e.g., en-US vs. en-GB).
Example
Input: "How to set up webhooks" guide
Output:
# Localization Prep: How to Set Up Webhooks
## Translatable Strings
### Section: Getting Started
[1] "Webhooks allow your application to receive real-time event notifications."
Context: Introductory sentence; explain what webhooks are
Variant: US English; formal tone
[2] "You'll need an active account and API credentials to proceed."
Context: Prerequisites; list requirements
Variant: US English; formal tone
### Section: Step 1 — Create an Endpoint
[3] "Click the Webhooks section in your dashboard."
Context: User instruction; action-oriented
Variant: US English; imperative voice
## Glossary (Do Not Translate)
- Webhook (technical term; keep as "webhook")
- Payload (keep as "payload")
- Event (context: webhook events; consider regional term if needed)
- Dashboard (product term; keep as "dashboard")
## Code & Untranslatable
```bash
curl -X POST https://api.example.com/webhooks
→ Keep as-is; no translation needed
Languages to Translate
French (fr_FR)
German (de_DE)
Spanish (es_ES)
Dutch (nl_NL)
Translator Checklist
Maintain code block integrity (no line breaks in code)
Preserve heading hierarchy (H1, H2, etc.)
Keep URLs unchanged
Preserve backticks for code references
Use glossary for consistent terminology
1---2name: localization-prep3description: Localization Prep4metadata:5 source: https://skillmd.com/skills/uitbreidenos/localization-prep6---7# Localization Prep89## When to activate10Before sending docs for translation into other languages.1112## When NOT to use13Do not use before docs are final. Use only on published or near-published content.1415## Instructions16171. Identify translatable strings (headings, body text, examples, alerts).182. Mark strings with context for translators:19 - Section name (e.g., "API Reference: Parameters")20 - Purpose (e.g., "User instruction" vs. "Code comment")21 - Special handling (e.g., "keep as-is" for variable names)223. Extract glossary:23 - Product-specific terms (should not be translated)24 - Technical terms (may need regional variants)25 - Common phrases (standardize translation across docs)264. Flag untranslatable elements (code blocks, URLs, file paths).275. Return translatable text file + context guide for translators.286. Identify languages and regional variants (e.g., en-US vs. en-GB).2930## Example3132**Input:** "How to set up webhooks" guide3334**Output:**35```36# Localization Prep: How to Set Up Webhooks3738## Translatable Strings3940### Section: Getting Started41[1] "Webhooks allow your application to receive real-time event notifications."42Context: Introductory sentence; explain what webhooks are43Variant: US English; formal tone4445[2] "You'll need an active account and API credentials to proceed."46Context: Prerequisites; list requirements47Variant: US English; formal tone4849### Section: Step 1 — Create an Endpoint50[3] "Click the Webhooks section in your dashboard."51Context: User instruction; action-oriented52Variant: US English; imperative voice5354## Glossary (Do Not Translate)55- Webhook (technical term; keep as "webhook")56- Payload (keep as "payload")57- Event (context: webhook events; consider regional term if needed)58- Dashboard (product term; keep as "dashboard")5960## Code & Untranslatable61```bash62curl -X POST https://api.example.com/webhooks63```64→ Keep as-is; no translation needed6566## Languages to Translate67- French (fr_FR)68- German (de_DE)69- Spanish (es_ES)70- Dutch (nl_NL)7172## Translator Checklist73- [ ] Maintain code block integrity (no line breaks in code)74- [ ] Preserve heading hierarchy (H1, H2, etc.)75- [ ] Keep URLs unchanged76- [ ] Preserve backticks for code references77- [ ] Use glossary for consistent terminology78```
Run npx get-skill add uitbreidenos/localization-prep in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Localization Prep It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
UitbreidenOS (@uitbreidenos) published this skill. Their other Agent Skills are listed on their SkillMD profile.