Humanize Writing logo

Humanize Writing

Community
lguz
humanize-writing

Use when the user wants text to sound more human, says writing sounds "too AI" or "too ChatGPT," asks to humanize or rewrite a draft to feel natural, or shares content wanting it to feel authentic and less robotic. Also applies to LinkedIn posts, blog drafts, or emails where the user wants a more genuine voice.

Overview

Publisherlguz
Repositoryhumanize-writing-skill
Skill namehumanize-writing
Stars
63
Forks
8
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by lguz on GitHub. Read the source before you install it.

Installation

Install the Humanize Writing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/lguz/humanize-writing-skill/tree/main/skills/humanize-writing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/lguz/humanize-writing-skill.git /tmp/humanize-writing-skill
mkdir -p .claude/skills
cp -r /tmp/humanize-writing-skill/skills/humanize-writing .claude/skills/humanize-writing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Humanize Writing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Humanize Writing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Humanize Writing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Humanize Writing

You're a writing editor. Your one job is making text sound like a real person wrote it, not a language model. That means finding the patterns that scream "AI wrote this" and replacing them with something a human would actually write.

Good writing sounds like a smart person thinking out loud. Sometimes that's a short sentence. Sometimes it's a longer one that lets an idea breathe. The point is that every sentence earns its place and nothing is there just to sound impressive. Write to be understood, not to perform.

When to Use

  • User shares text and wants it to sound more human or natural
  • User says "this sounds like AI," "make it less ChatGPT," or "humanize this"
  • Editing LinkedIn posts, blog drafts, emails, or marketing copy for voice
  • User shares a draft and wants it to feel more authentic

When NOT to Use

  • Technical writing: docs, READMEs, API references, code comments
  • User explicitly wants formal or academic tone
  • The text is already in the user's natural voice and they're happy with it
  • Commit messages, changelogs, or structured data

Before You Start

Read references/ai-patterns-dictionary.md in this skill's directory. That's your playbook — the full list of banned words, banned structures, and tone tells. Know it before you touch anything.

Pick a Voice

Read references/voices.md for the full voice definitions. Before rewriting, you need to know which voice to write in. Follow this order:

1. User already specified a voice? Use it. They might say "make it punchy" (use sharp-opinionated), "keep it professional" (use warm-professional), or name a voice directly.

2. User provided writing samples? Use the mirror voice. Study their samples and build a custom voice profile using the dimensions in voices.md. Don't describe the profile to them — just apply it. If they also show you writing they don't like, that's equally valuable. Study what makes it feel wrong to them.

3. Neither specified nor samples provided? Ask. Keep it quick and natural:

"Before I rewrite this — what voice do you want?

  • Clear thinker — smart person working through an idea. Direct, no decoration.
  • Casual storyteller — like telling a friend over coffee. Warm, loose, real.
  • Sharp & opinionated — strong takes, punchy sentences, zero hedging.
  • Warm professional — credible and polished but still sounds like a person.
  • Your voice — paste a sample of your writing and I'll match it.

Or just describe what you're going for and I'll adapt."

Wait for their answer before rewriting. Don't guess.

4. User says "just make it human" or seems impatient? Default to clear-thinker and go. Don't slow them down with questions if they just want results.

The Rewriting Process

Work through the text in three passes. Don't try to do everything at once.

Pass 1: Kill the AI Vocabulary

Go through the text word by word. Every time you hit a word from the Tier 1 or Tier 2 banned lists in the dictionary, replace it with the simpler human alternative. For Tier 3 transition words, check if they're clustered — more than 2 formal transitions in a short section is an AI tell. Replace clusters with simpler connectors or just delete them. Good writing often doesn't need explicit transitions at all.

Don't just swap synonyms mechanically. Sometimes the best fix is restructuring the whole sentence so the fancy word isn't needed in the first place.

Pass 2: Break the AI Structures

This pass matters more than vocabulary. AI models default to certain sentence and paragraph shapes because those shapes are statistically safe — they work everywhere and offend no one. That's exactly what makes them obvious. Scan for these patterns and break every single one.

Parallel negation ("Not X, but Y"): AI loves this rhetorical contrast because it sounds sophisticated. It appears 5-10x more in AI text than human text. Rewrite as a direct positive statement — just say what happened. Bad: "Not because I lacked skill, but because the context changed." Good: "The context changed, and I had to adapt."

Tricolons (groups of three): Models default to groups of three adjectives, nouns, or phrases because it sounds comprehensive. Humans rarely write this way outside of speeches. Pick the one or two items that actually matter, or find a completely different way to say it. Bad: "...collaboration, innovation, and problem-solving." Good: "...figuring things out together."

Em dash overuse: AI uses em dashes where humans would use commas, parentheses, or just split into two sentences. Wikipedia editors call it the "ChatGPT dash." Use commas, periods, or parentheses instead. Maximum 1 em dash per 500 words, and only for genuine emphasis.

Rhetorical Q + answer: AI uses this as a transition device every few paragraphs. Humans do it occasionally; AI does it constantly. State your point directly — lead with the answer, not the question. Bad: "What does this mean in practice? It means teams need autonomy." Good: "Teams need autonomy."

Mirror structures (A then B with same shape): Perfect structural symmetry in consecutive sentences is a model favorite. Break the symmetry — make the second item structurally different from the first. Let the second thought take a different shape, a different length, a different angle. Bad: "Engineers want clarity. Managers want context." Good: "Engineers want clarity. For managers, it's more about context — what's happening around the decision that you can't see from the outside."

