Agent skill

Content Humanizer

by borghei in borghei/Claude-Skills

Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring.

MITAuto-check passedWriting & Content

Install Content Humanizer

skills CLI
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills content-humanizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/content-humanizer .claude/skills/content-humanizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
content-humanizer
GitHub stars
881
Token cost
~5.7k tokens
SKILL.md length
2,930 words
Files
4 (incl. scripts)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring.

  • Works in 6 steps: Scan for overused filler words (delve,… → Check for hedging chains ("It's… → Count em-dash frequency (more than 2 per… → …
  • Content sounds robotic
  • SKILL.md covers Table of Contents, Keywords, Clarify First and Quick Start, plus 6 more sections
  • Runs Python scripts from its folder; calls python

What it does

Content Humanizer is an agent skill from borghei/Claude-Skills. Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring. Use when content sounds robotic, uses AI cliches, or the user wants to humanize or fix AI writing.

Its SKILL.md is about 5.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/ai_pattern_detector.py`, `scripts/content_scorer.py` and `scripts/readability_scorer.py`).

It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Content sounds robotic
  • Uses AI cliches
  • The user wants to humanize

Example prompts

  • “/content-humanizer”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  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)

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • digital-strategy.ec.europa.eu

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Content Humanizer loads about 5.7k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 2,930 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,930 words, ~5,727 tokens.

Download SKILL.mdSave it as .claude/skills/content-humanizer/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
content-humanizer
description
Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring. Use when content sounds robotic, uses AI cliches, or the user wants to humanize or fix AI writing.
license
MIT
metadata.version
1.0.0
metadata.author
borghei
metadata.category
marketing
metadata.domain
content
metadata.updated
2026-09-21

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

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


Clarify First

Before humanizing, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Mode — audit-only (annotated report) or full humanization rewrite (sets the deliverable and how invasive edits are)
  • Content type — docs, blog post, marketing copy, or email (determines how much personality to inject vs. preserve clarity)
  • Brand voice — guidelines or one example of writing they love (without it, voice injection is guesswork)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

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

MetricThreshold
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 attributionAny = 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 PhraseReplacement 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

TechniqueHow to Apply
Personal anecdotes"We saw this firsthand when building X"
Direct addressTalk to the reader as "you," not "users" or "teams"
Opinions without apology"We think the industry is wrong about this"
The asideBrief parenthetical showing you know more than you are saying
Rhythm signatureMatch the sentence pattern from the brand's best examples
Controlled imperfectionStrategic 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 — Instant Tells: delve, landscape (metaphorical), crucial, vital, pivotal, leverage, robust, comprehensive, holistic, foster, facilitate, ensure, navigate (metaphorical), utilize, furthermore, moreover, in addition

Tier 2 — Suspicious in Clusters: streamline, optimize, innovative, cutting-edge, game-changer, paradigm, synergy, ecosystem, empower, unlock, harness, transformative, seamless

Category 2: Hedging Chains (Critical)

AI hedges constantly because it does not want to be wrong:

  • "It's important to note that..."
  • "It's worth mentioning that..."
  • "One might argue that..."
  • "In many cases," "In most scenarios,"
  • "It goes without saying..."
  • "Needless to say..."
Category 3: Structural Uniformity (Critical)

Every paragraph follows the same SEEB pattern: Statement > Explanation > Example > Bridge

Real writing varies. Some paragraphs are one sentence. Some are lists. Some are questions followed by answers. Some digress and come back.

Category 4: Specificity Vacuum (Critical)

AI replaces specific claims with vague ones to avoid being wrong:

  • "Many companies" (which ones?)
  • "Studies show" (which studies?)
  • "Significantly improved" (by how much?)
  • "Leading brands" (name one)
  • "A growing number of" (how many?)
  • "Best practices suggest" (whose best practices?)
Category 5: Em-Dash Overuse (Medium)

One or two em-dashes per piece: fine. Em-dash in every other paragraph: AI fingerprint.

Category 6: False Certainty (Medium)

AI asserts confidently about things nobody can be certain about. "Companies that do X are more successful." According to what data? Based on what sample size?

Category 7: Generic Conclusions (Medium)

AI conclusions restate the introduction: "In this article, we explored X, Y, and Z. By implementing these strategies, you can achieve..."

No human concludes like this. Real conclusions add something new or nail the exit line.


Rhythm and Cadence Repair

The Problem

AI writing has metronomic consistency. Every sentence is roughly the same length. The reader's attention flatlines.

The Fix

Map sentence lengths and deliberately vary them:

Before (AI rhythm):

Content marketing is an essential strategy for modern businesses. It helps build trust with potential customers over time. Creating high-quality content requires careful planning and execution. The most effective content strategies combine data-driven insights with creative storytelling.

Every sentence: 8-10 words. Same structure. Same length.

After (human rhythm):

Content marketing works. Not because it is clever — because it builds trust before you ever ask for a sale. That takes time. It takes planning. And honestly? It takes more failed drafts than anyone likes to admit. But the companies that figure it out — the ones that combine real data with stories that actually land — they win. Not quickly. But permanently.

Mixed length. Fragments. Questions. Repetition for emphasis. Direction changes.

Rhythm Patterns to Use
PatternWhen to Use
Long. Short.After complex explanation, punch with a short statement
Question? Answer.Engage the reader, then satisfy the curiosity
Claim. Evidence. So what?Make a point, prove it, explain why it matters
List. Then prose.Present options or items, then return to narrative
Confession. Lesson.Admit a mistake, extract the learning

Specificity Replacement Guide

The Rule

Every vague claim must become either specific or honestly qualified. There is no third option.

Replacement Patterns
VagueSpecific AlternativeHonest Qualification
"Many companies""In a 2024 Gartner survey of 1,200 enterprises""In the teams I've worked with"
"Studies show""A Stanford study published in Nature (2023)""I haven't seen controlled studies, but the pattern is..."
"Significant improvement""A 34% reduction in churn over 6 months""Noticeable improvement — I'd estimate 20-30% range"
"Industry leaders""Stripe, Notion, and Linear""The companies I'd point to as examples"
"Best practices""[Organization]'s published framework recommends""What I've seen work consistently"
"Growing trend""Adoption grew from 12% to 47% between 2022 and 2025""Anecdotally, I'm seeing more teams try this"

Before and After Examples

Example 1: SaaS Product Description

Before (AI-generated):

It is crucial to leverage your existing customer data in order to effectively navigate the competitive landscape. Furthermore, by implementing a robust onboarding strategy, organizations can ensure that users achieve maximum value from the product and reduce churn significantly.

After (humanized):

Here's the thing nobody says out loud: most SaaS companies have the data to fix their churn problem. They just do not look at it until after customers leave.

Your activation funnel tells you everything. Your best cohorts, your worst, the exact moment the drop-off happens. You do not need another tool — you need someone to stop ignoring what the tool is already showing you.

Nail onboarding first. Everything else is downstream.

Show full SKILL.md (1,120 more words)Show less
Example 2: Marketing Blog Post

Before (AI-generated):

In the rapidly evolving landscape of digital marketing, it is essential for businesses to leverage cutting-edge strategies to stay ahead of the competition. By implementing a comprehensive content marketing approach, organizations can foster meaningful connections with their target audience and drive sustainable growth.

After (humanized):

Digital marketing changes fast. That part is true. But the companies that actually grow? They are not chasing every new tactic. They are doing the boring stuff well.

Write content people want to read. Answer questions your customers actually ask. Do it consistently for 12 months. It is not exciting advice. But it works — and the "cutting-edge strategies" usually do not.


Best Practices

  1. Audit before editing — Know what is wrong before you fix it. A piece with 3 AI tells needs polish. A piece with 15 needs a rewrite. The approach is different.

  2. Preserve what works — Some AI-generated paragraphs are genuinely good. Flag them before rewriting so you do not accidentally destroy the best parts.

  3. Do not over-humanize — Adding too much personality to technical documentation makes it harder to use. Match the humanity level to the content type.

  4. Get voice context first — Guessing the brand voice and being wrong wastes time. Ask for one example of writing they love before injecting personality.

  5. Read aloud — The single most effective test. If it sounds like a press release when read aloud, it is not human enough.

  6. Replace, do not just delete — Removing "furthermore" leaves a gap. Replace with a better transition or restructure the flow.

  7. Specific beats clever — A specific data point does more for credibility than a witty phrase. Prioritize substance over style.

  8. Consistency over personality — A mildly interesting but consistent voice beats a wildly creative voice that shifts every paragraph.

  9. One pass at a time — Detect first, humanize second, inject voice third. Trying to do all three simultaneously produces inconsistent results.

  10. Flag the specificity gap — You can make prose flow better, but you cannot invent proof points. If the piece makes five vague claims with zero data, the author needs to provide the specifics. Flag this clearly.


Integration Points

  • Content Production — Use to create the initial draft. Run Content Humanizer after drafting, before SEO optimization.
  • Copywriting — Use for conversion copy (landing pages, CTAs, headlines). Content Humanizer works on longer-form pieces.
  • Content Strategy — Use when deciding what content to create. Not for voice or draft execution.
  • AI SEO — Use after humanizing to optimize for AI search citation. Human-sounding content gets cited more, but still needs structure for extraction.
  • Brand Guidelines — Reference brand voice and personality standards before voice injection.
  • Copy Editing — Use after humanization for grammar, fact-checking, and editorial consistency passes.

Troubleshooting

ProblemLikely CauseFix
Content still sounds AI-generated after humanization passOnly surface-level word replacements done — structural uniformity and hedging patterns remainRun all three passes in order: filler removal, rhythm repair, specificity replacement. Address structure, not just words
Brand voice inconsistent after editingVoice injection done without reference examples or clear guidelinesRequest one example of writing the brand loves before injecting voice; extract formality, humor, and relationship stance
Over-humanized technical documentationPersonality injection applied to content that needs clarity over personalityMatch humanization level to content type — docs need clarity; blog posts and marketing copy need personality
Specificity gaps flagged but cannot be filledWriter does not have access to real data, expert quotes, or original researchFlag clearly as "author must provide" — humanizer cannot invent proof points. Honest qualification beats vague authority
Reviewers still say the piece reads as roboticStructural patterns (SEEB uniformity) persist despite word-level changesVary paragraph structures deliberately — single-sentence paragraphs, questions, fragments, asides. Judge by reader quality, not by AI-detector scores
Readability dropped after humanizationInformal language and fragments reduced Flesch scoreBalance personality with readability — fragments are fine but complex vocabulary can hurt scores. Target Flesch 60-70
Compliance Note: Humanizing Is Not Hiding Provenance

This skill improves voice, clarity, and specificity. It is not a tool for removing watermarks (e.g., SynthID) or defeating AI-content detection, and should not be used to conceal AI involvement where disclosure is required.

  • EU AI Act Article 50 applies from 2 August 2026 (as of September 2026). Providers of generative AI systems must mark outputs in a machine-readable, detectable way (Art. 50(2); systems already on the market before 2 August 2026 have until 2 December 2026). Deployers must disclose deepfakes and label AI-generated or manipulated text published to inform the public on matters of public interest — unless the text has undergone genuine human review or editorial control by someone who holds editorial responsibility (Art. 50(4)). Spell-checking or a light pass does not count as that review. Source: European Commission — Transparency obligations under Article 50.
  • Platform and client rules — many ad platforms, publishers, and clients require AI disclosure for synthetic images, video, or endorsements regardless of how the text reads.
  • Practical rule: if disclosure is required, keep it. Humanize the writing; do not strip provenance labels, metadata, or watermarks. When in doubt, route to legal review.

Success Criteria

  • AI tell density: Fewer than 3 AI tells per 500 words after humanization pass (from baseline of 8+ pre-edit)
  • Unique paragraph structures: At least 4 distinct paragraph patterns in any 1,000-word piece (vs. uniform SEEB pattern)
  • Specificity rate: Zero vague claims remaining without either specific data or honest qualification
  • Voice consistency: Consistent formality level, humor usage, and relationship stance from introduction to conclusion
  • Read-aloud test: Content sounds natural when read aloud — no press-release cadence or robotic phrasing
  • Readability maintenance: Flesch Reading Ease stays within 55-75 range after humanization (no degradation)
  • Brand voice match: Content passes brand voice review with 90%+ alignment to documented voice guidelines

Scope & Limitations

In scope:

  • AI pattern detection and audit (diagnostic only or with edits)
  • Filler word replacement with context-appropriate alternatives
  • Sentence rhythm and cadence repair
  • Paragraph structure diversification
  • Specificity replacement (vague claims to specific or honestly qualified)
  • Voice injection from brand guidelines or example content
  • Consistency checking across full-length pieces

Out of scope:

  • Content creation from scratch (use Content Production)
  • Grammar and spelling correction (use Copy Editing)
  • SEO optimization (use SEO Specialist or Content Production optimization pass)
  • Content strategy or topic selection (use Content Strategy)
  • AI content generation or LLM API integration
  • Plagiarism detection or originality verification

Known limitations:

  • Cannot add specificity where no data exists — must flag for author input
  • Third-party AI-text detectors are unreliable and produce false positives — do not use their scores as a quality target
  • Voice injection without clear brand guidelines produces inconsistent results
  • Humanization of very short content (<300 words) may not have enough surface area for meaningful improvement
  • Out of scope: removing watermarks or provenance markers (e.g., SynthID, C2PA metadata) — see the Compliance Note above

Scripts

bash
# Score content for AI patterns and generate audit report
python scripts/readability_scorer.py article.md --json

# Detect AI filler words and hedging patterns with counts
python scripts/ai_pattern_detector.py article.md --verbose

# Analyze content for humanization opportunities
python scripts/content_scorer.py article.md --json

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in marketing/content-humanizer of borghei/Claude-Skills.

  • SKILL.md
  • scripts/ai_pattern_detector.py
  • scripts/content_scorer.py
  • scripts/readability_scorer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Content Humanizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Content Humanizer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Humanizer this skillborghei/Claude-Skills881—~5.7kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17237 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT
Install Anti Sloptrycompai/crm11k1 repos~881Automated safety check: PassMIT
Stop SlopXe/site7328 repos~423Automated safety check: PassMIT

Similar skills

  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    172 GitHub starsUsed in 37 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed
  • Stop Slop

    Xe/site

    Remove AI writing patterns from prose. An agent skill from Xe/site.

    732 GitHub starsUsed in 8 repos~423 tokens
    Writing & ContentAuto-check passed
  • Korean AI-Text Humanizer

    epoko77-ai/im-not-ai

    Diagnoses and rewrites Korean text that reads as AI-generated, fixing translationese and mechanical parallelism across 85 patterns in 10 categories, with light to heavy passes.

    5.9k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Questions about Content Humanizer

What does Content Humanizer do?

Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring. Content Humanizer is an agent skill from borghei/Claude-Skills. Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring.

When should I use Content Humanizer?

Content Humanizer fits situations like: content sounds robotic; uses AI cliches; the user wants to humanize.

How do I install Content Humanizer in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill content-humanizer -a claude-code`. Or copy the skill folder (marketing/content-humanizer in borghei/Claude-Skills) into .claude/skills/content-humanizer in your project. Claude Code loads it when a task matches its description.

How do I install Content Humanizer in Codex?

Run `npx skills add borghei/Claude-Skills --skill content-humanizer -a codex`. Or copy the skill folder (marketing/content-humanizer in borghei/Claude-Skills) into .agents/skills/content-humanizer in your project. Codex loads it when a task matches its description.

Can I use Content Humanizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill content-humanizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-humanizer, .gemini/skills/content-humanizer, .github/skills/content-humanizer and .opencode/skills/content-humanizer in your project.

What does Content Humanizer need to run?

Going by SKILL.md and its folder, Content Humanizer needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Content Humanizer access the network?

SKILL.md names 1 domain. As links in the text: digital-strategy.ec.europa.eu. This is read from the text; nothing was executed.

Is Content Humanizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Content Humanizer use?

Content Humanizer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Humanizer use?

About 5.7k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Content Humanizer?

Skills that share tags, products or a category with Content Humanizer: Humanizer (Azure-Samples/interview-coach-agent-framework, 172 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), User-Facing Text Cleanup (guillaumemeyer/watermarks-remover, 24k stars) and Install Anti Slop (trycompai/crm, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Humanizer?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.