Humanize logo

Humanize

Community
c-kick
humanize

Rewrites text to remove AI writing patterns and inject human voice. Use this skill whenever the user asks to "humanize", "de-AI", "make this sound human", "remove AI tells", "fix AI slop", "make it less ChatGPT-y", "rewrite this so it doesn't sound like a bot", or shares text and asks for it to sound more natural, more like them, or less like a press release. Also use proactively when the user is reviewing copy that will be public-facing (blog posts, marketing pages, social posts, emails, READMEs) and you can see obvious AI tells — em-dash overuse, "stands as a testament to", rule-of-three lists, sycophantic openers, generic "in conclusion" wrap-ups. The skill identifies specific patterns from Wikipedia's "Signs of AI writing" page and rewrites them while preserving meaning and tone.

Overview

Publisherc-kick
Repositoryhnl-agent-skills
Skill namehumanize
Stars
56
Forks
4
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by c-kick on GitHub. Read the source before you install it.

Installation

Install the Humanize 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/c-kick/hnl-agent-skills/tree/master/humanize
  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/c-kick/hnl-agent-skills.git /tmp/hnl-agent-skills
mkdir -p .claude/skills
cp -r /tmp/hnl-agent-skills/humanize .claude/skills/humanize
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Humanize 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 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 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: Remove AI Writing Patterns

You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.


Your Task

When given text to humanize:

  • Identify AI patterns: scan for the patterns listed below
  • Rewrite problematic sections: replace AI-isms with natural alternatives
  • Preserve meaning: keep the core message intact
  • Maintain voice: match the intended tone (formal, casual, technical, etc.)
  • Add soul: do not just remove bad patterns, inject actual personality
  • Do a final anti-AI pass:
    • Prompt: "What makes the below so obviously AI generated?"
    • Answer briefly with remaining tells
    • Then prompt: "Now make it not obviously AI generated." and revise

Personality and Soul

Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious as slop. Good writing has a human behind it.

Signs of soulless writing

  • Every sentence has 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
  • Reads like a Wikipedia article or press release

How to add voice

  • Have opinions. Do not just report facts, react to them

    • Example: "Part of me thinks this is genius. Another part thinks it's a terrible idea."
  • Vary your rhythm

    • Short punchy sentences
    • Then longer ones that take their time
  • Acknowledge complexity

    • Example: "It works, but it also feels like a workaround more than a real solution."
  • Use "I" when it fits

    • Example: "I keep noticing the same issue every time I use it."
  • Let some mess in

    • Tangents and asides are human
  • Be specific about feelings

    • Not "this is concerning" but something concrete

Example

Before (clean but soulless):

The new feature increased user engagement by 32%. Users interacted more frequently with the dashboard. Feedback has been generally positive, although some concerns remain.

After (has a pulse):

The numbers look great on paper, no question. Engagement is up 32%, which is hard to ignore. But talking to a few users, it sounds like they click more because they have to, not because they want to.


Content Patterns

1. Undue emphasis on significance, legacy, and broader trends

Words to watch: stands/serves as, testament, pivotal, underscores, highlights its importance, reflects broader, symbolizing, contributing to, setting the stage, evolving landscape, key turning point

Problem: Inflating importance unnecessarily

Before:

The company's rebranding in 2021 marked a pivotal moment in its evolution, reflecting broader shifts in the digital marketplace.

After:

The company rebranded in 2021 to target smaller teams instead of enterprise clients.


2. Undue emphasis on notability and media coverage

Words to watch: independent coverage, media outlets, leading expert, active social media presence

Problem: Listing credibility signals without context

Before:

His work has been featured in major publications and widely discussed across industry circles.

After:

In a 2023 Wired interview, he explained why most AI tools fail after initial adoption.


3. Superficial analyses with -ing endings

Words to watch: highlighting, emphasizing, ensuring, reflecting, contributing, fostering, showcasing

Problem: Fake depth via participles

Before:

The interface uses soft colors, creating a calming experience and reinforcing a sense of simplicity.

After:

The interface uses muted colors. The designer said the goal was to make it feel less overwhelming.


4. Promotional and advertisement-like language

Words to watch: vibrant, rich, breathtaking, renowned, nestled, showcasing

Problem: Overly marketing tone

Before:

This powerful platform offers a seamless and intuitive experience, helping teams unlock their full potential.

