agentleFS
shali10shali10/awesome-agent-skills/skills/humanizer/SKILL.md

humanizer

Skill1 starsChanged 2 months agoMITView on GitHub

Use when stripping AI writing patterns, corporate fluff, and synthetic tone from drafts to restore natural human cadence.

188 other projects use a version of this.

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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 1

    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:

    Changing factual meaning during simplification: Ensure technical parameters, numbers, and commands remain identical.

    line 42

“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

Text Humanizer & Anti-AI Tone Filter

Overview

A specialized text purification skill that systematically scans, detects, and purges syntactic and semantic markers of LLM-generated text, transforming stiff output into natural, authentic human communication.

When to Use & When NOT to Use

When to Use

  • Rewriting LLM output for developer blogs, emails, announcements, and documentation.
  • Removing excessive hedging ("it may be beneficial to consider...") and passive voice.
  • Enforcing concise, punchy technical communication.

When NOT to Use

  • Translating structured data tables or code blocks.
  • Tasks requiring formal academic third-person passive syntax.

Transformation Matrix

LLM PatternWhy It Feels SyntheticTransformation Strategy
Sycophantic Agreement"You make a great point! Absolutely..."Delete entirely; answer the question directly
Rule-of-Three Adjectives"Seamless, robust, and scalable solution"Use one precise, factual description
Passive Hedging"It could potentially be argued that...""In our tests, X caused Y."
Synthetic Summaries"By following these steps, you will unlock..."Replace with a concise summary table or next actions

Common Pitfalls

  1. Replacing AI fluff with informal slang: Maintain professional engineering rigor while removing robotic phrasing.
  2. Changing factual meaning during simplification: Ensure technical parameters, numbers, and commands remain identical.

Verification Checklist

  • Removed all instances of sycophantic opening filler.
  • Converted passive hedges into direct, verifiable statements.
  • Maintained 100% of original technical facts and parameter values.

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.