SkillAgentSearch skills...

humanize

Use whenever the user asks to "humanize", "make this sound more human", "rewrite to avoid AI detection", "make this less AI-sounding", "add a human voice", or "write like a person".

Install / Use

npx skills add harshaneel/humanize --skill humanize

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Category

Marketing

Supported Platforms

Universal

Our assessment of humanize

humanize scores 84/100 on our quality scale, 497th of 652 Marketing skills we index.

Its SKILL.md is 35 KB long, well organised into 24 sections and no code examples: a thorough specification that gives an agent plenty to work with.

It has 496 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so humanize is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

humanize compared with similar skills

All 4 of these similar skills score higher than humanize; compare them before choosing.

SkillScoreStarsUpdatedFormat
humanize (this skill)by harshaneel8449657d agoSKILL.md
LocalAIby mudler10050.4ktodayMCP Server
algorithmic-artby anthropics100177.9k57d agoSKILL.md
pptxby anthropics100177.9k57d agoSKILL.md
prospectingby coreyhaines3110060.1k7d agoSKILL.md

Frequently asked questions

How do I install humanize?
Run npx skills add harshaneel/humanize --skill humanize. The install tabs above show the steps for each supported agent.
Which AI agents does humanize work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is humanize safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is humanize still maintained?
The repository was last updated about 2 months ago, so humanize is actively maintained.

name: humanize description: > Use whenever the user asks to "humanize", "make this sound more human", "rewrite to avoid AI detection", "make this less AI-sounding", "add a human voice", or "write like a person". Also use when the user pastes text and asks why it reads as robotic, generic, flat, or AI-like, or when generating new text in a register where AI tells (em dashes, semicolons, hedges, banned vocabulary like "delve", "leverage", "robust") would damage credibility.

Humanize Text Skill

Transforms AI-generated or flat text into output that mirrors the statistical and stylistic fingerprint of human writing. Grounded in the published detection literature; sources live in references/research.md (background only, not needed during a rewrite).


Hard rules (read first, enforce last)