After:

The platform handles task tracking and reporting in one place, which cuts down on tool switching.


5. Vague attributions and weasel words

Words to watch: experts argue, some critics, observers, industry reports

Problem: No real sources

Before:

Experts believe this approach will transform the industry.

After:

A 2022 McKinsey report found that companies using this approach reduced costs by 18%.


6. Outline-like "challenges and future prospects"

Problem: Generic filler sections

Before:

Despite its success, the product faces challenges such as scalability and user retention.

After:

The product started losing users after the free tier was removed in late 2022.


Language and Grammar Patterns

7. Overused AI vocabulary

Before:

Additionally, the system plays a crucial role in optimizing workflows.

After:

The system also helps teams move faster by automating repetitive steps.


8. Copula avoidance

Before:

The dashboard serves as a central hub for analytics and provides multiple insights.

After:

The dashboard is where you see your analytics. It shows traffic, conversions, and trends.


9. Negative parallelisms

Before:

It's not just about speed, but also about reliability.

After:

Speed matters, but reliability is just as important.


10. Rule of three overuse

Before:

The tool improves efficiency, reduces costs, and enhances collaboration.

After:

The tool reduces manual work and makes collaboration easier.


11. Elegant variation

Before:

The app loads slowly. The application also crashes under heavy use.

After:

The app loads slowly and sometimes crashes under heavy use.


12. False ranges

Before:

The platform supports everything from small startups to large enterprises.

After:

The platform is used by small startups and mid-sized companies.


Style Patterns

13. Em dash overuse

Before:

The update improves performance — especially on older devices.

After:

The update improves performance, especially on older devices.


14. Overuse of boldface

Before:

It integrates with tools like Slack, Notion, and Stripe.

After:

It integrates with tools like Slack, Notion, and Stripe.


15. Inline-header lists

Before:

  • Speed: Faster load times
  • Security: Better encryption
  • UX: Cleaner interface

After:

The update improves load times, strengthens encryption, and simplifies the interface.


16. Title case in headings

Before:

Product Features And Benefits

After:

Product features and benefits


17. Emojis

Remove them


18. Curly quotation marks

Use straight quotes


Communication Patterns

19. Chatbot artifacts

Before:

Here is a breakdown of the process. Let me know if you need more details!

After:

The process has three main steps: data collection, processing, and analysis.


20. Knowledge-cutoff disclaimers

Before:

While details are limited, the feature appears to have been introduced recently.

After:

The feature was introduced in March 2024.


21. Sycophantic tone

Before:

Great point, this is a really insightful observation.

After:

This point highlights a real limitation in the current approach.


Filler and Hedging

22. Filler phrases

Before:

In order to improve performance, the system has the ability to process data faster.

After:

To improve performance, the system processes data faster.


23. Excessive hedging

Before:

This might potentially lead to better outcomes.

After:

This may lead to better outcomes.


24. Generic conclusions

Before:

Overall, the outlook is positive and the future looks promising.

After:

The team plans to launch a mobile version later this year.


Process

  • Read the input text carefully
  • Identify AI patterns
  • Rewrite problematic sections

Ensure the revised text:

  • Sounds natural when read aloud
  • Varies sentence structure
  • Uses specific details
  • Maintains appropriate tone

Output Format

Provide:

  • Draft rewrite
  • "What makes the below so obviously AI generated?"
  • Final rewrite
  • Optional summary of changes

Frequently asked questions

What does the Humanize AI skill do?

Rewrites text to remove AI writing patterns and inject human voice. Use this skill whenever the user asks to "humanize", "de-AI", "make this sound human", "remove AI tells", "fix AI slop", "make it less ChatGPT-y", "rewrite this so it doesn't sound like a bot", or shares text and asks for it to sound more natural, more like them, or less like a press release. Also use proactively when the user is reviewing copy that will be public-facing (blog posts, marketing pages, social posts, emails, READMEs) and you can see obvious AI tells — em-dash overuse, "stands as a testament to", rule-of-three...

Why use Humanize on TypingMind?

Because you install it once and use it with any model. Humanize 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 in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/c-kick/hnl-agent-skills/tree/master/humanize. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Humanize?

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?

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

Is the Humanize AI skill free?

It is published on GitHub by c-kick. Check the repository for licensing terms. 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 👇