agentleFS
lukesw55lukesw55/ai-pm-toolkit/.agents/skills/humanizer/SKILL.md

humanizer

Skill1 starsChanged 42 days agoMITView on GitHub

Rewrite AI-sounding prose so it reads like the writer, not a chatbot, without changing what it says. Use when editing or reviewing any text people will read: exec memos, PRDs, Confluence pages, Slack messages, release notes, customer comms, ghostwritten drafts, discovery syntheses. Catalogue of patterns from Wikipedia's "Signs of AI writing": inflated claims, sales language, vague sources, stock AI words, forced groups of three, em dashes, bold mini-heading lists, chatbot leftovers, filler, stacked qualifiers, fake-candid openings, unraised objections. Keeps every claim, invents nothing, matches the writer's voice when a sample exists. For structural tells (label-colon bullets, emoji headings, file artefacts) use anti-slop; this skill owns the prose. Trigger on "humanise this", "humanize this", "remove AI tells", "make this sound human", "esse texto tá com cara de IA", "tira o ar de ChatGPT", "passa o humanizer".

187 other projects use a version of this, 8 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use economy-mode, personal-voice 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.
  • Microsoft AzureSkill

    economy-mode

    Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

    Also in 5 projects that use this

  • petermuirurithuoSkill

    personal-voice

    Captures the user's personality, communication style, and values. Use this skill whenever responding to the user, drafting anything on their behalf (emails, CVs, messages, opinions, explanations), or whenever tone, word choice, or how an opinion is delivered matters. Apply it by default for any prompt, not only when the user explicitly asks for "my style" or "my voice.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 3 projects that use this

  • +9 more from Azure

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 21

    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 given text to humanize:

    line 48
  2. Distinctive:

    Find AI patterns: Check the text against the patterns below.

    line 50
  3. Distinctive:

    Match the voice: Use the right tone for the text, such as formal, casual, or technical.

    line 53
  4. Distinctive:

    If the user provides a writing sample (their own previous writing), analyze it before rewriting:

    line 59
  5. Distinctive:

    Read the sample first. Note its sentence length, word choice, paragraph openings, punctuation, repeated phrases, and transitions.

    line 61
  6. Distinctive:

    If there is no sample, use the guidance below.

    line 63
  7. Distinctive:

    Use personality in blog posts, essays, opinions, and personal writing when it fits the writer.

    line 71
  8. Distinctive:

    When personality fits, keep the writer's opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm.

    line 73
  9. Distinctive:

    Useful limits and disclaimers: Keep scope statements, legal and safety notices, real corrections, named objections, replies, and FAQ …

    line 100
  10. Distinctive:

    Real alternatives: Keep options that a reader may consider in a design document, tutorial, or argument.

    line 101
  11. Distinctive:

    Secondhand text: Do not rewrite watched phrases inside quotations, titles, proper names, or examples where the phrase is being discussed …

    line 104
  12. Distinctive:

    When unsure, look for several patterns together.

    line 106
  13. Distinctive:

    Specific, unusual details: Keep a real address, an odd quote, or a phrase such as "the lawyer who used to work upstairs from my dentist."

    line 112
  14. Distinctive:

    Mixed feelings and unresolved tension: Keep lines such as "I think this is mostly good, but it bothers me, and I can't fully explain why."

    line 113
  15. Distinctive:

    Deliberate first-person choices: Keep a cut or word choice when the writer can explain why it belongs.

    line 115
  16. Distinctive:

    File mode: When the user names a file, run the full rewrite process but write only the final text to the file.

    line 126
  17. Distinctive:

    Embedded mode: When another task uses this skill for a pull request, commit message, or document, return only the final text.

    line 128
  18. Distinctive:

    Read the source and mark each AI pattern.

    line 132
  19. Distinctive:

    Write a draft. Read it aloud.

    line 133
  20. Distinctive:

    Treat any unsupported addition or lost claim as an error.

    line 137
  21. Distinctive:

    Write the final version. State each point naturally instead of patching one flagged phrase at a time.

    line 138

“Common” is measured: kept by at least 6 in 10 of the 174 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

Humanizer: remove AI writing patterns

