humanize-korean — Claude Code skill: what it does, how to install
The humanize-korean skill edits awkward, translation-shaped Korean and formulaic AI phrasing while leaving facts, numbers, names, and quotations intact. It works in one pass.
MIT ★ 880 updated 2026-09-03
npx skills add sangrokjung/claude-forge --skill humanize-korean -a claude-codeWhat humanize-korean does
humanize-korean scans existing Korean prose for translation patterns and machine-like phrasing, then makes targeted changes to wording and rhythm. It consults a compact rule sheet and a fuller pattern guide, then checks the result against a checklist. The response includes the edited text, an estimated change rate, a rough grade, and examples of edits.
Facts, dates, proper nouns, numbers, units, and direct quotations must remain unchanged. If edits affect more than half the text, the skill stops instead of returning a rewritten version. Long Korean text can be split into sections; writing new marketing copy, editing English, and basic spell-checking fall outside its scope.
The pass runs in the current session. If rewriting is routed through an external service, text containing client names, deal amounts, personal data, salary details, or secrets needs clearance before it is sent there.
What it helps with
- Remove translation-shaped phrasing from Korean prose
- Replace formulaic AI wording with natural Korean
- Edit style without changing facts or quotations
- Catch edits that have grown into a full rewrite
Example prompts for the agent
- Edit this Korean passage to sound natural, while keeping its facts and quotations intact.
- Remove translation-like phrasing from this section and show me the main edits.
- Check this Korean prose for formulaic AI wording without changing names or numbers.
How to install humanize-korean
1Skills CLI (Vercel)
npx skills add sangrokjung/claude-forge --skill humanize-korean -a claude-code2Manually: put the files in place
~/.claude/skills/humanize-korean/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/humanize-korean/
1Skills CLI (Vercel)
npx skills add sangrokjung/claude-forge --skill humanize-korean -a codex2Manually: put the files in place
.agents/skills/humanize-korean/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sangrokjung/claude-forge --skill humanize-korean -a cursor2Manually: put the files in place
.cursor/skills/humanize-korean/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sangrokjung/claude-forge skills/humanize-korean2Manually: put the files in place
.github/skills/humanize-korean/SKILL.md1Skills CLI (Vercel)
npx skills add sangrokjung/claude-forge --skill humanize-korean -a gemini-cli2Platform CLI
gemini skills install https://github.com/sangrokjung/claude-forge --path skills/humanize-koreanManually: put the files in place
.devin/skills/humanize-korean/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about humanize-korean
How do I install humanize-korean in Claude Code?
Run npx skills add sangrokjung/claude-forge --skill humanize-korean -a claude-code. The skill file is at ~/.claude/skills/humanize-korean/SKILL.md.
What does humanize-korean do?
It makes targeted style and rhythm edits to existing Korean prose, addressing translation-like constructions and formulaic AI phrasing. Facts, numbers, names, and quotations stay unchanged.
Can I use it for English text or spell-checking?
No. The skill is for editing existing Korean prose, not English, routine spelling checks, or drafting marketing copy from scratch.
Source text
SKILL.md · MIT
--- name: humanize-korean description: "Clean up translation-ese and AI-writing tics in Korean prose so it reads like a person wrote it — content (facts, numbers, proper nouns, quotes) stays 100% unchanged, only style and rhythm are touched. Single-pass, done in this session. Triggers — AI 티 없애줘, 번역투 고쳐줘, 한글 자연스럽게 윤문해줘, sounds like a machine translation, remove AI tells from this Korean text, make this Korean read naturally. Not for: marketing copy generation (write it clean the first time — see rules/korean-writing-quality.md), English text, plain spell-check (see korean-spell-check), or book-length manuscripts." --- # Humanize Korean — single-pass cleanup skill (한글 윤문 스킬) > **Analogy.** A proofreading desk for text that reads like it just came out of a translator — the goal is to make it read like it was written in Korean from the start. It changes **not a single fact** (proper nouns, numbers, quotes stay 100% intact) — only the style and rhythm. This is *removing translation-ese and AI idioms to improve Korean prose quality*, not "evading an AI detector." > > 비유: 번역기를 갓 거친 듯 어색한 한글을 "원래 한국어로 쓴 글"처럼 다듬는 교정 데스크. **사실은 한 글자도 안 바꾸고**(고유명사·수치·인용 100% 보존) 문체·리듬·표현만 손본다. 이것은 *번역투·AI 구문 제거 = 한글 품질 개선*이지 "AI 탐지기 우회"가 아니다. ## 0. Before you start — scope and data-surface check 1. **Routing check.** If the input is marketing copy that hasn't been written yet, don't run this skill on it — write it clean the first time per `rules/korean-writing-quality.md` instead; this skill is for cleaning up existing text. If the input is a full book manuscript, treat this as a starting point only — long-form editorial judgment belongs to a human editor or a project-specific process. 2. **Sensitive-text check (see `rules/korean-writing-quality.md` §5).** If this session or your tooling routes the actual rewrite through a model surface outside this session (a different vendor's API, a hosted service), don't send text containing client names, deal amounts, PII, salary data, or secrets through that surface unless you've explicitly cleared it for that data. When in doubt, do the cleanup pass locally in this session, or redact first. ## 1. Single-pass workflow (in this session, one pass) 1. **Read the input.** If it's long (roughly 5,000+ Korean characters), consider splitting it into logical sections and running the pass per section — don't try to hold the whole self-check in your head for a very long piece at once. 2. **Detect.** Scan the text against `references/quick-rules.md` (compact ID + prescription table) and, for anything ambiguous or worth a worked example, `reference/ai-tell-taxonomy.md` (the full pattern reference this pack ships at the repo root). 3. **Rewrite.** Fix only the spans you detected — a surgical edit, not a rewrite of the whole piece. Keep every proper noun, number, date, unit, and direct quote byte-for-byte identical. 4. **Self-check.** Run the six-item checklist in `references/quick-rules.md` before returning the result. If change rate exceeds 50%, stop and tell the user instead of shipping the rewrite — that's not a cleanup pass anymore. 5. **Return.** The cleaned text, plus: (a) a one-line status (change rate estimate, rough grade A-D per `references/quick-rules.md`), and (b) 3-6 of the most significant before → after examples so the user can see what actually changed. ## 2. Iron rules (violate any of these → roll back) 1. **Meaning is invariant.** Facts, claims, numbers, dates, proper nouns, and quotes are preserved 100%. 2. **Evidence-grounded.** Only touch spans that map to a pattern in `references/quick-rules.md` or `reference/ai-tell-taxonomy.md`. Don't edit prose just because you'd have phrased it differently. 3. **Genre and register stay put.** A column doesn't become an essay. A report doesn't slide into blog voice. Formal register stays formal. 4. **No over-polish.** A change rate above 30% is a warning sign; above 50%, stop and reconsider — you're rewriting, not cleaning up. ## 3. Forbidden framing (CRITICAL) Never describe this skill's purpose as "evading an AI detector," "detector bypass," or "hiding that this was AI-written." The actual purpose is *improving awkward, translation-ese Korean into natural Korean* — a legitimate prose-quality goal, independent of who or what wrote the draft. ## 4. Deeper cleanup (out of scope for this skill) For long-form (8,000+ characters), high-stakes, or precision-critical text, a heavier multi-pass review (separate detection, rewrite, and independent fidelity/naturalness review stages) does a more thorough job than this single-pass skill. That's a project-specific setup this skill doesn't ship — if you need it, build a multi-stage review around `reference/ai-tell-taxonomy.md` as the shared pattern reference. ## 5. References - Quality standard this cleanup targets: `rules/korean-writing-quality.md` - Full pattern reference (10 categories A-J, severity tiers, before/after examples): `reference/ai-tell-taxonomy.md` - Compact cheat sheet for this single pass: `references/quick-rules.md` - Adjacent utility skills: `skills/korean-character-count` (deterministic character/byte counting), `skills/korean-spell-check` (rule-based spell/grammar check via a public checker)
© sangrokjung · MIT · sangrokjung/claude-forge