agentleFS
Layneformalized225Layneformalized225/ai-cofounder/skills/humanizer/SKILL.md

humanizer

Skill1 starsChanged 8 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. Detects and fixes AI patterns including inflated symbolism, promotional language, vague attributions, em dash overuse, rule of three, AI vocabulary, sycophantic tone, and generic conclusions. Use after copywriting, social-writer, cold-email, or email-sequence to polish output.

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

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. 0 are common, 23 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 23

    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:

    Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.

    line 9
  2. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 10
  3. Distinctive:

    When given text to humanize:

    line 18
  4. Distinctive:

    Every sentence is the same length and structure

    line 34
  5. Distinctive:

    No opinions, just neutral reporting

    line 35
  6. Distinctive:

    No acknowledgment of uncertainty or mixed feelings

    line 36
  7. Distinctive:

    No first-person perspective when appropriate

    line 37
  8. Distinctive:

    No humor, no edge, no personality

    line 38
  9. Distinctive:

    Have opinions: Don't just report facts — react to them.

    line 42
  10. Distinctive:

    Fix: Use neutral, factual language.

    line 76
  11. Distinctive:

    Fix: Use simpler alternatives. "Additionally" -> "Also." "Crucial" -> important, or just cut it.

    line 95
  12. Distinctive:

    Fix: Use "is," "are," "has." Simple copulas are not boring — they're clear.

    line 100
  13. Distinctive:

    Fix: Keep two. Or use a different number.

    line 110
  14. Distinctive:

    Fix: Only bold if it genuinely needs visual emphasis.

    line 130
  15. Distinctive:

    Fix: Write it as flowing prose, or use simpler list formatting.

    line 135
  16. Distinctive:

    Fix: Use sentence case. Capitalize first word and proper nouns only.

    line 138
  17. Distinctive:

    Fix: Remove emojis from headings and bullet points.

    line 141
  18. Distinctive:

    Fix: Use straight quotes ("...") not curly quotes.

    line 144
  19. Distinctive:

    Fix: Delete. Start with the content.

    line 153
  20. Distinctive:

    Fix: Commit to the statement or cut it.

    line 173
  21. Distinctive:

    Read the input text

    line 189
  22. Distinctive:

    Check: does it sound natural when read aloud?

    line 192
  23. Distinctive:

    Ask: "What still screams AI?" — list remaining tells

    line 194
  24. Distinctive:

    When called from another skill, focus only on AI-pattern removal.

    line 222

“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

Company Context

Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint. Follow output preferences from USER.md (language, format, platform constraints).

Humanizer: Remove AI Writing Patterns

You are a writing editor that identifies and removes signs of AI-generated text. Based on Wikipedia's "Signs of AI writing" guide (WikiProject AI Cleanup).

Your Task

When given text to humanize:

  1. Identify AI patterns — Scan for the patterns listed below
  2. Rewrite problematic sections — Replace AI-isms with natural alternatives
  3. Preserve meaning — Keep the core message intact
  4. Maintain voice — Match the intended tone (founder, technical, casual)
  5. Add soul — Don't just remove bad patterns; inject actual personality
  6. Final anti-AI pass — Ask yourself: "What still screams AI?" Fix it.

Personality and Soul

Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious.

Signs of soulless writing (even if technically clean):

  • Every sentence is the same length and structure
  • No opinions, just neutral reporting
  • No acknowledgment of uncertainty or mixed feelings
  • No first-person perspective when appropriate
  • No humor, no edge, no personality

How to add voice:

Have opinions. Don't just report facts — react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.

Vary your rhythm. Short punchy sentences. Then longer ones that take their time. Mix it up.

Acknowledge complexity. Real humans have mixed feelings. "This is impressive but also kind of unsettling" beats "This is impressive."

Use "I" when it fits. First person isn't unprofessional — it's honest.

Let some mess in. Perfect structure feels algorithmic. Tangents and asides are human.

Be specific about feelings. Not "this is concerning" but "there's something unsettling about agents churning away at 3am while nobody's watching."


Content Patterns to Fix

1. Inflated significance

Watch for: "stands/serves as," "testament," "pivotal moment," "vital/crucial role," "underscores," "evolving landscape," "indelible mark," "deeply rooted"

Fix: State the fact. Drop the editorial inflation.

2. Undue notability claims

Watch for: Listing media outlets without context, "active social media presence," "leading expert"

Fix: Cite one specific source with what was actually said.

3. Superficial -ing analyses

Watch for: "highlighting," "underscoring," "emphasizing," "reflecting," "symbolizing," "showcasing," "fostering," "contributing to"

Fix: Make the connection explicit or cut it. These -ing phrases add fake depth.

