content-humanizer
Transform AI-generated content into authentic, human-sounding writing. Covers AI pattern detection, natural writing rhythm restoration, voice injection, brand personality application, and authenticity scoring. Use when content sounds robotic, uses AI cliches, lacks personality, reads like committee writing, or when user mentions AI content, make it human, add personality, sounds robotic, fix AI writing, content authenticity, AI detection, or humanize content.
What this skill does
# Content Humanizer
Transform machine-sounding content into writing that reads like it came from a real person with real opinions and real experience.
---
## Table of Contents
- [Keywords](#keywords)
- [Quick Start](#quick-start)
- [Core Workflows](#core-workflows)
- [AI Pattern Detection Catalog](#ai-pattern-detection-catalog)
- [Humanization Techniques](#humanization-techniques)
- [Voice Injection Framework](#voice-injection-framework)
- [Rhythm and Cadence Repair](#rhythm-and-cadence-repair)
- [Specificity Replacement Guide](#specificity-replacement-guide)
- [Before and After Examples](#before-and-after-examples)
- [Best Practices](#best-practices)
- [Integration Points](#integration-points)
---
## Keywords
content humanizer, AI content, humanize writing, AI detection, natural writing, authentic content, AI cliches, robotic writing, brand voice, personality injection, writing rhythm, AI patterns, content authenticity, human voice, AI tells, content polishing, voice consistency, writing style, content quality
---
## Quick Start
### Detect AI Patterns in Content
1. Scan for overused filler words (delve, landscape, crucial, leverage, robust)
2. Check for hedging chains ("It's important to note that...")
3. Count em-dash frequency (more than 2 per 500 words = AI fingerprint)
4. Evaluate paragraph structure uniformity (identical patterns = AI)
5. Flag all unattributed vague claims ("Many companies," "Studies show")
6. Score severity: High (10+ tells per 500 words = full rewrite needed)
### Humanize a Draft
1. Replace all filler words with plain-language alternatives
2. Vary sentence length deliberately (short, long, medium, fragment)
3. Replace every vague claim with a specific data point or honest qualification
4. Break uniform paragraph structure with fragments, questions, and asides
5. Add friction and imperfection (qualifications, direction changes, opinions)
6. Inject brand voice if voice guidelines exist
---
## Core Workflows
### Workflow 1: AI Pattern Audit (Diagnostic Only)
Scan content without editing. Produce an annotated report.
**Step 1: Run Detection Scan**
Flag every instance in these categories with severity ratings:
- Critical (kills credibility): Overused filler words, hedging chains, identical paragraph structure, lack of specificity
- Medium (softens impact): Em-dash overuse, false certainty, generic conclusions
- Minor (polish only): Slightly repetitive transitions, mild formatting uniformity
**Step 2: Count and Score**
| Metric | Threshold |
|--------|-----------|
| AI tells per 500 words | < 3 = minor edits needed, 3-7 = significant editing, 8+ = full rewrite |
| Unique paragraph structures | < 3 patterns in 1,000+ words = AI fingerprint |
| Vague claims without attribution | Any = flag each one |
| Sentences starting with "It is" | > 3 per 1,000 words = flag |
**Step 3: Deliver Audit Report**
```markdown
## AI Pattern Audit
Content: [Title or description]
Word count: [X]
AI Tell Count: [X] (Critical: [X], Medium: [X], Minor: [X])
Recommendation: [Minor edits / Significant editing / Full rewrite]
### Critical Issues
[Each issue with line reference, pattern category, and specific fix]
### Medium Issues
[Same format]
### Minor Issues
[Same format]
```
### Workflow 2: Full Humanization Pass
Transform the content from AI-sounding to authentically human.
**Step 1: Remove AI Filler Words**
Never just delete — always replace with something better or restructure the sentence:
| AI Phrase | Replacement Options |
|-----------|-------------------|
| "delve into" | "look at," "dig into," "break down," or restructure without the phrase |
| "the [X] landscape" | "how [X] works today," "the current state of [X]" |
| "leverage" | "use," "apply," "put to work" |
| "crucial" / "vital" / "pivotal" | State the thing and let it be self-evidently important |
| "furthermore" / "moreover" | Start the next sentence directly, or use "and" or "also" |
| "robust" / "comprehensive" | Replace with specific description of what it actually covers |
| "facilitate" / "foster" | "help," "make easier," "allow," "create" |
| "navigate this challenge" | "handle this," "deal with this," "get through this" |
| "in order to" | "to" |
| "it is important to note that" | Delete the phrase; start with the actual note |
| "it goes without saying" | If it goes without saying, do not say it |
| "at the end of the day" | Delete entirely or replace with specific conclusion |
| "a wide range of" | Specify the range or say "many" |
**Step 2: Fix Sentence Rhythm**
AI produces uniform sentence length (18-22 words per sentence). The ear goes numb.
Deliberately vary:
- Break long sentences into two
- Add a short sentence after a long one. Like this.
- Use fragments for emphasis. Especially for emphasis.
- Let some sentences run when the thought needs room to unwind
- Mix declarative, interrogative, and imperative forms
Target rhythm patterns:
- Long. Short. Long, long. Short.
- Question? Answer. Proof.
- Claim. Specific example. So what?
**Step 3: Replace Generic with Specific**
Every vague claim is an invitation to doubt:
Before: "Many companies have seen significant improvements by implementing this strategy."
After (if you have data): "HubSpot published their onboarding funnel data in 2023 — companies that hit first-value in 7 days showed 40% higher 90-day retention."
After (if you do not have data): "I don't have a controlled study to cite, but in every SaaS onboarding flow I've worked on, the pattern is the same: earlier activation = higher retention."
Honest qualification beats vague authority.
**Step 4: Vary Paragraph Structure**
Break the uniform pattern (Statement > Explanation > Example > Bridge):
- Single-sentence paragraph for emphasis
- Question paragraph: pose a question, then answer it
- List in the middle when items are genuinely parallel
- Aside or parenthetical that reveals personality
- Confession: "I got this wrong the first time"
- Fragment paragraph. Just one thought. Then move on.
**Step 5: Add Friction and Imperfection**
Real people:
- Change direction mid-thought: "Actually, let me back up..."
- Qualify things they are uncertain about
- Have opinions that might be wrong: "I might be wrong about this, but..."
- Notice things: "What's interesting here is..."
- React: "Which, if you've ever tried to debug this, you know is maddening."
- Acknowledge tradeoffs: "This works, but it costs you..."
### Workflow 3: Voice Injection
After removing AI patterns, inject the brand's specific personality.
**Step 1: Extract Voice from Examples**
If brand guidelines exist, reference them. If not, request one example of writing the brand loves. Extract:
- Sentence length preference (short punchy vs. flowing)
- Formality level (contractions, slang, jargon policy)
- Humor usage (dry wit, self-deprecating, none)
- Relationship stance (peer-to-peer, expert-to-student, provocateur)
- Signature phrases or patterns
**Step 2: Apply Voice Techniques**
| Technique | How to Apply |
|-----------|-------------|
| Personal anecdotes | "We saw this firsthand when building X" |
| Direct address | Talk to the reader as "you," not "users" or "teams" |
| Opinions without apology | "We think the industry is wrong about this" |
| The aside | Brief parenthetical showing you know more than you are saying |
| Rhythm signature | Match the sentence pattern from the brand's best examples |
| Controlled imperfection | Strategic fragments, direction changes, honest qualifications |
**Step 3: Consistency Check**
After voice injection, verify:
- Voice is consistent from intro to conclusion (no drift)
- Tone matches the content type (blog post vs. docs vs. email)
- Personality does not override clarity (if a joke obscures the point, cut the joke)
- The piece sounds like the same person wrote all of it
---
## AI Pattern Detection Catalog
### Category 1: Overused Filler Words (Critical)
These words appear disproportionately in AI-generated text:
**Tier 1 Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".