Neat endings on every paragraph: AI wraps every thought in a bow. Real writing doesn't. Let at least 30% of paragraphs just stop without a tidy conclusion. Let some thoughts hang. Let the reader sit with an idea instead of being told what to think about it.

Dramatic reveals ("Here's the thing:", "The result?"): These are overused LinkedIn/content-marketing AI patterns. Drop the theatrical setup and start with the substance. Trust that the content is interesting enough without the drumroll.

Inflation of importance: AI puffs up the significance of everything — "pivotal moment," "crucial development," "testament to." It rarely just states a fact without editorializing about how important it is. Remove these sentences entirely. If something is important, the reader will get that from the content itself.

Watch for secondary convergence. When you avoid one AI pattern, don't fall into a new one to replace it. If you stopped using "Furthermore," don't start every transition with "That said" or "The thing is." Vary your approaches. Sometimes use no transition at all — just start the next thought. Sometimes restructure so the connection is implicit. The fix for a cliche is never another cliche.

Pass 3: Add Human Texture

This is where the text goes from "clean" to "real," and where the selected voice takes over. Apply the voice's specific guidance from references/voices.md for sentence rhythm, paragraph style, tone, transitions, and signature qualities. Then layer in these universal human-writing qualities:

Vary sentence length aggressively. Follow a long sentence with a short one. Then maybe two medium ones. Then a fragment. AI writes at a steady rhythm because it picks the most statistically likely pattern. Humans speed up and slow down. That variation is what makes writing feel alive.

Make less predictable word choices. AI picks the most probable next word, which makes the text feel flat and expected. Where AI would say "significant impact," a human might say "it changed everything" or "it broke the whole system." Reach for the specific, the concrete, the slightly unexpected. Not forced or weird — just less autopilot.

Start some sentences with "And" or "But." This is how people actually write when they're not worried about grammar rules. It creates a conversational rhythm that formal writing can't touch.

Leave some thoughts slightly unresolved. Not every idea needs a landing. Sometimes "I'm still figuring this out" is the most honest and compelling thing you can write. Let some ideas sit without wrapping them up.

Use specific details over generic ones. Replace "the initiative faced challenges" with "we burned through $40k and had nothing to show for it." Numbers, names, places, dates — specificity is what separates human writing from AI blandness.

Let the author's actual opinion show. AI hedges everything. Humans take positions. If the text is making an argument, let it actually argue. Remove "it could be argued that" and "some might say" and just say the thing.

Allow mild imperfections. A slightly awkward transition or an informal word choice is better than robotic perfection. Real writing has texture. Don't sand it down until it's smooth and lifeless.

Special Rules for LinkedIn Posts

LinkedIn is where AI writing gets spotted and punished the fastest — lower reach, lower engagement. Apply these extra rules:

  • Lead with the most interesting or provocative line. Not a setup, not context. The hook.
  • Keep sentences under 20 words on average. LinkedIn is read on phones.
  • Use line breaks liberally. One thought per line works well.
  • Write like you'd tell a story to a coworker, not like you're writing an essay.
  • No "thought leadership" framing. Don't say "I learned" or "key takeaway." Just tell what happened and what you think about it.
  • End with something real and unresolved, not a neat lesson. Vulnerability and honesty outperform polished conclusions on LinkedIn.

Quality Checklist (Run Before Returning)

Before presenting the rewritten text, verify every single item:

  • Zero Tier 1 banned words remain
  • Tier 2 words appear max once each, and only where truly natural
  • No more than 2 formal transition words in the entire piece
  • Zero parallel negation structures ("Not X, but Y")
  • Zero tricolons (groups of three)
  • Max 1 em dash per 500 words
  • No rhetorical question + answer combos
  • No mirror structures (consecutive sentences with identical shapes)
  • No dramatic reveals or theatrical setups
  • At least 30% of paragraphs don't end with a neat conclusion
  • Sentence length varies noticeably (mix of short, medium, long)
  • At least one sentence starts with "And" or "But"
  • The author's actual opinion is visible somewhere
  • No inflation of importance ("pivotal," "crucial," "testament")
  • No secondary convergence (same replacement used repeatedly)
  • Word choices include some less predictable, specific phrasing
  • Output matches the selected voice's rhythm, tone, and signature qualities
  • Reads like a real person talking, not a polished essay

What to Protect

Keep the meaning and factual content of the text intact. You're editing voice and style, not substance.

Keep the intelligence level. "Human" doesn't mean "dumbed down." Simple writing can be the smartest writing. Aim for clear and smart, not simplistic.

Keep it real. Don't over-correct into a different kind of artificiality. "Fellow humans, am I right?" is worse than AI writing. The goal is invisible editing — the reader should never think about how it was written at all.

Don't add emojis, hashtags, or engagement bait unless the user asks for it.

Just return the rewritten text. Don't explain your changes unless asked.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Humanize Writing AI skill do?

Use when the user wants text to sound more human, says writing sounds "too AI" or "too ChatGPT," asks to humanize or rewrite a draft to feel natural, or shares content wanting it to feel authentic and less robotic. Also applies to LinkedIn posts, blog drafts, or emails where the user wants a more genuine voice.

Why use Humanize Writing on TypingMind?

Because you install it once and use it with any model. Humanize Writing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Humanize Writing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lguz/humanize-writing-skill/tree/main/skills/humanize-writing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Humanize Writing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Humanize Writing?

As many as you like. As long as a model supports skills, you can use Humanize Writing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Humanize Writing AI skill free?

Yes. It is published on GitHub by lguz under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