k-humanizer
Writes, localizes, and edits Korean for Korean customers so Korean readers find it natural. Helps writers, including non-native speakers, translate English sales emails, ads, landing and product pages, support replies, service notices, or app UI and notifications into Korean, check a Korean translation against its English source, or fix Korean that sounds translated, stiff, or AI-written. Also covers documents, messages, email, public posts, code review, and dialogue. Routes resumes and job applications to k-humanizer-resume. Preserves meaning, commercial terms, placeholders, and the writer's voice.
evergreentree97 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add evergreentree97/K-Humanizer --skill k-humanizerAbout this skill
name: k-humanizer description: Writes, localizes, and edits Korean for Korean customers so Korean readers find it natural. Helps writers, including non-native speakers, translate English sales emails, ads, landing and product pages, support replies, service notices, or app UI and notifications into Korean, check a Korean translation against its English source, or fix Korean that sounds translated, stiff, or AI-written. Also covers documents, messages, email, public posts, code review, and dialogue. Routes resumes and job applications to k-humanizer-resume. Preserves meaning, commercial terms, placeholders, and the writer's voice.
K-Humanizer
Produce Korean that a Korean reader would accept as written for them, without changing what the text says. Many users cannot fully check the Korean themselves, so accuracy comes before polish. AI detector scores are outside the goal.
1. Identify the input mode
| Input | Task | Scope |
|---|---|---|
| Korean only | Edit the Korean | Keep the voice and structure, and keep a coherent register. Change the register only when the user asks or the supplied context clearly shows a channel or brand mismatch. Read the surrounding text for context, but edit only the passage the request covers, and only where it does not work. |
| English source with a Korean draft | Check the Korean against the source text, fix drift, then fix awkward Korean | Use the text the user names as the source. If they name none, use the English. Keep Korean wording that is accurate and natural. |
| English only, Korean requested | Translate and localize | Build each sentence in Korean order. Merge, split, or reorder sentences when Korean reads better, keeping every fact and condition. Do not aim for word-by-word correspondence or minimal change from a machine translation. |
When the Korean draft and the English disagree on a price, date, limit, policy, or promise, do not silently pick one. Decide from what the user and the context actually say:
- If the user names one version as approved, current, or authoritative, follow it without asking again.
- If the Korean clearly mistranslates the English, such as a dropped exclusion or a softened "only", and nothing marks the Korean as authoritative, fix it and say so in one line.
- If it is unclear which version governs and the choice would change commercial terms, ask one focused question, or keep the Korean and mark the clause as unresolved. Do not present that clause as verified, paste-ready copy.
A won price, a VAT note, or a Korea-specific policy does not by itself show that the Korean was approved. Do not infer approval or local policy from assumptions about the Korean market.
Translating Korean into English is a different task. Do it when asked, keep it faithful, and do not apply this skill's Korean style guidance to the English.
2. Read the situation
Work out from the request, the text, and any existing Korean copy:
- Audience: consumers, business customers, partners, or an internal team.
- Channel: sales email, ad, landing or product page, app UI or notification, support reply, formal notice, or a native-writing genre such as a report or chat message.
- Brand register: speech level (합쇼체, 해요체, or short labels) and how warm or restrained the brand sounds.
- Purpose: purchase, information, inquiry, apology, or guidance, and what the reader should do next.
Infer defaults from context. Professional does not mean stiff, and natural does not mean casual. Unless the context points elsewhere:
- B2B email, contracts, and formal notices use 합쇼체.
- Consumer apps and many consumer brands use 해요체 in sentences.
- Buttons, headlines, banners, and spec tables can use noun phrases.
- Existing Korean strings, brand samples, or style guides override these defaults. Defaults fill gaps; they do not justify changing Korean that is already coherent.
When the brand voice or another preference is missing, use these defaults and draft without noting them. When a material fact is missing or unclear, such as a price, period, or what a button actually does, still translate everything the source supports. Identify the exact field the requested output needs, and leave only that field as a neutral placeholder or a plainly unresolved field. Match every question, including a parenthetical sub-question, to that field. Drop related questions that would matter only if the requested content grew, such as hypothetical variants, terms the source never raised, or how the product might be built. When a task has several independently missing facts, ask about each of them.
3. Write or edit
Read for meaning first: actor, action, reason, conditions, and outcome. Then look for what a Korean reader would notice:
- Translationese and English word order
- Wording more formal or ceremonial than the channel needs
- English idioms Korean readers do not use
- Pronouns and subjects Korean leaves out, such as
당신,그것, or우리는; omit a subject only when the reader can still tell who acts, and restate the actor when it changes - Long nominalized sentences
- Speech levels that mix without reason or do not fit the brand
- Calls to action that read like translated commands
- Repeated AI phrasing
Judge each sentence in its paragraph, for its reader and channel. No word is
banned: 통해, 제공, 진행, and 관련하여 are ordinary Korean when they fit.
Do not shorten to meet a quota; a shorter or more casual synonym is not a fix.
Read connected prose as a paragraph and keep the wording that carries cause,
contrast, sequence, or reference. Keep field terms readers
actually use, including English terms and loanwords, and explain an unfamiliar
term when the reader needs it. Use patterns.md to
diagnose phrasing and rhythm.
When the source gives no action, result, or reason, keep the claim narrow or flag the gap. Use the writer's own wording or supplied samples for tone, never as a source of facts.
Read the complete source ↗