agentleFS
cwinvestmentscwinvestments/memstack/skills/humanize/SKILL.md

humanize

Skill425 starsChanged 5 months agoMITView on GitHub

Use when the user says 'humanize', 'clean up writing', 'make it sound natural', or wants text to not sound AI-generated.

74 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use humanize-redo, humanize-korean and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dawn840705Skill

    humanize-redo

    가장 최근 윤문 결과를 2차로 다시 다듬는다 — 특정 카테고리·문단·강도 조정도 가능. humanize-korean 의 윤문 콜을 기존 run_id 에 재실행해 잔존 finding 을 처리한다. 트리거 — "$humanize-redo". **명시적 슬래시 호출 전용** — 자연어 후속 요청은 `humanize-korean` 오케스트레이터가 받는다.

    Also in 5 projects that use this

  • mskim8717Skill

    humanize-korean

    AI(ChatGPT·Claude·Gemini 등)가 쓴 한글 텍스트를 "사람이 쓴 글처럼" 윤문해주는 오케스트레이터 스킬. 번역투·영어 인용 과다·기계적 병렬·관용구·피동태 남용·접속사 남발·리듬 균일성·이모지/불릿 과다 등 10대 카테고리 40+ AI 티 패턴을 탐지·분류해 내용은 한 글자도 건드리지 않고 문체·리듬·표현만 자연스러운 한국어로 재작성한다. 트리거 — "AI 티 없애줘", "AI 같은 글 자연스럽게", "GPT/ChatGPT 문체", "AI 번역투 고쳐", "사람이 쓴 것처럼 윤문", "AI 윤문", "ChatGPT 티 제거", "한글 AI 탐지·윤문", "AI 글 사람처럼", "번역투 제거", "영어 인용 많은 글 윤문", "AI 글 티 안 나게", "휴머나이저", "humanize Korean", "AI detector bypass 한글". 후속 작업 — "특정 카테고리만 다시", "윤문 강도 조정", "장르 바꿔서", "이 문단만", "2차 윤문" 도 모두 이 스킬. 단순 맞춤법·오탈자 교정은 직접 처리, 번역은 번역 스킬, 내용 추가·삭제를 동반한 재작성은 별도 집필 스킬.

    Also in 3 projects that use this

  • CoralGameSkill

    perf-profile

    Structured performance profiling workflow. Identifies bottlenecks, measures against budgets, and generates optimization recommendations with priority rankings.

    Also in 3 projects that use this

  • Rayan55050Skill

    content

    Создание контента: посты, статьи, тексты

    Also in 3 projects that use this

  • luischanciSkill

    proofread

    Run the proofreading protocol on manuscript files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.

    Also in 3 projects that use this

  • insight68Skill

    pricing

    Help figure out pricing for a product or service using minimalist entrepreneur principles. Use when someone is setting prices, considering price changes, or struggling with what to charge.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 64 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill activates, output:

    line 13
  2. Distinctive:

    Bullet-point-itis: Every section as bullets → Mix in short paragraphs

    line 58
  3. Distinctive:

    Lead with the point: Don't build up to it

    line 66
  4. Distinctive:

    Shorter sentences: If a sentence has a comma and an "and", consider splitting it

    line 67
  5. Distinctive:

    Cut the filler: If removing a word doesn't change the meaning, remove it

    line 71
  6. Distinctive:

    Read it aloud: If it sounds like a press release, rewrite it

    line 72

“Common” is measured: kept by at least 6 in 10 of the 64 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

✍️ Humanize: Rewriting for Natural Voice...

Remove AI tells and rewrite content to sound like a human wrote it.

Activation

When this skill activates, output:

✍️ Humanize: Rewriting for natural voice...

Then execute the protocol below.

Context Guard

ContextStatusPriority
User says "humanize", "make it sound human/natural"ACTIVE: rewrite contentP1
User says "clean up this writing", "remove AI tone"ACTIVE: rewrite contentP1
User says "rewrite for blog/social/client"ACTIVE, rewrite with audience in mindP2
User is writing code or technical docs (API refs, JSDoc)DORMANT, technical writing is fine as-isnone
User is writing commit messages or changelogsDORMANT, these have their own formatnone

Protocol

Step 1: Identify AI Patterns

Scan the content for these common AI writing tells:

Words to eliminate or replace:

AI PatternReplace With
"delve", "delve into""explore", "look at", "dig into"
"leverage""use", "take advantage of"
"utilize""use"
"facilitate""help", "make easier"
"comprehensive"(often removable, or "thorough", "complete")
"robust""solid", "strong", "reliable"
"streamline""simplify", "speed up"
"moreover", "furthermore"(cut entirely or use "also", "and")
"it's important to note"(cut: just state the thing)
"in conclusion"(cut, the reader knows it's the end)
"in today's [X] landscape"(cut entirely)
"game-changer"(be specific about the benefit)
"navigate" (non-literal)"deal with", "handle", "work through"
"paradigm"(use a concrete noun instead)
"synergy""overlap", "combination", "fit"

Structural patterns to fix:

  • Excessive hedging: "It might be worth considering that perhaps..." → Just say the thing
  • Hollow transitions: "Now, let's turn our attention to..." → Cut, or use a heading
  • Overlong intros: "In the ever-evolving world of..." → Start with the point
  • Bullet-point-itis: Every section as bullets → Mix in short paragraphs
  • Triple emphasis: "truly remarkable and incredibly powerful" → Pick one adjective
  • Sycophantic openings: "Great question!" → Don't; just answer
  • Unnecessary qualifiers: "very", "really", "quite", "rather" → Usually cuttable

Step 2: Rewrite

Apply these principles:

  1. Lead with the point: Don't build up to it
  2. Shorter sentences: If a sentence has a comma and an "and", consider splitting it
  3. Active voice: "The team built X" not "X was built by the team"
  4. Concrete over abstract: Specific examples beat general claims
  5. Vary rhythm: Mix short punchy sentences with longer ones. Not all the same length.
  6. Cut the filler: If removing a word doesn't change the meaning, remove it
  7. Read it aloud: If it sounds like a press release, rewrite it

Step 3: Preserve

Do NOT change:

  • Technical accuracy or meaning
  • Code examples or technical terms
  • Proper nouns, brand names, acronyms
  • Intentional formatting (headings, lists where appropriate)
  • The author's actual opinions or arguments

Step 4: Present

Show the rewritten version. If the changes are substantial, briefly note what was changed:

  • "Removed hedging and filler from intro"
  • "Replaced passive voice throughout"
  • "Cut 40%: mostly redundant transitions"

Inputs

  • Text content to humanize (from user's prompt, clipboard, or a file)
  • Optional: target audience (blog readers, clients, social media)

Outputs

  • Rewritten content with AI patterns removed
  • Brief summary of changes made

Example Usage

User: "Humanize this paragraph"

In today's rapidly evolving digital landscape, it's important to note that leveraging comprehensive AI solutions can facilitate robust workflow optimization. Moreover, these game-changing tools enable organizations to navigate complex challenges and streamline their operations.

✍️ Humanize: Rewriting for natural voice...

AI tools speed up your workflow. They handle the repetitive stuff so your
team can focus on work that actually matters.

Changes: Cut filler intro, replaced "leverage/facilitate/robust/streamline"
with plain language, removed empty transitions, reduced from 41 words to 22.

Level History

  • Lv.1: Base: AI pattern detection and rewrite protocol. Curated replacement table, structural fixes, voice guidelines. (Origin: MemStack v3.1, Feb 2026)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.