Rewrite AI-sounding text so it reads like the writer, not a chatbot. Do not change what it says or make up details.

The patterns below come from Wikipedia's "Signs of AI writing", maintained by WikiProject AI Cleanup.

Trigger phrases

Invoke on: "humanise this", "humanize this", "remove AI tells", "make this sound human", "fix the AI tone", "esse texto tá com cara de IA", "tira o ar de ChatGPT", "passa o humanizer", "AI-written", "soa como IA".

Typical material: essays, articles, blog posts, exec memos, PRDs, Confluence pages, Slack messages, release notes, customer comms, LinkedIn posts, ghostwritten drafts, any AI-generated text that needs rewriting.

Related skills

  • anti-slop owns the structural twin of several patterns here: label-colon bullets, decorative emoji headings, follow-up spam, forbidden file artefacts. When text mixes prose and structure, both apply; the Toolkit note: lines inside the pattern references say which anti-slop item pairs with which pattern.
  • humanize-deliverables is the publish-time gate. It runs this skill on outbound prose, then hooks/humanize-mark.sh records a sha256 of the final bytes and hooks/humanize-gate.sh blocks the publish or send tool until that mark exists.
  • inference-discipline takes precedence over §21 and §24: a qualifier that marks a claim as unverified stays, or the claim goes. It never gets smoothed into a confident sentence. Approval markers belong to the conversation, written out in words, and never survive into a delivered artefact.

Progressive loading

Load this SKILL.md first. The pattern catalogue sits in references/ (table below); references/progressive-loading.md says which file to open for which kind of text.

What to do

When given text to humanize:

  1. Find AI patterns. Check the text against the patterns below.
  2. Keep every claim. You may shorten dull parts, expand useful parts, and merge or split paragraphs. Keep the information even when you change the structure.
  3. Do not invent facts. Do not add a fact, name, number, date, quote, or citation unless it comes from the source or the user. If a sentence needs a missing detail, ask for it or use a simpler sentence. You may add an opinion or reaction when the writer's voice calls for one, but you may not add a factual claim. Fiction is exempt because invented details are part of the task.
  4. Match the voice. Use the right tone for the text, such as formal, casual, or technical. Add personality only when the text and the writer call for it.

The input type controls what you return. See How to return the result. Use the same rewrite process in every mode.

Match the writer's voice

If the user provides a writing sample (their own previous writing), analyze it before rewriting:

  1. Read the sample first. Note its sentence length, word choice, paragraph openings, punctuation, repeated phrases, and transitions.
  2. Match those habits. Do not replace casual words with formal ones or remove deliberate quirks.
  3. If there is no sample, use the guidance below.

A writing sample takes priority over these style rules. If the sample uses em dashes, keep them at about the same rate. Do not apply §14 as a ban.

Add personality only when it fits

Removing AI patterns is only half the job. The result should still sound like a person.

Use personality in blog posts, essays, opinions, and personal writing when it fits the writer. Keep reference, technical, legal, and factual text neutral. Do not add opinions or first-person language where they do not belong.

When personality fits, keep the writer's opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never invent facts to make the text feel personal.

Pattern catalogue

PatternsFile
1–13, content and language: inflated claims, name-dropping, -ing analysis, sales language, vague sources, stock challenge sections, overused AI words, avoiding is/are, not X but Y, forced groups of three, synonym cycling, false ranges, passive voicereferences/patterns-1-13-content-and-language.md
14–35, style, chatbot, filler and hedging: dashes, bold, bold mini-heading lists, title case, emojis, curly quotes, chatbot leftovers, knowledge-limit disclaimers, agreeable tone, filler, qualifiers, generic endings, hyphenated pairs, fake depth, announcements, repeated headings, previous-version talk, dramatic fragments, sayings, fake-candid openings, unraised objections, fake alternativesreferences/patterns-14-35-style-and-filler.md
Vocabulary supplement to §7 and §23references/n-gram-blacklist.md

Check for false positives

What not to flag

