[omh] Make a product or content release locale-ready with terminology, cultural-fit, and quality-review guidance.
SkillScore91Maintained
Automatic
◆Translation & Localization pack
Last verified 8/19/2026
What it changes
Passed 20 of 22 test cases with the skill, and 15 of 22 without it.
Without skill68%
With skill91%
Checks it passed that the model alone missed
Flags placeholder mutation as a high-severity functional issue in the issue matrix
Assigns clear review ownership or action roles for each flagged issue in the matrix
Structures findings into an issue matrix categorizing severity level, context, and review ownership
and 2 more in the full report
5 fixed15 passed either way2 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+66%
Agent turns
0%
Response time
0%
Model gemini-3.6-flashMeasured 8/19/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Please perform a localization review for our Simplified Chinese (zh-CN) cart and payment confirmation screens, targeting urban mobile shoppers. We have 20 strings ready for context and terminology evaluation.
What was checked, without and with the skill
Checked
Without skill
With skill
Outputs a source version brief, glossary choices, issue matrix, and locale QA criteria tailored to zh-CN
Missed
Passed
case-22 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md113 linessingle file
Localization Review
This is a Hermes-native localization-review workflow skill.
Why This Exists
localization-review makes terminology, context, cultural fit, and locale QA reviewable without treating a drafted translation as a published or visually validated release.
Do Not Use When
The request is a short sentence or word translation or rewrite with no product or locale QA context; answer directly or use content-operator.
The user needs fresh rendered UI evidence, clipping checks, or a visual PASS/REVISE/BLOCK verdict; use visual-qa.
The user asks to edit locale files, push a translation-management-system job, publish strings, or configure localization settings; use workspace-file-operator or connector-operator with explicit target and authority.
The request asks for a regulatory or contractual conclusion about translated legal text; use legal-compliance-review.
Examples
Good example:
Prompt: Review our Korean checkout strings for terminology consistency, cultural fit, and context gaps before launch.
Expected behavior: Prepare the locale and source-version brief, glossary choices, issue matrix, and locale QA criteria.
Why: The product-release context needs localization review beyond a one-off translation.
Bad example:
Prompt: Translate 'Your trial ends tomorrow' into Korean.
Expected behavior: Answer directly or route to content-operator, not localization-review.
Why: A one-off sentence has no product locale QA or release-review objective.
Completion Checklist
Findings or no-issue results are grounded in concrete file, artifact, command, or source evidence.
Open questions, residual risk, and missing verification are named.
Fixes or follow-up work are separate handoffs unless the user explicitly asked to implement them.
Recovery Notes
If the reviewed target is missing, inspect the requested artifact or ask one target question.
If independent verification is unavailable, report the gap and avoid an approval-style claim.