Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring.
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills content-humanizer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "content-humanizer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizer into .claude/skills/content-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-humanizer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills content-humanizer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/content-humanizer .agents/skills/content-humanizer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-humanizer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizer into .agents/skills/content-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-humanizer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills content-humanizer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/content-humanizer .cursor/skills/content-humanizer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-humanizer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizer into .cursor/skills/content-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-humanizer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path marketing/content-humanizer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills content-humanizer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/content-humanizer .gemini/skills/content-humanizer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-humanizer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizer into .gemini/skills/content-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-humanizer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills content-humanizerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/content-humanizer .github/skills/content-humanizer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-humanizer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizer into .github/skills/content-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-humanizer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill content-humanizer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills content-humanizer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/content-humanizer .opencode/skills/content-humanizer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-humanizer" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/content-humanizer into .opencode/skills/content-humanizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-humanizer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
content-humanizerTransform 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. 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.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
digital-strategy.ec.europa.euFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,930 words, ~5,727 tokens.
.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.Transform machine-sounding content into writing that reads like it came from a real person with real opinions and real experience.
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
Before humanizing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
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.
Scan content without editing. Produce an annotated report.
Step 1: Run Detection Scan
Flag every instance in these categories with severity ratings:
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
## 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]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:
Target rhythm patterns:
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):
Step 5: Add Friction and Imperfection
Real people:
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:
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:
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
AI hedges constantly because it does not want to be wrong:
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.
AI replaces specific claims with vague ones to avoid being wrong:
One or two em-dashes per piece: fine. Em-dash in every other paragraph: AI fingerprint.
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?
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.
AI writing has metronomic consistency. Every sentence is roughly the same length. The reader's attention flatlines.
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.
| Pattern | When 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 |
Every vague claim must become either specific or honestly qualified. There is no third option.
| Vague | Specific Alternative | Honest 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 (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.
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.
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.
Preserve what works — Some AI-generated paragraphs are genuinely good. Flag them before rewriting so you do not accidentally destroy the best parts.
Do not over-humanize — Adding too much personality to technical documentation makes it harder to use. Match the humanity level to the content type.
Get voice context first — Guessing the brand voice and being wrong wastes time. Ask for one example of writing they love before injecting personality.
Read aloud — The single most effective test. If it sounds like a press release when read aloud, it is not human enough.
Replace, do not just delete — Removing "furthermore" leaves a gap. Replace with a better transition or restructure the flow.
Specific beats clever — A specific data point does more for credibility than a witty phrase. Prioritize substance over style.
Consistency over personality — A mildly interesting but consistent voice beats a wildly creative voice that shifts every paragraph.
One pass at a time — Detect first, humanize second, inject voice third. Trying to do all three simultaneously produces inconsistent results.
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.
| Problem | Likely Cause | Fix |
|---|---|---|
| Content still sounds AI-generated after humanization pass | Only surface-level word replacements done — structural uniformity and hedging patterns remain | Run all three passes in order: filler removal, rhythm repair, specificity replacement. Address structure, not just words |
| Brand voice inconsistent after editing | Voice injection done without reference examples or clear guidelines | Request one example of writing the brand loves before injecting voice; extract formality, humor, and relationship stance |
| Over-humanized technical documentation | Personality injection applied to content that needs clarity over personality | Match humanization level to content type — docs need clarity; blog posts and marketing copy need personality |
| Specificity gaps flagged but cannot be filled | Writer does not have access to real data, expert quotes, or original research | Flag clearly as "author must provide" — humanizer cannot invent proof points. Honest qualification beats vague authority |
| Reviewers still say the piece reads as robotic | Structural patterns (SEEB uniformity) persist despite word-level changes | Vary paragraph structures deliberately — single-sentence paragraphs, questions, fragments, asides. Judge by reader quality, not by AI-detector scores |
| Readability dropped after humanization | Informal language and fragments reduced Flesch score | Balance personality with readability — fragments are fine but complex vocabulary can hurt scores. Target Flesch 60-70 |
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.
In scope:
Out of scope:
Known limitations:
# 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
SKILL.md and 3 other files (scripts) in marketing/content-humanizer of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Humanizer this skillborghei/Claude-Skills | 881 | — | ~5.7k | Automated safety check: Pass | MIT | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 172 | 37 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Install Anti Sloptrycompai/crm | 11k | 1 repos | ~881 | Automated safety check: Pass | MIT | |
| Stop SlopXe/site | 732 | 8 repos | ~423 | Automated safety check: Pass | MIT |
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
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.
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
Xe/site
Remove AI writing patterns from prose. An agent skill from Xe/site.
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.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
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.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
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.
Content Humanizer fits situations like: content sounds robotic; uses AI cliches; the user wants to humanize.
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.
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.
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.
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.
SKILL.md names 1 domain. As links in the text: digital-strategy.ec.europa.eu. This is read from the text; nothing was executed.
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.
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.
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.
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.
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.