These seven fail more often than everything else combined, because the model that wrote the draft is the model checking it. You systematically overproduce these patterns; your draft contains em dashes even when you don't remember writing them. Treat "my draft is probably clean" as false by default.

  1. Em dashes: at most one per 300 words of output. Under 300 words, zero.
  2. Semicolons: none, unless a list item itself contains commas or the register is explicitly formal/academic (Lever 8).
  3. Straight quotes and apostrophes only. Never curly. Sole exception: publishing contexts where typographic quotes are house style (Lever 8).
  4. Banned vocabulary (full list at end of this skill). Highest-frequency offenders: delve, leverage, utilize, robust, comprehensive, streamline, furthermore, moreover, "it is important to note".
  5. No negation framing: "not just X", "not X, it's Y", "it's not about X, it's about Y", "more X than Y". Say what the thing IS. Poetic forms count: "isn't proof you failed, it's proof you showed up" is the same banned pivot wearing a nicer coat. (False binaries like "either X or Y" are handled by the Signal I checklist's either/or item.)
  6. Output shape: the rewritten text only. No preamble ("Here's the humanized version:"), no trailing changelog ("Main moves:", "What I changed:"). The ONLY permitted additions are the two meta-notes mandated by protocol steps 2 and 5.6, appended after the rewrite. If the user wants the diff explained, they'll ask.
  7. Sentence-length spread: in any output over ~80 words, the longest sentence must beat the shortest by 20+ words, and fewer than half the sentences may sit in the 10-to-20-word band. Your uncorrected rhythm clusters at 10-20 words with ~6 words of deviation; that uniformity is a measured tell even when every other rule passes. Verify from the written count list (step 5), never by feel.

These apply in EVERY register, including creative, lyrical, and narrative prose. An em dash in a poem is still an em dash to a detector, and creative registers are where the "this one is doing literary work" rationalization kicks in hardest.

Enforcement is positional: stated here at the top, checked at the END against the finished draft by re-reading the actual draft text and counting occurrences (protocol steps 4-5). Never mark them clean from memory. If long context forces you to drop every other rule in this skill, keep these seven.


Mental model: what detectors actually measure

Nine signals: eight stylometric plus the RLHF fingerprint. Your output must move in the human direction on ALL of them.

| Signal | AI direction (avoid) | Human direction (target) | |---|---|---| | Perplexity | Predictable, low-surprise word choices | Occasional unexpected but apt words; word choices driven by rhythm, specificity, or memory | | Burstiness | Uniform sentence length (~15–20 words every time) | Aggressive alternation: short punchy sentences. Then a longer one that builds and unfolds over a clause or two. | | Hedge density | Overuse of "often", "generally", "typically", "it is important to note" | Hedges only when actually uncertain; direct assertion otherwise | | Lexical repetition | Same root words recycled across paragraphs | Natural semantic diversity; synonyms and reformulations | | Structural markers | Bullet lists for everything; numbered steps; excessive subheadings | Flowing prose; structure emerges from content, not imposed on it | | Personal/emotional specificity | Generic, neutral, applicable-to-anyone claims | Specific: exact numbers, named examples, temporal anchors ("last quarter", "when I ran X") | | POS density | High adjective/auxiliary verb density; subordinating conjunctions everywhere | Nouns and verbs do the heavy lifting; adjectives earned, not decorative | | Punctuation fingerprint | Em dashes for drama, semicolons to link clauses, mid-sentence colons — all overused | Periods do the work. Em dashes rare. Semicolons almost never. Colons mainly to introduce lists. |

The levers below are the write-side counterparts of the signals ai-check grades (A–I): 1→A, 2→B, 3→C, 4→D, 5→E, 6→H, 7→F, 8→G, 9→I (RLHF subset). The full rhetorical-scaffolding catalog for Signal I is enforced by the audit pass (step 5.5), not by any single lever.


Nine humanization levers, apply all of them

Lever 1: Perplexity injection (word-level)

Replace predictable vocabulary with words a real person would choose given this context:

  • Swap generic verbs for specific ones: "address" → "untangle", "utilize" → "lean on", "implement" → "wire up"
  • Let the subject matter suggest the vocabulary: a Go engineer says "flush the buffer", not "clear the temporary data storage"
  • One or two genuinely surprising but accurate word choices per paragraph
  • Avoid: "delve", "leverage", "robust", "streamline", "significant", "comprehensive", "notably", "it is worth noting", "in today's fast-paced world"

Watch for elegant variation (synonym cycling). LLMs cycle synonyms for the same referent: "The protagonist faces challenges. The main character must adapt. The central figure triumphs." Same person, three labels. Rule: pick the canonical noun per referent and use it consistently; vary with a pronoun, not a synonym. "the company / the firm / the organization" → "the company" + "it".

Lever 2: Burstiness injection (sentence-level)

Enforce sentence length variance. Target: standard deviation of sentence word count > 8. You can't compute stdev mentally, so enforce these two countable proxies instead; BOTH are required (hard rule 7):

  • Range floor: longest sentence minus shortest ≥ 20 words. In practice: at least one fragment of 5 words or fewer AND at least one 25-plus-word sentence that earns its length.
  • Mid-band cap: fewer than half the sentences in the 10-to-20-word band. Satisfying the range floor with one fragment and one long sentence while everything else sits at 12-16 words still reads uniform; the middle must spread too.

Supporting rules:

  • Every 3–4 sentences, insert one sentence of 5 words or fewer. Just drop it. Like that.
  • Never more than 3 consecutive sentences within 5 words of each other in length.
  • Burstiness fails in both directions: a run of shorts without a longer counterweight reads choppy, not punchy.
  • Mid-paragraph uniformity trap: openers and closers vary, but the middle 3–4 sentences collapse into the same band. Break one.

Lever 3: Hedge surgery

Audit every softening word:

  • Delete: "it is important to note that", "it is worth mentioning that", "generally speaking", "in many cases", "it can be argued", "often", "typically" (unless genuinely needed for accuracy)
  • Replace with direct assertion: "This matters because X" not "It is important to consider that X may be relevant"
  • Real uncertainty gets human phrasing: "I'm not sure this holds for edge cases, but..." not "while results may vary"
  • Don't soften real rules with "almost always" / "generally". If exceptions exist, name them: "This breaks down when X."
  • No announcement-colon openers: "The rule I use:", "The key insight:" — state the rule directly. (Pattern announcement in general is a Signal I checklist item.)
  • A sentence doing two logical jobs (comparison AND conclusion) usually reads cleaner as two.

Filler-phrase substitutions (the pattern generalizes: any multi-word wrapper around a one-word meaning gets the one word):

| Verbose (AI) | Concise (human) | |---|---| | Due to the fact that | Because | | In the event that | If | | Has the ability / capacity to | Can | | Make a decision / an assumption | Decide / Assume | | For the purpose of | To / For | | With regard to / With respect to | About / On | | Prior to / Subsequent to | Before / After | | In light of the fact that / Despite the fact that | Since / Although | | In the process of / The fact that | (drop entirely; rephrase) |

Lever 4: Structural flattening

Rhetorical scaffolding patterns (either/or binaries, chiasmus, tricolons, balanced parenthetical pairs, anaphora, "turns out" pivots, thesis-first openers incl. "X is the easy/hard part", mini-aphorism closers, parallel-subject mirrors) are catalogued ONCE in the Signal I checklist (step 5.5); negation pivots live in hard rule 5 and the step-4 diminishment scan. Apply the checklist at write time too. This table covers only what the checklist doesn't:

| AI pattern | Human replacement | |---|---| | Intro sentence + 3-bullet list | Prose paragraph where items are joined by flow, not bullets | | "There are three main factors: ..." | Just talk about the factors; transitions carry the structure | | "In conclusion, ..." | End mid-thought if the thought is complete; or "The net of all this..." / "Bottom line:" | | Numbered sections for everything | Sections only when content is genuinely enumerable and order matters | | Topic sentence + evidence + restatement | Skip the restatement; humans don't recap what they just said | | Formula personal essay opener: "The [noun] I [remember/think about] most [adverb]" | Start with the incident itself: "In 2019 I shipped a rate limiter that fell apart the first hour it hit real traffic." | | Intensifier/diminisher opposition: "X obsessively / Y barely at all" | Make the contrast asymmetric: "I tested the happy path constantly. The failure paths got one pass." | | Landing phrase: "is the actual/real work" | State the conclusion without the landing phrase. | | Local coherence over-smooth | Every sentence connects perfectly; reads too uniform, survives surface rewriting. Fix: one sentence per paragraph that slightly misfires — a thought that shifts direction, a word more casual than the register, a connection that isn't clean. | | "Laid out that way" / "Seen this way" reframe pivot | Make the observation directly. | | Perfect paragraph-per-idea essay arc | Let one paragraph do two jobs, or leave a thought unresolved. | | Three-act Slack/update structure | Break with a fourth element that doesn't fit the arc. | | Copula avoidance: "X serves as Y", "X stands as Y", "X marks/represents/boasts/features/offers Y" | Use "is" or "has": "Gallery 825 is LAAA's exhibition space." | | Significance inflation: "stands as a testament to", "marks a pivotal moment in", "evolving landscape", "setting the stage for" | Cut, or replace with the concrete claim: "established in 1989 to publish regional statistics independently." | | Promotional register: "nestled in the heart of", "vibrant", "breathtaking", "must-visit", "boasts a rich heritage", "renowned for" | Cut the brochure language: "Alamata is a town in the Gonder region known for its weekly market." | | Vague attributions: "Industry observers have noted", "Experts argue", "Critics have suggested" | Name a specific source or drop the claim. | | Outline-formula "Challenges and Future Prospects" sections | Replace with the specific challenges and what's being done, or drop the section. |

Lever 5: Specificity insertion

Every abstract claim needs a grounding anchor (a number, a name, a date, a concrete example). "Perfo

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars496
CategoryMarketing
Updated1mo ago
Forks51

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions