agentleFS
BolivarTechBolivarTech/claude-skills/humanize/SKILL.md

humanize

Skill0 starsChanged 51 days agoMITView on GitHub

Rewrite existing prose with a natural, consistent voice, varied rhythm, plain language, and fewer formulaic AI patterns. Use when the user asks to humanize, de-robotify, make text sound natural or less like AI, or improve first-person writing such as emails, applications, posts, essays, cover letters, and bios. Use for editing an existing draft, not composing from notes or from scratch.

74 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use humanize-redo, humanize-korean and 9 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

  • 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

  • ElasticSkill

    create-skill

    Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 64 edited versions we read keep these.

  • 9

    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:

    Never invent opinions, anecdotes, comparisons, reactions, habits, or specific facts.

    line 42
  2. Distinctive:

    Do not delete a weak claim as filler, transfer an attributed claim to the writer, or strengthen a hedge.

    line 47
  3. Distinctive:

    If a qualifier's effect is unclear, preserve it.

    line 50
  4. Distinctive:

    Keep the writer's distribution of emphasis unless the source supports a change.

    line 77
  5. Distinctive:

    Filler: Remove empty framing ("It's worth noting"), stage directions ("Let me break this down"), redundant closers, and decorative asides …

    line 78
  6. Distinctive:

    Vocabulary: Prefer plain verbs and exact nouns, such as *use* over *utilize*.

    line 93
  7. Distinctive:

    Prefer a structural rewrite to a synonym where it helps more.

    line 100
  8. Distinctive:

    Repetition: Keep the correct subject noun rather than rotating through "system", "platform", "solution", and "tool".

    line 101
  9. Distinctive:

    Stop when the relevant problems are addressed.

    line 145

“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

Edit existing prose. Do not expand notes into a draft or compose new content; treat any requested expansion as a separate task. Work from the writer's facts, vocabulary, stance, and certainty, regardless of who drafted the text. Edit the writing; do not manufacture a persona. Human writing can still be stiff, repetitive, vague, or overworked. Improve structure before substituting words.

Meaning and voice

The pass is editorial, not semantic: change rhythm, syntax, word choice, sentence length, paragraph entry, and presentation, never what the text asserts or who asserts it. Rewrite running prose only. Unless the user authorizes content changes, preserve facts, names, numbers, dates, versions, paths, flags, commands, and meaningful order, including chronology and argument dependencies; the breadth and strength of claims, attribution, uncertainty, and its reasons; code blocks, inline code, signatures, identifiers, structured docstring fields, reference tables, command examples and output, error messages, UI strings, and technical symbols such as ×, ÷, and ≈. Preserve direct quotations verbatim, punctuation included, unless the user explicitly asks to edit them; a request to humanize the surrounding text does not cover the quote.

Infer audience, medium, formality, verbosity, grammatical person, contractions, and regional or domain vocabulary from the request and source. Keep one register across the document and preserve the existing one when no preference is given: formal writing need not become chatty, and useful technical terms stay. Keep each passage in the language it was written in.

Never invent opinions, anecdotes, comparisons, reactions, habits, or specific facts; use details from the supplied material or keep the wording general. Preserve informative asides and useful irregularities, but correct mistakes. Do not add typos, false starts, fragments, or awkwardness to simulate a person.

Do not delete a weak claim as filler, transfer an attributed claim to the writer, or strengthen a hedge. Collapse redundant qualifiers only at the same certainty: "may potentially possibly reduce X" can become "may reduce X", never "reduces X". If a qualifier's effect is unclear, preserve it. Ask only when missing information prevents completion and cannot be handled by preserving the source or using existing context; optional improvements need no approval and do not make an edit incomplete.

Editorial checks

