<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: evergreenRok</title>
    <description>The latest articles on DEV Community by evergreenRok (@evergreen_rokd).</description>
    <link>https://dev.to/evergreen_rokd</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4090762%2Fa556e275-cd0f-45e8-846f-6d7e0b2c6772.png</url>
      <title>DEV Community: evergreenRok</title>
      <link>https://dev.to/evergreen_rokd</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/evergreen_rokd"/>
    <language>en</language>
    <item>
      <title>I built K-Humanizer from 7,500+ edits across 120,000 Korean responses</title>
      <dc:creator>evergreenRok</dc:creator>
      <pubDate>Sun, 23 Aug 2026 12:14:07 +0000</pubDate>
      <link>https://dev.to/evergreen_rokd/i-built-k-humanizer-an-open-source-agent-skill-for-natural-korean-writing-b0d</link>
      <guid>https://dev.to/evergreen_rokd/i-built-k-humanizer-an-open-source-agent-skill-for-natural-korean-writing-b0d</guid>
      <description>&lt;p&gt;AI-written Korean can be grammatically correct and still feel awkward. English-shaped word order lingers, the tone is more formal than the situation calls for, and abstract wording makes it hard to tell what actually happened.&lt;/p&gt;

&lt;p&gt;I reviewed more than 120,000 Korean responses and made over 7,500 edits. The same phrase could sound natural in one context and awkward in another. That work taught me what to change, when to leave a sentence alone, and how to preserve the writer's meaning.&lt;/p&gt;

&lt;p&gt;I put that experience into &lt;a href="https://github.com/evergreentree97/K-Humanizer" rel="noopener noreferrer"&gt;K-Humanizer&lt;/a&gt;, an open-source Agent Skill for Cursor, Claude, and Codex. It helps AI drafts sound closer to the way people actually write in Korean while keeping facts, numbers, names, uncertainty, and domain terms unchanged.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;한국어 글을 자연스럽게 쓰고 싶거나 AI 초안을 평소 쓰는 문장에 가깝게 다듬고 싶은 분에게 추천합니다.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  A small example
&lt;/h2&gt;

&lt;p&gt;Before:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;고객 문의 분류 체계 고도화를 통해 주간 평균 처리 시간을 18시간에서 11시간으로 크게 개선했습니다.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;After:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;고객 문의 분류 기준을 정리해 주간 평균 처리 시간을 18시간에서 11시간으로 줄였습니다.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Both sentences make the same factual claim. The second tells the reader what changed without the abstract wording.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the skill checks
&lt;/h2&gt;

&lt;p&gt;K-Humanizer looks for English-like word order, unnecessary passive voice, long noun-heavy phrasing, repeated connective words, and formality that does not fit the channel. It also distinguishes between a resume, email, chat message, product screen, and everyday writing.&lt;/p&gt;

&lt;p&gt;Each change depends on context. For example, the skill does not replace every instance of "~를 통해". It keeps the phrase when it describes a real path or intermediary and changes it only when it makes the sentence longer without adding meaning.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it protects
&lt;/h2&gt;

&lt;p&gt;The skill is designed to keep:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;facts and numbers&lt;/li&gt;
&lt;li&gt;names and sources&lt;/li&gt;
&lt;li&gt;professional terminology&lt;/li&gt;
&lt;li&gt;the original level of certainty&lt;/li&gt;
&lt;li&gt;sentences that already sound natural&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It does not promise to bypass AI detectors. It also does not invent resume achievements or make uncertain claims sound definite.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx skills add evergreentree97/K-Humanizer &lt;span class="nt"&gt;--skill&lt;/span&gt; k-humanizer &lt;span class="nt"&gt;--full-depth&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then give the skill the purpose of the text and its intended reader:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Use $k-humanizer to revise the Korean text below for a product notice.
Keep facts, numbers, names, and product terms unchanged.
Fix only translation-like phrasing and unnecessary formality.

[Your text]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Validation so far
&lt;/h2&gt;

&lt;p&gt;The 7,500+ edits and the public validation set serve different purposes. The edits informed how the skill handles context. The repository's public validation set contains 200 synthetic examples across resumes, everyday writing, chat, email, documents, product copy, dialogue, and code review. No real resumes, private messages, customer data, or internal company text are included.&lt;/p&gt;

&lt;p&gt;The current public report checks dataset structure, domain distribution, duplicate IDs, required fields, and repository hygiene. It does not claim a naturalness score yet. A separate manual evaluation for naturalness and meaning preservation is planned.&lt;/p&gt;

&lt;p&gt;The repository is MIT licensed. If you find a Korean sentence that still sounds translated, a synthetic before-and-after example would be useful. Please do not submit real resumes, private messages, customer data, or internal company text.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/evergreentree97/K-Humanizer" rel="noopener noreferrer"&gt;https://github.com/evergreentree97/K-Humanizer&lt;/a&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>opensource</category>
      <category>ai</category>
      <category>agents</category>
    </item>
  </channel>
</rss>
