Translate or revise localized UI strings and prose while preserving meaning, terminology, placeholders, and structure.
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/oma-translation/SKILL.mdTranslate, review, or adapt multilingual content faithfully and naturally while preserving the parts that must remain exact: placeholders, code, links, formatting, terminology, and file structure.
resources/lang/{code}.md, if one exists.resources/translation-rubric.md for substantive content or review.resources/style-skills.md.code_intelligence capability when available for code-context navigation; native
search/read for local source and sibling translations, and when the capability is unavailable
or times out.| Failure | Recovery |
|---|---|
| Missing target context | Use the source register and state the assumption, unless the ambiguity changes meaning |
| Conflicting literal wording and project convention | Follow the established target convention and explain a material difference |
| Placeholder or structure mismatch | Revise before emitting or applying a patch |
| Unclear cultural reference | Add a concise note only when the target audience needs it |
| Selected external style skill unavailable | Use the in-repo fallback in resources/style-skills.md, complete supported translation checks, and report that the external style pass did not run; do not substitute another language's style skill or claim it ran |
Resolve the BCP 47 primary subtag and load one matching profile when present:
| Target | Profile |
|---|---|
| Korean | resources/lang/ko.md |
| Japanese | resources/lang/ja.md |
| Chinese | resources/lang/zh.md; resolve the declared variant |
| English | resources/lang/en.md |
| Other | no profile; use shared guidance |
Profiles define typography, register, and target-language checks. Shared guidance explains common
risks. A profile wins if they conflict. Add a new profile from resources/lang/_template.md only
when the task is to extend this skill.
translation_voice from .agents/oma-config.yaml only as a rhythm/formality preference:
formal, balanced (default), or interpreter. It never overrides meaning or target norms.Always check:
For substantive content and review mode, also check the rubric: naturalness, accuracy, register, terminology, and technical integrity. Apply the selected target-language style route while preserving intentional source style and content.
Review from evidence, not from an expectation that every draft is machine-translated. Record zero findings when no material defect is confirmed. Separate:
Do not rewrite a sound translation merely to produce findings.
For batches, read the complete set first, translate values only, and maintain one terminology and register decision. Verify placeholders and key structure across the set.
For diff-sync, map each source hunk by heading and surrounding context. Touch only the affected target section; leave unrelated text byte-identical. State updated sections, skipped cosmetic hunks, and material terminology decisions.
For a single text, present the translation and brief notes for ambiguities or adaptations. For files, preserve the input format and modify only requested values. For review, show the original, the suggested revision only when warranted, and the evidence for each finding.
en (including regional variants): load resources/style-skills.md and resolve humanizer.ko (including regional variants): load that resource and resolve humanize-korean.../_shared/core/anti-ai-prose.md with
resources/anti-ai-patterns.md and the target profile.
When a prose-style route is selected, record it with subject
translation.route-selection per ../_shared/runtime/route-selection.md
(style skill, target subtag that selected it, and translation_voice).Changes locale or docs files only when the user asked for file changes; otherwise the result is translated text or review findings in the response. May retrieve a missing selected style-skill bundle from upstream over the network; installed or cached instructions are reused. Upstream intermediate files stay in a writable scratch workspace.
resources/translation-rubric.md (load for substantive content or review)resources/style-skills.md (English or Korean substantive prose)../_shared/core/anti-ai-prose.md (other target languages, with translation exceptions when prose style needs review)resources/anti-ai-patterns.md (other target languages, with common diagnostics when prose style needs review)resources/lang/{ko,ja,zh,en}.md (load one matching profile)resources/lang/_template.md (only when adding a profile)../_shared/core/context-loading.md../_shared/core/quality-principles.mdfirst-fluke/oh-my-agent
2bd468c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.