A person may use some of these patterns. Do not treat any item below as proof by itself:

  • Perfect grammar and consistent style. Many writers are professionals or have been edited. Polish does not equal AI.
  • Mixed casual and formal styles. This can reflect the writer's field, age, or personal habits.
  • "Bland" or "robotic" prose. AI prose has specific tells. Generic dryness without those tells is just dry writing.
  • Formal or academic words. §7 lists specific words that AI writing overuses. Do not simplify every formal word.
  • Letter-style opening or closing on a comment. Salutations and sign-offs predate ChatGPT by centuries.
  • Common transition words in isolation. Additionally, moreover, consequently are AI-coded only when piled up. One however is not a tell.
  • Curly quotes alone. macOS, Word, Google Docs, and most CMSes auto-curl by default. Curly quotes only count when stacked with other tells.
  • Em dashes alone. Many editors and journalists use them often. Em dashes are evidence only when paired with formulaic sales-y rhythm.
  • One short sentence for emphasis. Flag dramatic fragments only when several appear in a row.
  • Deliberate repeated openings. Writers may repeat an opening to build rhythm or pressure, as in "She came. She saw. She conquered." Change it only when the repetition adds nothing.
  • "Honestly" or "look" mid-sentence. These are ordinary in casual writing. The tell is the standalone theatrical opener, not the word itself.
  • Useful limits and disclaimers. Keep scope statements, legal and safety notices, real corrections, named objections, replies, and FAQ answers.
  • Real alternatives. Keep options that a reader may consider in a design document, tutorial, or argument. Remove only an unlikely option that the text dismisses and never uses again.
  • Unsourced claims. Most of the web is unsourced. Lack of citations doesn't prove anything.
  • Correct, complex formatting. Visual editors and templates produce clean output without any AI.
  • Secondhand text. Do not rewrite watched phrases inside quotations, titles, proper names, or examples where the phrase is being discussed rather than used.

When unsure, look for several patterns together. One em dash proves nothing. Several stock patterns in the same passage are stronger evidence.

Human details to keep

These details often carry the writer's voice. Keep them unless they hurt the meaning:

  • Specific, unusual details. Keep a real address, an odd quote, or a phrase such as "the lawyer who used to work upstairs from my dentist."
  • Mixed feelings and unresolved tension. Keep lines such as "I think this is mostly good, but it bothers me, and I can't fully explain why."
  • Dated, era-bound references. Slang, memes, or in-jokes that map to a specific year and subculture. Models lag by a year or more.
  • Deliberate first-person choices. Keep a cut or word choice when the writer can explain why it belongs.
  • Variety in sentence length. Real writing alternates short and long. AI writing tends toward an even, mid-length cadence.
  • Genuine asides, parentheticals, or self-corrections. "(I keep wanting to say 'almost' here, but it really was certain.)" Models rarely interrupt themselves like this.
  • Edits made before November 30, 2022. ChatGPT's public launch. Anything older than that is, with very rare exceptions, not AI-written.

How to return the result

Pasted text (default). Return the draft, a short list of remaining AI patterns, and the final rewrite.

Toolkit note: that short list also names the metrics, dates, names, and constraints that stayed intact, so the reader can check that nothing load-bearing moved; the substance check in humanize-deliverables reads it.

File mode. When the user names a file, run the full rewrite process but write only the final text to the file. Change prose only. Keep code blocks, YAML metadata, data, and link targets unchanged. Then give the user a short summary.

Embedded mode. When another task uses this skill for a pull request, commit message, or document, return only the final text.

Rewrite process

  1. Read the source and mark each AI pattern.
  2. Write a draft. Read it aloud. Check the rhythm, details, simple verbs such as is and has, and the right level of formality.
  3. Ask two questions:
    • "What still sounds AI-generated?"
    • "Did the rewrite add or remove any fact, name, number, date, quote, citation, ranking, or other claim?" Treat any unsupported addition or lost claim as an error.
  4. Write the final version. State each point naturally instead of patching one flagged phrase at a time. If a sentence stays awkward, rewrite the paragraph around its main point. Apply the dash rule in §14.

Return the result required by How to return the result.

Source

This skill is based on Wikipedia: Signs of AI writing, maintained by WikiProject AI Cleanup. Its patterns come from reviews of AI-generated text on Wikipedia.

Wikipedia's main point: "LLMs use statistical algorithms to guess what should come next. The result tends toward the most statistically likely result that applies to the widest variety of cases."

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.