tekkiiiii/the-agency/humanizer

Claude Code and agent skill by tekkiiiii/the-agency

Trust tier 2
  • community
  • ext:[{"type":"config","description":"Configuration overrides"}]
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Rewrite AI-sounding text so it reads naturally without changing what it says. Use when editing or reviewing prose for inflated claims, sales language, vague sources, repetitive structure, stock AI words, passive voice, filler, or chatbot artifacts. Calibrates output to document type (CV, LinkedIn post, blog, email, etc.) so a CV bullet stays tight and parallel while a blog post gets natural rhythm. Based on Wikipedia's "Signs of AI writing."

Install

npx vskill@latest install tekkiiiii/the-agency/humanizer

Semi-extensibleMentions customization, but needs skill-specific knowledge. Read the extensible skills standard

SKILL.md

The same SKILL.md was published earlier as tekkiiiii/the-agency/humanizer.

Humanizer: remove AI writing patterns

Rewrite AI-sounding text so it reads like the writer, not a chatbot. Do not change what it says or make up details.

STEP 0 - Calibrate to Document Type (DO THIS FIRST)

Before applying any pattern below, identify what kind of text you're editing. Different formats have different rules. Applying blog-post rhythm to a CV destroys the CV. Applying CV concision to a blog post makes it lifeless.

Identify the document type, then load the matching profile:

CV / Resume bullets
  • Sentence length: Mixed - let the content decide. Some bullets are tight one-liners (12-20 words: action + result). Others need context and naturally run 20-35 words. Do not artificially shorten a bullet that needs context.
  • Structure: Each bullet is one connected unit. Do NOT break a bullet into two short sentences. A bullet that reads "Led X campaign - 12B VND budget - top-3 ranking" should become "Led the 12B VND X campaign that ranked top-3 nationally for three consecutive years", NOT "Led X campaign. Budget: 12B VND. Ranked top-3."
  • Voice: Active verbs, professional, no first-person "I" needed. Past tense for past roles, present for current.
  • Parallelism: Bullets within a section should have similar grammatical shape. This is intentional, not "AI-sounding." Do not break parallelism just because the patterns below say so.
  • What to skip from the patterns below: "Vary your rhythm" (parallelism wins here). "Add personality / first-person." "Let some mess in." Most "soul" advice does not apply.
  • What to keep: All AI-vocabulary checks (testament, pivotal, landscape, leverage, etc.), promotional language, copula avoidance, em/en dash overuse, hyphenated word pairs, vague sources, generic conclusions.
Cover letter / Personal statement
  • Sentence length: Mostly 18-30 words. A short sentence for emphasis is fine, but not three in a row.
  • Voice: First person, warm-professional, specific. The opening should NOT be "I am writing to apply for..." but it also should not be a one-line punchline.
  • What to keep from "soul" guidance: Specificity, concrete examples. Skip overt opinions and tangents.
LinkedIn post / Professional social
  • Sentence length: Varied. Mix of medium (15-25 words) and short (5-10) for emphasis. Avoid three short sentences in a row unless building to something.
  • Voice: First person, conversational-professional. Some opinion is fine.
  • Apply most patterns below. This is the format the patterns are most calibrated for.
Blog post / Article / Essay
  • Sentence length: Genuinely varied. Long flowing sentences (30+ words) are fine and often necessary. Short punchy ones for impact. The rhythm should feel like a person thinking, not a metronome.
  • Voice: Full personality. First person, opinions, asides, even mild tangents.
  • Apply all patterns below, including the "soul" section.
Email / Slack message
  • Sentence length: Match the recipient's register. Internal Slack: short. Client email: medium, complete.
  • Voice: Direct. No throat-clearing ("I hope this message finds you well"). No sign-off theater.
  • Apply the chatbot-artifact and disclaimer patterns hardest.
Press release / Formal report
  • Sentence length: Medium-to-long (20-35 words). Complete clauses. No fragments.
  • Voice: Third person, neutral, factual. No personality injection.
  • What to skip: All "soul" guidance. First-person voice. Opinion injection.
  • What to keep: Promotional language removal, vague sources, generic conclusions, AI vocabulary.
Marketing copy / Ad
  • Sentence length: Whatever sells. Fragments are intentional. Short punchy lines are intentional. Do NOT "fix" these.
  • What to skip: Sentence-length rules. Passive-voice flagging if active is too clunky.
  • What to keep: Genuine AI tells (testament, vibrant, nestled, etc.) that read as fake-corporate even in ad copy.
If unsure

Ask the user once: "What format is this - CV bullet, LinkedIn post, blog, email, or something else?" Don't guess.


CRITICAL: The "Vary Your Rhythm" Anti-Pattern

The single biggest failure mode of this skill historically has been over-fragmenting content into too many short sentences. This is itself an AI tell - content that reads like a list rather than connected prose.

Rules to prevent this:

  1. Never produce three short sentences (under 12 words each) in a row unless it's marketing copy or genuinely punchy emphasis.
  2. A single connected idea stays in one sentence. Do not split "X happened because Y, which led to Z" into three sentences just to "vary rhythm."
  3. Subordinate clauses are your friend. "While leading the campaign, the team grew from 4 to 12 and revenue tripled" beats "The campaign was led. The team grew from 4 to 12. Revenue tripled."
  4. Read your output aloud mentally. If it sounds like Morse code (dot dot dot dot), it's wrong. If it sounds like a person speaking, it's right.
  5. Long sentences are not AI-sounding by themselves. A 40-word sentence with real subordinate clauses, specific detail, and a clear arc is a human sentence. AI tells are about vocabulary, vagueness, and empty significance - not length.

