agentleFS
allthriveaiallthriveai/amplify/.claude/skills/humanizer/SKILL.md

humanizer

Skill0 starsChanged 3 months agoMITView on GitHub

Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

188 other projects use a version of this, 2 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 4 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

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the user runs /humanizer or asks to humanize text, apply these rules to all prose.

    line 10
  2. Distinctive:

    No em dash overuse: Use commas, colons, or separate sentences.

    line 92
  3. Distinctive:

    Break the rule-of-three: Don't always list exactly three items.

    line 93
  4. Distinctive:

    No negative parallelisms: Avoid "It's not just X; it's Y" and "Not only...but also...".

    line 96
  5. Distinctive:

    No brochure language ("revolutionize your workflow", "unlock the power of")

    line 100
  6. Distinctive:

    No generic positive conclusions ("the future looks bright", "exciting times ahead")

    line 101
  7. Distinctive:

    No sycophantic language ("Great question!", "Absolutely!", "I hope this helps!")

    line 102
  8. Distinctive:

    Read each paragraph out loud.

    line 114

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

Instructions

When the user runs /humanizer or asks to humanize text, apply these rules to all prose. Preserve code, data, tables, and structural elements exactly as-is.

AI Vocabulary

Replace these words with natural alternatives:

AI wordUse instead
delvedig into, explore, look at
landscapespace, field, area
crucial / pivotalimportant, key, matters because
showcaseshow, demonstrate
leverageuse
utilizeuse
facilitatehelp, enable
comprehensivethorough, full, complete
robustsolid, strong, reliable
innovativenew, novel, clever
cutting-edgelatest, modern, new
game-changerbig shift, major change
paradigmmodel, approach
synergycombination, working together
empowerlet, help, enable
streamlinesimplify, speed up
tapestry(just cut it)
underscoreshow, point to
fosterbuild, grow, support
enhanceimprove, strengthen
vibrant(be specific about what makes it alive)
profounddeep, real, serious
interplayrelationship, tension, push and pull
intricatedetailed, layered, complex
multifaceted(just describe the facets)
nuancedspecific, layered
realmarea, space, field
testamentproof, evidence, sign

Significance Inflation

Cut phrases that puff up importance beyond what the content earns:

  • "stands as a testament to"
  • "marking a key moment in"
  • "reflects broader themes of"
  • "speaks to the larger"
  • "is a powerful reminder that"
  • "serves as a beacon of"

Replace with plain statements. If it's important, the content shows that. You don't need to announce it.

Superficial -ing Phrases

Cut these when they add no information:

  • "highlighting the importance of"
  • "underscoring the need for"
  • "symbolizing the"
  • "emphasizing the"
  • "showcasing the"
  • "demonstrating the power of"
  • "illustrating the"

These are padding. Say what the thing actually does instead.

Filler and Hedging

Remove entirely:

  • "It's worth noting that"
  • "It's important to note"
  • "Interestingly"
  • "In today's [X] landscape/world/era"
  • "Let's dive in"
  • "Without further ado"
  • "In order to" (just say "to")
  • "At its core"
  • "It is important to note that"
  • "Essentially" / "Basically" / "Fundamentally"
  • Excessive "very", "really", "quite"

Structural Tells

  • No em dash overuse. Use commas, colons, or separate sentences. One em dash per page is fine. Five is a tell.
  • Break the rule-of-three. Don't always list exactly three items. Sometimes two is enough. Sometimes four is what's true.
  • Vary sentence rhythm. Mix short and long. Don't keep them uniform. A paragraph of five 15-word sentences sounds generated.
  • Don't start consecutive paragraphs the same way. Especially with "The" or "This".
  • No negative parallelisms. Avoid "It's not just X; it's Y" and "Not only...but also...". Say what it is. Skip what it isn't.

Promotional Tone

  • No brochure language ("revolutionize your workflow", "unlock the power of")
  • No generic positive conclusions ("the future looks bright", "exciting times ahead")
  • No sycophantic language ("Great question!", "Absolutely!", "I hope this helps!")
  • State facts. Have opinions. Skip the cheerleading.

What to Preserve

  • Code examples, data points, technical details: exactly as-is
  • Bullet lists, numbered lists, tables, headings: structural, not AI patterns
  • The user's own words and voice: the humanizer is for YOUR writing, not theirs
  • Specific details, names, numbers, quotes: keep all of it

The Test

Read each paragraph out loud. If it sounds like something assembled from parts rather than something said by a person, rewrite it. Good writing has rhythm, specificity, and occasionally surprises you. AI writing is smooth, balanced, and never takes a risk.

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.