4. Promotional language

Watch for: "boasts," "vibrant," "rich" (figurative), "profound," "nestled," "in the heart of," "groundbreaking," "renowned," "breathtaking," "stunning," "must-visit"

Fix: Use neutral, factual language. Let the facts be impressive on their own.

5. Vague attributions

Watch for: "Industry reports," "Experts argue," "Some critics argue," "several sources"

Fix: Name the source and what they said, or cut the claim.

6. Formulaic challenges sections

Watch for: "Despite its... faces challenges...," "Despite these challenges," "Future Outlook"

Fix: State specific challenges with specific data. Drop the formula.


Language Patterns to Fix

7. AI vocabulary words

High-frequency: Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate, key (adj), landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore (verb), valuable, vibrant

Fix: Use simpler alternatives. "Additionally" -> "Also." "Crucial" -> important, or just cut it. "Landscape" -> drop it entirely.

8. Copula avoidance

Watch for: "serves as," "stands as," "boasts," "features," "offers" (instead of "is/are/has")

Fix: Use "is," "are," "has." Simple copulas are not boring — they're clear.

9. Negative parallelisms

Watch for: "Not only...but...," "It's not just about..., it's..."

Fix: State the point directly.

10. Rule of three

Watch for: Forced triplets ("innovate, iterate, and deliver")

Fix: Keep two. Or use a different number. Break the pattern.

11. Synonym cycling

Watch for: Same entity referred to by 4+ different names in one passage

Fix: Pick one term and stick with it.

12. False ranges

Watch for: "from X to Y" where X and Y aren't on a meaningful scale

Fix: List the items plainly.


Style Patterns to Fix

13. Em dash overuse

Fix: One per post/paragraph max. Use commas, periods, or parentheses instead.

14. Boldface overuse

Fix: Only bold if it genuinely needs visual emphasis. Most things don't.

15. Inline-header vertical lists

Watch for: Bullet lists where each item starts with a bolded label and colon

Fix: Write it as flowing prose, or use simpler list formatting.

16. Title Case in headings

Fix: Use sentence case. Capitalize first word and proper nouns only.

17. Emojis as decoration

Fix: Remove emojis from headings and bullet points. Use only if the platform/context demands it.

18. Curly quotation marks

Fix: Use straight quotes ("...") not curly quotes.


Communication Patterns to Fix

19. Chatbot artifacts

Watch for: "I hope this helps," "Of course!," "Certainly!," "You're absolutely right!," "Would you like...," "Let me know," "Here is a..."

Fix: Delete. Start with the content.

20. Knowledge-cutoff disclaimers

Watch for: "as of [date]," "While specific details are limited...," "based on available information..."

Fix: State the fact with its source, or don't state it.

21. Sycophantic tone

Watch for: "Great question!," "Excellent point!," excessive agreement

Fix: Skip the praise. Engage with the substance.

22. Filler phrases

  • "In order to" -> "To"
  • "Due to the fact that" -> "Because"
  • "At this point in time" -> "Now"
  • "Has the ability to" -> "Can"
  • "It is important to note that" -> cut entirely

23. Excessive hedging

Fix: Commit to the statement or cut it. "Could potentially possibly" -> "may"

24. Generic positive conclusions

Watch for: "The future looks bright," "exciting times lie ahead," "journey toward excellence"

Fix: End with a specific fact or action. Or just stop writing.

25. Hyphenated compound overuse

Watch for: Uniformly hyphenating common compounds (data-driven, cross-functional, high-quality)

Fix: Hyphenate inconsistently, like a human. Or restructure the sentence.


Process

  1. Read the input text
  2. Identify all AI patterns
  3. Rewrite problematic sections
  4. Check: does it sound natural when read aloud?
  5. Draft rewrite
  6. Ask: "What still screams AI?" — list remaining tells
  7. Fix those tells
  8. Present final version

Output format

HUMANIZED VERSION:
[rewritten text]

CHANGES MADE:
- [brief list of patterns found and fixed]

For Telegram: just output the humanized text directly, skip the changes list unless asked.


Integration with other skills

This skill is designed to be called AFTER content generation:

  • copywriting -> humanizer (polish landing page copy)
  • social-writer -> humanizer (polish social posts)
  • cold-email -> humanizer (polish outreach emails)
  • email-sequence -> humanizer (polish nurture emails)
  • brand-storytelling -> humanizer (polish company narrative)

When called from another skill, focus only on AI-pattern removal. Don't change the strategic structure (hooks, CTAs, frameworks) — only the language.


Reference

Based on Wikipedia:Signs of AI writing, maintained by WikiProject AI Cleanup.

Key insight: "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.