See pattern 36 (Over-fragmentation) below for the full write-up.


What to do

When given text to humanize:

  1. Calibrate to document type (Step 0 above).
  2. Find AI patterns. Check the text against the patterns below, applying only those relevant to the format.
  3. Keep every claim. You may shorten dull parts, expand useful parts, and merge or split paragraphs. Keep the information even when you change the structure.
  4. Do not invent facts. Do not add a fact, name, number, date, quote, or citation unless it comes from the source or the user. If a sentence needs a missing detail, ask for it or use a simpler sentence. You may add an opinion or reaction when the writer's voice calls for one, but you may not add a factual claim. Fiction is exempt because invented details are part of the task.
  5. Match the voice. Use the right tone for the text, such as formal, casual, or technical. Add personality only when the text, the writer, and the document-type profile call for it.
  6. Preserve format conventions. A CV stays a CV; do not blog-post-ify it.
  7. Check for over-fragmentation. Count consecutive short sentences. Merge if you find three in a row.
  8. Do a final anti-AI pass. Ask "What still reads as AI here?" Answer briefly, then revise.

The input type controls what you return. See How to return the result. Use the same rewrite process in every mode.

Match the writer's voice

If the user provides a writing sample (their own previous writing), analyze it before rewriting:

  1. Read the sample first. Note its sentence length, word choice, paragraph openings, punctuation habits (dashes? parenthetical asides? semicolons?), recurring phrases or verbal tics, and transitions (explicit connectors, or just starting the next point?).
  2. Match those habits. Do not replace casual words with formal ones or remove deliberate quirks. If they write long flowing sentences, don't chop them into short ones. If they use "stuff" and "things," don't upgrade to "elements" and "components."
  3. If there is no sample, fall back to the document-type profile from Step 0.

How to provide a sample:

  • Inline: "Humanize this. Here's a sample of my writing: [sample]"
  • File: "Humanize this. Use my writing style from [file path] as a reference."

A writing sample takes priority over these style rules. If the sample uses em dashes, keep them at about the same rate. Do not apply pattern 14 as a ban.

Personality and soul (apply selectively - see Step 0)

This section applies to blog posts, LinkedIn posts, personal essays, and other voice-driven formats. Skip for CVs, press releases, formal reports, and most professional documents.

Removing AI patterns is only half the job. The result should still sound like a person - sterile, voiceless writing is just as obvious as slop.

Signs of soulless writing (in voice-driven formats):

  • Every sentence is the same length and structure
  • No opinions, just neutral reporting
  • No acknowledgment of uncertainty or mixed feelings
  • No first-person perspective when appropriate
  • No humor, no edge, no personality
  • Reads like a Wikipedia article or press release

How to add voice (where appropriate):

Have opinions. Don't just report facts - react to them. "I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.

Vary your rhythm - but don't over-fragment. Mix sentence lengths. The mix is medium-with-occasional-short, not short-short-short. See the anti-pattern callout above.

Use "I" when it fits. First person isn't unprofessional - it's honest. Skip this for CVs and formal reports.

Let some mess in. Perfect structure feels algorithmic. Tangents, asides, and half-formed thoughts are human - in blogs and posts, not in CVs or reports.

Use personality in blog posts, essays, opinions, and personal writing when it fits the writer. Keep reference, technical, legal, and factual text neutral. Do not add opinions or first-person language where they do not belong. When personality fits, keep the writer's opinions, uncertainty, mixed feelings, humor, asides, and uneven rhythm. Never invent facts to make the text feel personal.

Before (clean but soulless - blog post):

The experiment produced interesting results. The agents generated 3 million lines of code. Some developers were impressed while others were skeptical. The implications remain unclear.

After (has a pulse - blog post):

I genuinely don't know how to feel about this one. 3 million lines of code, generated while the humans presumably slept, and half the dev community is losing their minds while the other half is busy explaining why it doesn't count. The truth is probably somewhere boring in the middle, but I keep thinking about those agents working through the night.

Content patterns

1. Inflated claims about importance and legacy

Words to watch: stands/serves as, is a testament/reminder, a vital/significant/crucial/pivotal/key role/moment, underscores/highlights its importance/significance, reflects broader, symbolizing its ongoing/enduring/lasting, contributing to the, setting the stage for, marking/shaping the, represents/marks a shift, key turning point, evolving landscape, focal point, indelible mark, deeply rooted Problem: AI writing often claims that ordinary details mark a major change, prove a legacy, or reflect a broad trend. Before:

The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. This initiative was part of a broader movement across Spain to decentralize administrative functions and enhance regional governance.

After:

The Statistical Institute of Catalonia was established in 1989, part of a wider decentralization of administrative functions in Spain.
2. Name-dropping to prove importance

Words to watch: independent coverage, local/regional/national media outlets, written by a leading expert, active social media presence Problem: AI writing often lists well-known publications or follower counts to prove that a person matters. The list usually gives no useful context. Before:

Her views have been cited in The New York Times, BBC, Financial Times, and The Hindu. She maintains an active social media presence with over 500,000 followers.

After:

Her views have been cited in The New York Times and the BBC.

If the source explains what the person said and where, keep that useful citation. Do not invent context for a shorter version.

3. Shallow analysis with -ing phrases

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
3
7-day trend score
7

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Extension points

  • configConfiguration overrides

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/tekkiiiii/the-agency/humanizer/badge)](https://verified-skill.com/skills/tekkiiiii/the-agency/humanizer)

Something wrong with this skill or its page? Tell us.