mcpField
C
content-humanizer

content-humanizer

github.com/oakossMarketing & growth20217 installsUpdated 11w ago
Repository

About content-humanizer

A writing skill for revising AI-generated prose, aimed at writers and teams preparing blogs, marketing copy, email, and narrative documentation. It focuses on rhythm, audience and brand voice, and removing formulaic patterns rather than changing technical text.

Key features

  1. 01Vary sentence rhythm and paragraph structure
  2. 02Rewrite passive and abstract phrasing
  3. 03Calibrate tone to audience and brand
  4. 04Remove formulaic AI writing patterns
  5. 05Preserve organization while revising prose

Use cases

  1. 01Polish an AI-drafted blog post
  2. 02Adapt marketing copy to a brand voice
  3. 03Improve narrative documentation readability
  4. 04Revise robotic-sounding email campaigns

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/oakoss/agent-skills --skill content-humanizer

After installing, type/content-humanizerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
advanced-patterns.md
ai-pattern-removal.md
tone-and-voice.md
writing-patterns.md

Details

From the project README

Content Humanizer

Overview

Content humanizer transforms AI-generated prose into writing that reads as natural and intentional. It covers sentence rhythm, tone calibration, audience adaptation, and systematic removal of patterns that signal machine authorship. Applies to blog posts, marketing copy, email campaigns, narrative documentation, and any long-form prose.

When to use: Polishing AI-drafted blog posts, adapting marketing copy for a specific brand voice, improving readability of narrative documentation, rewriting content that feels robotic or formulaic.

When NOT to use: On code or technical specifications where precision matters more than voice. On content that was already human-written and reads naturally. For removing AI artifacts from code comments or READMEs (use the de-slopify skill instead).

Quick Reference

PatternTechniqueKey Points
Flat rhythmSentence variationMix short (5-word) and long (20+ word) sentences
Passive voiceActive rewritingSubject performs the action; aim for 80-90% active
Abstract claimsConcrete languageReplace "significant improvement" with specific numbers
Hedging phrasesDirect assertionDelete "it's worth noting" and state the fact
Filler vocabularyPlain language"utilize" becomes "use", "leverage" becomes "use"
Over-qualificationConfident toneRemove unnecessary caveats and balanced-to-a-fault phrasing
List addictionProse conversionConvert mechanical bullet lists into flowing paragraphs
Generic transitionsContextual connectorsReplace "furthermore" and "moreover" with idea-specific links
Uniform paragraphsVaried structureBreak predictable paragraph lengths and opening patterns
Missing voiceBrand calibrationDefine audience, formality level, and personality before editing
No E-E-A-T signalsExperience injectionAdd first-person anecdotes, specific data, authoritative sources
Low burstinessLength variationAlternate 3-word and 25-word sentences to break uniformity
Low perplexityWord unpredictabilityReplace formulaic phrases with domain-specific, concrete language

Common Mistakes

MistakeCorrect Pattern
Replacing AI words with a thesaurusRewrite the sentence; synonym swaps create awkward phrasing
Removing all structure to sound casualKeep headings and organization; rewrite prose within the structure
Over-correcting into choppy fragmentsRead aloud after editing; recombine sentences that lost flow
Editing without defining target voiceSet persona, audience, and formality level before starting
Treating humanization as a single passUse multiple passes: structure, then voice, then polish
Making every sentence short and punchyVary length deliberately; monotone short sentences feel robotic too
Adding personality through exclamation marksVoice comes from word choice and rhythm, not punctuation
Ignoring paragraph-level patternsAI writes uniform paragraphs; vary length and opening structure

Delegation

  • Scan a repository for prose files that need humanization: Use Explore agent
  • Rewrite an entire blog or documentation site: Use Task agent
  • Define a brand voice guide and editorial standards: Use Plan agent

If the de-slopify skill is available, delegate code comment cleanup and technical writing artifact removal to it. Otherwise, recommend: npx skills add oakoss/agent-skills --skill de-slopify

References

Comments

Markdown supported