Humanize Korean
Clean up translation-ese and AI-writing tics in Korean prose so it reads like a person...
Install
npx skills add sangrokjung/claude-forge --skill humanize-korean -g -a claude-code -y- Repository
- sangrokjung/claude-forge868
- Category
- Marketing
- Updated
- 2mo ago
- License
- MIT
- Context cost
- Lightabout 1,148 tokens
- Runs scripts
- No, instructions only
What it does
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
- 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.mdinstead; 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. - 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.