Review the entire text for meaning, voice, structure, rhythm, filler, repetition, and vocabulary; a first impression of naturalness does not excuse the review. Apply changes that fit the voice and address a problem in the draft, and return the original only when the full review finds no justified improvement. Do not maximize variation or force every sentence into a new shape.

  • Rhythm: Vary openings, clause complexity, and sentence length. If more than half the sentences cluster around 12 to 20 words, shorten some and let others develop. Do so by cutting, reordering, joining, or splitting existing sentences; do not add explanations, examples, or transitions to vary length, nor manufacture fragments, parentheticals, or unusual syntax. Passive voice is appropriate when the affected thing is the topic or the actor is unknown or irrelevant. After removing filler, join short sentences that form one thought if the rhythm has gone flat.
  • Paragraphs: Address repeated topic/support/conclusion structures, identical paragraph lengths, excessive headings, mechanical three-part lists, and consecutive paragraphs that open with the same subject; vary those by opening with the object, a circumstance, or the verb, not by renaming the subject. Open with an existing example, consequence, number, or objection where it helps. Keep the writer's distribution of emphasis unless the source supports a change.
  • Filler: Remove empty framing ("It's worth noting"), stage directions ("Let me break this down"), redundant closers, and decorative asides only when removal changes neither information nor claim strength. A familiar phrase may carry certainty, emphasis, or stance: "I care about quality" is a personal claim, even if vague.
  • Constructions: Rewrite "It's not just X; it's Y", "This isn't about X; it's about Y", and "Not only X, but also Y", preserving both halves and the contrast between them: recast the pair as a plain conjunction or as two sentences, keeping neither half of the frame, not "not only", "not just", or "no solo", and not "but", "sino", or "también"; a colon or dash in place of "sino" keeps the construction. Break repeated tricolons without dropping claims. In casual prose, replace formal transitions such as furthermore, moreover, and consequently with plain connectives or omit them. Whatever the register, a replaced or removed transition keeps its logical relationship.
  • Vocabulary: Prefer plain verbs and exact nouns, such as use over utilize. Scan for delve, tapestry, leverage, seamless, foster, elevate, unlock, holistic, game-changer, cutting-edge, and "in today's fast-paced world". These are contextual signals, not a substitution table: replace wording for imprecision, redundancy, or register mismatch. A superlative, intensifier, or evaluative adjective is part of the claim's strength; drop it only when another word in the sentence already carries it. Prefer a structural rewrite to a synonym where it helps more.
  • Repetition: Keep the correct subject noun rather than rotating through "system", "platform", "solution", and "tool". Fix monotonous openings and connectives by changing sentence construction, not the subject's name.

Character handling

Scan editable prose last for —, –, --, …, “, ”, ‘, and ’, with a search or regular expression when available, excluding protected material and direct quotations from the search before replacing anything, and correct matches contextually. Rewrite sentences that use an em dash or -- as a separator, preferring a period, comma, parentheses, or colon over another dash; a dash that opens or closes dialogue, as in Spanish, is punctuation and stays. Replace prose-separator en dashes with a hyphen or restructure; 2010–2015 may become 2010-2015. Replace curly quotes with straight quotes and … with ... in ordinary prose. Leave typography inside protected material and direct quotations unchanged.

Other languages

Apply the same structural and semantic criteria, but do not translate the English word list mechanically; derive local patterns from native drafts when available and otherwise avoid claiming complete coverage.

For Spanish, inspect potentially empty framing ("es importante destacar", "cabe mencionar", "en el mundo actual"), stage directions ("a continuación analizaremos", "veamos"), automatic por ende or asimismo, repeated closing gerunds ("logrando así", "permitiendo"), shifts between tú and usted or verb persons, and English sentence patterns in translations. Oral markers such as bueno, o sea, and pues must fit an existing informal voice, region, and context; never insert them as a quota. "Sin duda alguna" can express certainty: removing it from "Sin duda alguna, esta es la mejor opción" weakens the writer's stated confidence even though the core claim remains. Preserve it unless the context shows its force is redundant and fully retained.

Workflow and delivery

  1. Identify voice, audience, medium, and register.
  2. Freeze protected material and flag any change that could alter claims, attribution, certainty, or meaningful order.
  3. Edit structure, language, rhythm, repetition, and characters, in that order.
  4. Compare source and result for meaning and register drift, invented material, repetition, rhythm after deletions, and unnecessary growth.

Stop when the relevant problems are addressed; constant contractions, asides, or fragments create another artificial register. Preserve or reduce length, allowing only the minimal increase needed to avoid ambiguity, preserve meaning, or state a supplied fact precisely; add no unrequested summaries, restatements, or explanations. Do not add a title, unsolicited questions, lists of missing details, or incomplete-pass labels for optional edits, before or after the text. Assess internally and return the edited text without explaining individual decisions unless the user asks for an analysis.

Examples of semantic boundaries

  • "Many experts believe this approach may potentially improve retention." becomes "Many experts believe this approach may improve retention." Attribution and uncertainty remain.
  • "The system is reliable" must not become "The system stays up": the latter narrows the claim.
  • "In today's fast-paced world, I am passionate about leveraging cutting-edge solutions to drive impactful results" permits removing empty framing, but the personal claim stays and specificity requires facts from the source.
  • A quotation that reads "he called the plan “final”" keeps its curly quotes even when the surrounding prose is normalized to straight ones: the characters inside a quotation are part of what was said.
  • Three consecutive paragraphs beginning "The report…", "The report…", "The report…" become, for instance, "The report…", "In its second part, the report…", "What the report leaves out…": same subject, different entry point.

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.