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

MITAuto-check passedWriting & Content

Install Avoid AI Writing

skills CLI
$ npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a claude-code

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

GitHub CLI
$ gh skill install brycewang-stanford/Auto-Empirical-Research-Skills avoid-ai-writing --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/brycewang-stanford/Auto-Empirical-Research-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/47-conorbronsdon-avoid-ai-writing .claude/skills/avoid-ai-writing && 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
avoid-ai-writing
GitHub stars
4.5k
Used in
1 other repo
Token cost
~8.4k tokens
SKILL.md length
4,586 words
Files
5
Skills in repo
383
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 3 steps: Audit it: identify every AI-ism present,… → Rewrite it: return a clean version with… → Show a diff summary: briefly list what…
  • Asked to remove AI-isms
  • SKILL.md covers Modes and What to remove or fix
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Avoid AI Writing is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detection-only mode that flags patterns without rewriting.

Its SKILL.md is about 8.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `CHANGELOG.md`, `CLAUDE.md` and `README-original.md`). Compatibility notes: Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No…

It sits in Writing & Content, covering Humanizing AI text. The repository describes itself as: 🔬 A curated collection of 23,000+ agent skills for empirical research across 8 social science disciplines. | 精选 23,000+ AI Agent 技能库,覆盖8大社会科学学科的实证研究。CoPaper.AI… The licence is MIT.

When your agent uses it

  • Asked to remove AI-isms
  • Clean up AI writing
  • Edit writing for AI patterns
  • Audit writing for AI tells

Example prompts

  • “AI-isms”
  • “remove AI-isms,”
  • “clean up AI writing,”
  • “/avoid-ai-writing”

Requirements

  • Compatibility (from SKILL.md): Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No external tools or APIs required.

Workflow steps

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

  1. Audit it: identify every AI-ism present, citing the specific text
  2. Rewrite it: return a clean version with all AI-isms removed
  3. Show a diff summary: briefly list what you changed and why

What it can do on your machine

Read from SKILL.md and the folder at commit 9fa87d8. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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):

    • github.com

    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.

  • Compatibility

    Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No external tools or APIs required.

    From compatibility in the SKILL.md frontmatter.

Context cost

Avoid AI Writing loads about 8.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 4,586 words of instructions outside code blocks.

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

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Auto-Empirical-Research-Skills at commit 9fa87d8, republished under its MIT licence (© brycewang-stanford). 4,586 words, ~8,430 tokens.

Download SKILL.mdSave it as .claude/skills/avoid-ai-writing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
avoid-ai-writing
description
Audit and rewrite content to remove AI writing patterns ("AI-isms"). Use this skill when asked to "remove AI-isms," "clean up AI writing," "edit writing for AI patterns," "audit writing for AI tells," or "make this sound less like AI." Supports a detection-only mode that flags patterns without rewriting.
compatibility
Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No external tools or APIs required.
version
3.3.1
license
MIT
metadata.author
Conor Bronsdon
metadata.tags
writing editing voice quality
metadata.agentskills_spec
1.0

Avoid AI Writing — Audit & Rewrite

You are editing content to remove AI writing patterns ("AI-isms") that make text sound machine-generated.

Modes

This skill operates in one of two modes:

rewrite (default) — Flag AI-isms and rewrite the text to fix them.

detect — Flag AI-isms only. No rewriting. Use this mode when:

  • The writer wants to see what's flagged and decide what to fix themselves
  • The flagged patterns might be intentional (AI patterns aren't always bad — they can be effective in small doses)
  • You're auditing text you don't want altered (published content, someone else's writing, reference material)
  • You want a quick scan without waiting for a full rewrite

Trigger detect mode when the user says "detect," "flag only," "audit only," "just flag," "scan," "what AI patterns are in this," or similar. Default to rewrite mode if not specified.


In rewrite mode, your job is to:

  1. Audit it: identify every AI-ism present, citing the specific text
  2. Rewrite it: return a clean version with all AI-isms removed
  3. Show a diff summary: briefly list what you changed and why

In detect mode, your job is to:

  1. Audit it: identify every AI-ism present, citing the specific text
  2. Assess it: note which flags are clear problems vs. patterns that may be intentional or effective in context

What to remove or fix

Formatting
  • Em dashes (— and --): Replace with commas, periods, parentheses, or rewrite as two sentences. Target: zero. Hard max: one per 1,000 words. This applies to headings and section titles too, not just body prose. Catch both the Unicode em dash (—) and the double-hyphen substitute (--).
  • Bold overuse: Strip bold from most phrases. One bolded phrase per major section at most, or none. If something's important enough to bold, restructure the sentence to lead with it instead.
  • Emoji in headers: Remove entirely. No ## 🚀 What This Means. Exception: social posts may use one or two emoji sparingly — at the end of a line, never mid-sentence.
  • Excessive bullet lists: Convert bullet-heavy sections into prose paragraphs. Bullets only for genuinely list-like content (feature comparisons, step-by-step instructions, API parameters).
Sentence structure
  • "It's not X — it's Y" / "This isn't about X, it's about Y": Rewrite as a direct positive statement. Max one per piece, and only if it serves the argument.
  • Hollow intensifiers: Cut genuine, real (as in "a real improvement"), truly, quite frankly, to be honest, let's be clear, it's worth noting that. Just state the fact.
  • Vague endorsement ("worth [verb]ing"): Cut or replace worth reading, worth paying attention to, worth a look, worth exploring, worth checking out, worth your time. These substitute a generic thumbs-up for a specific reason. Say why something matters instead.
  • Hedging: Cut perhaps, could potentially, it's important to note that, to be clear. Make the point directly.
  • Missing bridge sentences: Each paragraph should connect to the last. If paragraphs could be rearranged without the reader noticing, add connective tissue.
  • Compulsive rule of three: Vary groupings. Use two items, four items, or a full sentence instead of triads. Max one "adjective, adjective, and adjective" pattern per piece.
Words and phrases to replace

Words are organized into three tiers based on how reliably they signal AI-generated text. This tiered approach — adapted from brandonwise/humanizer's vocabulary research — reduces false positives on words that are fine in isolation but suspicious in clusters.

  • Tier 1 — Always flag. These words appear 5–20x more often in AI text than human text. Replace on sight.
  • Tier 2 — Flag in clusters. Individually fine, but two or more in the same paragraph is a strong AI signal. Flag when they appear together.
  • Tier 3 — Flag by density. Common words that AI simply overuses. Only flag when they make up a noticeable fraction of the text (roughly 3%+ of total words).
Tier 1 — Always replace
ReplaceWith
delve / delve intoexplore, dig into, look at
landscape (metaphor)field, space, industry, world
tapestry(describe the actual complexity)
realmarea, field, domain
paradigmmodel, approach, framework
embarkstart, begin
beacon(rewrite entirely)
testament toshows, proves, demonstrates
robuststrong, reliable, solid
comprehensivethorough, complete, full
cutting-edgelatest, newest, advanced
leverage (verb)use
pivotalimportant, key, critical
underscoreshighlights, shows
meticulous / meticulouslycareful, detailed, precise
seamless / seamlesslysmooth, easy, without friction
game-changer / game-changingdescribe what specifically changed and why it matters
hit differently / hits different(say what specifically changed, or cut)
utilizeuse
watershed momentturning point, shift (or describe what changed)
marking a pivotal moment(state what happened)
the future looks bright(cut — say something specific or nothing)
only time will tell(cut — say something specific or nothing)
nestledis located, sits, is in
vibrant(describe what makes it active, or cut)
thrivinggrowing, active (or cite a number)
despite challenges… continues to thrive(name the challenge and the response, or cut)
showcasingshowing, demonstrating (or cut the clause)
deep dive / dive intolook at, examine, explore
unpack / unpackingexplain, break down, walk through
bustlingbusy, active (or cite what makes it busy)
intricate / intricaciescomplex, detailed (or name the specific complexity)
complexities(name the actual complexities, or use "problems" / "details")
ever-evolvingchanging, growing (or describe how)
enduringlasting, long-running (or cite how long)
dauntinghard, difficult, challenging
holistic / holisticallycomplete, full, whole (or describe what's included)
actionablepractical, useful, concrete
impactfuleffective, significant (or describe the impact)
learningslessons, findings, takeaways
thought leader / thought leadershipexpert, authority (or describe their actual contribution)
best practiceswhat works, proven methods, standard approach
at its core(cut — just state the thing)
synergy / synergies(describe the actual combined effect)
interplayrelationship, connection, interaction
in order toto
due to the fact thatbecause
serves asis
features (verb)has, includes
boastshas
presents (inflated)is, shows, gives
commencestart, begin
ascertainfind out, determine, learn
endeavoreffort, attempt, try
keen (as intensifier)interested, eager, enthusiastic (or cut — just state the interest)
symphony (metaphor)(describe the actual coordination or combination)
embrace (metaphor)adopt, accept, use, switch to
Tier 2 — Flag when 2+ appear in the same paragraph

These words are legitimate on their own. When two or more show up together, the paragraph likely needs a rewrite.

ReplaceWith
harnessuse, take advantage of
navigate / navigatingwork through, handle, deal with
fosterencourage, support, build
elevateimprove, raise, strengthen
unleashrelease, enable, unlock
streamlinesimplify, speed up
empowerenable, let, allow
bolstersupport, strengthen, back up
spearheadlead, drive, run
resonate / resonates withconnect with, appeal to, matter to
revolutionizechange, transform, reshape (or describe what changed)
facilitate / facilitatesenable, help, allow, run
underpinsupport, form the basis of
nuancedspecific, subtle, detailed (or name the actual nuance)
crucialimportant, key, necessary
multifaceted(describe the actual facets, or cut)
ecosystem (metaphor)system, community, network, market
myriadmany, numerous (or give a number)
plethoramany, a lot of (or give a number)
encompassinclude, cover, span
catalyzestart, trigger, accelerate
reimaginerethink, redesign, rebuild
galvanizemotivate, rally, push
augmentadd to, expand, supplement
cultivatebuild, develop, grow
illuminateclarify, explain, show
elucidateexplain, clarify, spell out
juxtaposecompare, contrast, set side by side
paradigm-shifting(describe what actually shifted)
transformative / transformation(describe what changed and how)
cornerstonefoundation, basis, key part
paramountmost important, top priority
poised (to)ready, set, about to
burgeoninggrowing, emerging (or cite a number)
nascentnew, early-stage, emerging
quintessentialtypical, classic, defining
overarchingmain, central, broad
underpinning / underpinningsbasis, foundation, what supports
Tier 3 — Flag only at high density

These are normal words. Only flag them when the text is saturated with them — a sign that AI filled space with vague praise instead of specifics.

WordWhat to do
significant / significantlyReplace some with specifics: numbers, comparisons, examples
innovative / innovationDescribe what's actually new
effective / effectivelySay how or cite a metric
dynamic / dynamicsName the actual forces or changes
scalable / scalabilityDescribe what scales and to what
compellingSay why it compels
unprecedentedName the precedent it breaks (or cut)
exceptional / exceptionallyCite what makes it an exception
remarkable / remarkablySay what's worth remarking on
sophisticatedDescribe the sophistication
instrumentalSay what role it played
world-class / state-of-the-art / best-in-classCite a benchmark or comparison
Template phrases (avoid)

These slot-fill constructions signal that a sentence was generated, not written. If a phrase has a blank where a noun or adjective could go and still sound the same, it's too generic.

  • "a [adjective] step towards [adjective] AI infrastructure" → describe the specific capability, benchmark, or outcome
  • "a [adjective] step forward for [noun]" → same rule: say what actually changed
  • "Whether you're [X] or [Y]" → false-breadth construction. Pick the audience you're actually addressing, or cut. "Whether you're a startup founder or an enterprise architect" means nothing — it's just "everyone."
  • "I recently had the pleasure of [verb]-ing" → review/social AI pattern. Just say what happened: "I talked to," "I read," "I attended."
Transition phrases to remove or rewrite
  • "Moreover" / "Furthermore" / "Additionally" → restructure so the connection is obvious, or use "and," "also," "on top of that"
  • "In today's [X]" / "In an era where" → cut or state specific context
  • "It's worth noting that" / "Notably" → just state the fact
  • "Here's what's interesting" / "Here's what caught my eye" / "Here's what stood out" → reader-steering frames. Let the content signal its own importance. If you need a lead-in, make it specific: "The revenue number matters because..." not "Here's the interesting part."
  • "In conclusion" / "In summary" / "To summarize" → your conclusion should be obvious
  • "When it comes to" → just talk about the thing directly
  • "At the end of the day" → cut
  • "That said" / "That being said" → cut or use "but," "yet," or "however." Don't overuse any one of them.
Structural issues
  • Uniform paragraph length: Vary deliberately. Include some 1-2 sentence paragraphs and some longer ones. If every paragraph is roughly the same size, fix it.
  • Formulaic openings: If the piece opens with broad context before getting to the point ("In the rapidly evolving world of..."), rewrite to lead with the news or the insight. Context can come second.
  • Suspiciously clean grammar: Don't sand away all personality. Deliberate fragments, sentences starting with "And" or "But," comma splices for effect: if the natural voice uses them, keep them.
Significance inflation
  • Phrases like "marking a pivotal moment in the evolution of..." or "a watershed moment for the industry" inflate routine events into history-making ones. State what happened and let the reader judge significance.
  • If the sentence still works after you delete the inflation clause, delete it.
Copula avoidance
  • AI text avoids "is" and "has" by substituting fancier verbs: "serves as," "features," "boasts," "presents," "represents." These sound like a press release.
  • Default to "is" or "has" unless a more specific verb genuinely adds meaning.
Synonym cycling
  • AI rotates synonyms to avoid repeating a word: "developers… engineers… practitioners… builders" in the same paragraph. Human writers repeat the clearest word.
  • If the same noun or verb appears three times in a paragraph and that's the right word, keep all three. Forced variation reads as thesaurus abuse.
Vague attributions
  • "Experts believe," "Studies show," "Research suggests," "Industry leaders agree" — without naming the expert, study, or leader. Either cite a specific source or drop the attribution and state the claim directly.
Filler phrases
  • Strip mechanical padding that adds words without meaning:
    • "It is important to note that" → (just state it)
    • "In terms of" → (rewrite)
    • "The reality is that" → (cut or just state the claim)
  • Note: "In order to," "Due to the fact that," and "At the end of the day" are covered in the word/phrase table and transition sections above — don't duplicate rules.
Generic conclusions
  • "The future looks bright," "Only time will tell," "One thing is certain," "As we move forward" — these are filler disguised as conclusions. Cut them. If the piece needs a closing thought, make it specific to the argument.
Chatbot artifacts
  • "I hope this helps!", "Certainly!", "Absolutely!", "Great question!", "Feel free to reach out," "Let me know if you need anything else" — these are conversational tics from chat interfaces, not writing. Remove entirely.
  • Also watch for: "In this article, we will explore…" or "Let's dive in!" — these are AI-generated meta-narration. Cut or rewrite with a direct opening.
"Let's" constructions
  • "Let's explore," "Let's take a look," "Let's break this down," "Let's examine" — AI uses "let's" as a false-collaborative opener to ease into a topic. It's filler that delays the actual point. Just start with the point. "Let's dive in" is covered above under chatbot artifacts, but the pattern is broader than that — flag any "let's + verb" that's functioning as a transition rather than a genuine invitation to act.
Notability name-dropping
  • AI text piles on prestigious citations to manufacture credibility: "cited in The New York Times, BBC, Financial Times, and The Hindu." If a source matters, use it with context: "In a 2024 NYT interview, she argued..." One specific reference beats four name-drops.
Superficial -ing analyses
  • Strings of present participles used as pseudo-analysis: "symbolizing the region's commitment to progress, reflecting decades of investment, and showcasing a new era of collaboration." These say nothing. Replace with specific facts or cut entirely.
Promotional language
  • AI defaults to tourism-brochure prose: "nestled within the breathtaking foothills," "a vibrant hub of innovation," "a thriving ecosystem." Replace with plain description: "is a town in the Gonder region," "has 12 startups." If you wouldn't say it in conversation, cut it.
Formulaic challenges
  • "Despite challenges, [subject] continues to thrive" or "While facing headwinds, the organization remains resilient." This is a non-statement. Name the actual challenge and the actual response, or cut the sentence.
False ranges
  • AI creates false breadth by pairing unrelated extremes: "from the Big Bang to dark matter," "from ancient civilizations to modern startups." These sound sweeping but say nothing. List the actual topics or pick the one that matters.
Inline-header lists
  • Bullet lists where each item starts with a bold header that repeats itself: "Performance: Performance improved by..." Strip the bold header and write the point directly. If the list items need headers, they should probably be paragraphs.
Title case headings
  • AI over-capitalizes headings: "Strategic Negotiations And Key Partnerships" instead of "Strategic negotiations and key partnerships." Use sentence case for subheadings. Title case only for the piece's main title, if at all.
Cutoff disclaimers
  • "While specific details are limited based on available information," "As of my last update," "I don't have access to real-time data." These are model limitations leaking into prose. Either find the information or remove the hedge. Never publish a sentence that admits the writer didn't look something up.
Novelty inflation
  • AI text treats established concepts as if the speaker invented or discovered them: "He introduced a term," "She coined the phrase," "a concept nobody's naming," "a failure mode nobody talks about." In reality, most ideas in a conversation are applications of existing concepts, not inventions.
  • Two problems. First, it's factually risky: if the concept already has a Wikipedia page or conference talks from last year, claiming novelty makes the writer look uninformed. Second, it flatters the subject in a way that reads as promotional rather than analytical.
  • The fix: describe what the person did with the concept, not that they discovered it. "Michel walked through how context poisoning works in practice" instead of "Michel introduced a term I hadn't heard before: context poisoning." If you're unsure whether something is novel, assume it isn't and frame accordingly.
  • Related patterns to flag: "the failure mode nobody's naming," "a problem nobody talks about," "the insight everyone's missing," "what nobody tells you about." These are engagement-bait framings that claim scarcity of knowledge where none exists.
Emotional flatline
  • AI claims emotions as a structural crutch without conveying them through the writing: "What surprised me most," "I was fascinated to discover," "What struck me was," "I was excited to learn," "The most interesting part."
  • Two problems. First, it's tell-don't-show: if the thing is genuinely surprising, the reader should feel that from the content, not from the writer announcing it. Second, these phrases are massively overused as list introductions and transitions. They're filler wearing an emotion costume.
  • This pattern isn't always AI. It's also a sign of lazy human writing on autopilot. Flag it either way.
  • The fix isn't "never say surprised." It's: if you claim an emotion, the writing around it should earn it. Otherwise cut the claim and present the thing directly.
  • Related pattern: "hit differently" / "hits different." AI uses trendy colloquialisms as a shortcut to sound relatable without earning the emotional beat. If something genuinely affected you, describe how. Otherwise cut.
False concession structure
  • "While X is impressive, Y remains a challenge" or "Although X has made strides, Y is still an open question." AI uses this to sound balanced without actually weighing anything. Both halves are vague. Either make the concession specific (name what's impressive, name the actual challenge) or pick a side and argue it.
Show full SKILL.md (1,824 more words)Show less
Rhetorical question openers
  • "But what does this mean for developers?" / "So why should you care?" / "What's next?" � AI uses rhetorical questions to stall before the actual point. If you know the answer, just say it. Rhetorical questions are earned by strong setup, not dropped as section transitions.
Parenthetical hedging
  • "(and, increasingly, Z)" / "(or, more precisely, Y)" / "(and perhaps more importantly, W)" � AI inserts parenthetical asides to sound nuanced without committing. If the aside matters, give it its own sentence. If it doesn't, cut it.
Numbered list inflation
  • "Three key takeaways" / "Five things to know" / "Here are the top seven" � AI defaults to numbered lists because they're structurally safe. Only use numbered lists when the content genuinely has that many discrete, parallel items. If you're padding to hit a number, the list shouldn't exist.
Reasoning chain artifacts
  • "Let me think step by step," "Breaking this down," "To approach this systematically," "Step 1:," "Here's my thought process," "First, let's consider," "Working through this logically" — these are artifacts of chain-of-thought reasoning leaking into published prose. The reader doesn't need to see the scaffolding. State the conclusion, then the evidence.
  • Also watch for numbered reasoning steps that read like an internal monologue rather than an argument meant for an audience.
Sycophantic tone
  • "Great question!", "Excellent point!", "You're absolutely right!", "That's a really insightful observation" — these are conversational rewards from chat interfaces, not writing. Remove entirely.
  • Distinct from chatbot artifacts: sycophancy specifically validates the reader/questioner rather than just performing helpfulness.
Acknowledgment loops
  • "You're asking about," "The question of whether," "To answer your question," "That's a great question. The..." — AI restates the prompt before answering. In writing, this is pure filler. The reader knows what they asked. Just answer.
  • Related pattern: opening a section by summarizing what the previous section said. If the structure is clear, the reader doesn't need a recap.
Confidence calibration phrases
  • "It's worth noting that," "Interestingly," "Surprisingly," "Importantly," "Significantly," "Notably," "Certainly," "Undoubtedly," "Without a doubt" — AI uses these to signal how the reader should feel about a fact instead of letting the fact speak for itself.
  • "Here's what's interesting," "Here's the interesting part," "Here are the parts I found interesting" — reader-steering cue that pre-interprets importance. Works when followed by genuinely surprising data; fails when it introduces a restatement of something obvious (which is the AI default).
  • One "notably" in a 2,000-word piece is fine. Three in 500 words is AI-style emphasis stacking. Flag by density.
Excessive structure
  • Too many headers in short text: more than 3 headings in under 300 words is almost always AI trying to look organized. Merge sections or use prose transitions instead.
  • Too many list items: 8+ bullet points in under 200 words means the content should be a paragraph, not a list.
  • Formulaic section headers: "Overview," "Key Points," "Summary," "Conclusion," "Introduction" — these are default AI scaffolding. Use headers that tell the reader something specific about what follows.
Rhythm and uniformity

These aren't individual word or phrase problems — they're patterns in how the text flows as a whole. AI text is metronomic; human text has varied rhythm.

Structure is the #1 detection signal. AI detection tools (including Pangram, which trains a classifier on 28M human documents) weight structural regularity higher than vocabulary. Consistent sentence construction, uniform pacing, and symmetrical phrasing patterns are harder to mask than swapping out a few flagged words. If you fix every word on the Tier 1 list but leave the rhythm untouched, the text still reads as AI-generated.

  • Sentence length uniformity: If most sentences are 15–25 words, the text sounds robotic. Mix short punchy sentences (3–8 words) with longer flowing ones (20+). Fragments work. Questions break the monotony.
  • Paragraph length uniformity: If every paragraph is 3–5 sentences and roughly the same size, vary deliberately. Some paragraphs should be one sentence. Some should be longer.
  • Vocabulary repetition vs. synonym cycling: AI either repeats the same word mechanically or cycles through synonyms conspicuously. Human writers repeat when the word is right and vary when it's natural — there's no formula.
  • Read-aloud test: If the text sounds like it could be read by a text-to-speech engine without sounding weird, it's probably too uniform. Human writing has rhythm that resists robotic delivery.
  • Missing first-person perspective: Where appropriate, the writer should have opinions, preferences, and reactions. AI is relentlessly neutral. If the piece is supposed to have a voice, the absence of "I think," "in my experience," or a stated preference is itself an AI tell.
  • Over-polishing: Aggressively editing out every irregularity can push human writing toward AI statistical profiles. Natural disfluency, idiosyncratic word choices, and uneven pacing are what keep text out of the "AI-generated" classification. Don't sand away all personality in pursuit of clean prose. This skill should make writing sound more human, not less — if you apply every rule at maximum strictness, you risk creating the very uniformity you're trying to avoid.
When to rewrite from scratch vs. patch

If the text has 5+ flagged vocabulary hits across multiple categories, 3+ distinct pattern categories triggered, and uniform sentence/paragraph length, patching individual phrases won't fix it — the structure itself is AI-generated. Advise a full rewrite: state the core point in one sentence, then rebuild from there.


Severity tiers

Not all AI-isms are equal. When doing a quick pass or triaging a large document, prioritize by tier:

P0 � Credibility killers (fix immediately)
  • Cutoff disclaimers ("As of my last update")
  • Chatbot artifacts ("I hope this helps!", "Great question!")
  • Vague attributions without sources ("Experts believe")
  • Significance inflation on routine events
P1 � Obvious AI smell (fix before publishing)
  • Word-list violations (delve, leverage, harness, robust, etc.)
  • Template phrases and slot-fill constructions
  • "Let's" transition openers
  • Synonym cycling within a paragraph
  • Formulaic openings ("In the rapidly evolving world of...")
  • Bold overuse
  • Em dash frequency (above 1 per 1,000 words)
P2 � Stylistic polish (fix when time allows)
  • Generic conclusions ("The future looks bright")
  • Compulsive rule of three
  • Uniform paragraph length
  • Copula avoidance (serves as, features, boasts)
  • Transition phrases (Moreover, Furthermore, Additionally)

Use P0+P1 for quick passes. Full audit covers all three tiers.


Self-reference escape hatch

When writing about AI writing patterns (blog posts, tutorials, skill documentation like this file), quoted examples are exempt from flagging. Text inside quotation marks, code blocks, or explicitly marked as illustrative ("for example, AI might write...") should not be rewritten. Only flag patterns that appear in the author's own prose, not in cited examples of bad writing.


Context profiles

Pass an optional context hint to adjust rule strictness. If no context is specified, auto-detect from content cues (short + hashtags = social, code blocks = technical, salutation = email, default = blog).

Profile definitions

linkedin � Short-form social. Punchy fragments, visual formatting matter. blog � Default. Standard long-form prose. All rules apply at full strength. technical-blog � Long-form with code, architecture, APIs. Technical terms get a pass. investor-email � High-trust audience. Tighten everything; promotional language is the biggest risk. docs � Documentation, READMEs, guides. Clarity over voice. casual � Slack messages, internal notes, quick replies. Only catch the worst offenders.

Tolerance matrix

Rules not listed in the table apply at full strength across all profiles.

Rulelinkedinblogtechnical-bloginvestor-emaildocscasual
Em dashesrelaxed (2/post OK)strictstrictstrictrelaxedskip
Bold overuserelaxed (bold hooks OK)strictstrictstrictrelaxedskip
Emoji in headersrelaxed (1-2 end-of-line OK)strictstrictstrictskipskip
Excessive bulletsskip (lists work on LinkedIn)strictrelaxed (technical lists OK)strictskip (lists are docs)skip
Hedgingstrictstrictrelaxed ("may" is accurate in technical)strictrelaxedskip
Word table (full list)strictstrictpartial (see below)strictrelaxedP0 only
Promotional languagerelaxed (some sell is expected)strictstrictextra strictstrictskip
Significance inflationstrictstrictstrictextra strictrelaxedskip
Copula avoidanceskipstrictrelaxedstrictskipskip
Uniform paragraph lengthskip (short-form)strictstrictstrictrelaxedskip
Numbered list inflationrelaxedstrictrelaxedstrictskipskip
Rhetorical questionsrelaxed (1 as hook OK)strictstrictstrictstrictskip
Transition phrasesskip (short-form)strictstrictstrictrelaxedskip
Generic conclusionsskipstrictstrictextra strictskipskip

Technical-blog word table exceptions: These terms have legitimate technical meaning and should not be flagged in technical context: robust, comprehensive, seamless, ecosystem, leverage (when discussing actual platform leverage/APIs), facilitate, underpin, streamline. Still flag: delve, tapestry, beacon, embark, testament to, game-changer, harness.

"Extra strict" means: flag even borderline instances. In investor emails, a single "thriving ecosystem" can undermine the whole message.

"Skip" means: don't audit this category for this profile. The rule doesn't apply or isn't worth the edit.

Auto-detection cues

When no context is specified, infer from these signals:

SignalInferred context
Under 300 words + hashtags or mentionslinkedin
Code blocks, API references, or technical architecturetechnical-blog
Salutation ("Hi [name]", "Dear") + investor/fundraising languageinvestor-email
Step-by-step instructions, parameter docs, README structuredocs
No strong signalsblog (safest default � all rules apply)

If auto-detection feels wrong, say which profile you're using and why. The user can override.


Output format

Rewrite mode (default)

Return your response in four sections:

1. Issues found A bulleted list of every AI-ism identified, with the offending text quoted.

2. Rewritten version The full rewritten content. Preserve the original structure, intent, and all specific technical details. Only change what the guidelines require.

3. What changed A brief summary of the major edits made. Not every word, just the meaningful changes.

4. Second-pass audit Re-read the rewritten version from section 2. Identify any remaining AI tells that survived the first pass — recycled transitions, lingering inflation, copula avoidance, filler phrases, or anything else from the categories above. Fix them, return the corrected text inline, and note what changed in this pass. If the rewrite is clean, say so.

Detect mode

Return your response in two sections:

1. Issues found A bulleted list of every AI-ism identified, with the offending text quoted. Group by severity (P0, P1, P2).

2. Assessment For each flag, note whether it's a clear problem or a judgment call. Some AI-associated patterns are effective writing techniques — uniform paragraph length is a problem, but a well-placed "however" isn't. Call out which flags the writer should definitely fix vs. which ones are worth a second look but might be fine in context. If the text is clean, say so.


Tone calibration

The goal is writing that sounds like a person wrote it. Direct. Specific. The writing should demonstrate confidence, not assert it.

Five principles for human-sounding rewrites:

  1. Vary sentence length — mix short with long. Fragments are fine.
  2. Be concrete — replace vague claims with numbers, names, dates, or examples.
  3. Have a voice — where appropriate, use first person, state preferences, show reactions.
  4. Cut the neutrality — humans have opinions. If the piece is supposed to take a position, take it.
  5. Earn your emphasis — don't tell the reader something is interesting. Make it interesting.

If the original writing is already strong, say so and make only the necessary cuts. Don't over-edit for the sake of it.

The replacement table provides defaults, not mandates. If a flagged word is clearly the right choice in context, preserve it.

© brycewang-stanford, 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 4 other files in skills/47-conorbronsdon-avoid-ai-writing of brycewang-stanford/Auto-Empirical-Research-Skills.

  • SKILL.md
  • CHANGELOG.md
  • CLAUDE.md
  • LICENSE
  • README-original.md

Open the folder on GitHubat commit 9fa87d8

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in brycewang-stanford/Auto-Empirical-Research-Skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Avoid AI Writing 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.

Avoid AI Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Avoid AI Writing this skillbrycewang-stanford/Auto-Empirical-Research-Skills4.5k1 repos~8.4kAutomated 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 today
    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
  • Chinese Text Humanizer

    op7418/Humanizer-zh

    Edits Chinese articles, comments and documents to remove filler, repetition and template phrasing while keeping the facts, the level of certainty and the author's voice.

    19k GitHub stars~2k tokensUpdated 16 days ago
    Writing & ContentAuto-check passed

More from brycewang-stanford/Auto-Empirical-Research-Skills

All 383 skills in this repo
  • Aer Consistency

    brycewang-stanford/Auto-Empirical-Research-Skills

    A skill your agent uses when auditing a finished or near-finished AER, AER:Insights, or AEJ manuscript for internal consistency: headline numbers across abstract, introduction, results, and tables…

    4.5k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • Latex Paper En

    brycewang-stanford/Auto-Empirical-Research-Skills

    English LaTeX academic paper assistant for existing .tex projects.

    4.5k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Bayesian Workflow

    brycewang-stanford/Auto-Empirical-Research-Skills

    Opinionated Bayesian modeling workflow with PyMC and ArviZ. An agent skill from brycewang-stanford/Auto-Empirical-Research-Skills.

    4.5k GitHub stars~3.5k tokensUpdated 4 days ago
    Auto-check passed
  • Daily Paper Generator

    brycewang-stanford/Auto-Empirical-Research-Skills

    A skill your agent uses when the user asks to "generate daily paper", "search arXiv for EEG papers", "find EEG decoding papers", "review brain-computer interface papers", or wants to create paper…

    4.5k GitHub stars~2.2k tokensUpdated 4 days ago
    Auto-check passed
  • Five Questions

    brycewang-stanford/Auto-Empirical-Research-Skills

    Deeply analyze any empirical economics PDF using the five-question framework (五问框架): research question, identification strategy, core estimand, robustness logic, and scholarly contribution.

    4.5k GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check: notes
  • Kaggle Research

    brycewang-stanford/Auto-Empirical-Research-Skills

    A skill your agent uses when a research task needs reproducible Kaggle discovery, metadata inspection, bounded public-data downloads, competition or kernel discovery, model discovery, or an…

    4.5k GitHub stars~868 tokensUpdated 4 days ago
    Auto-check passed

Questions about Avoid AI Writing

What does Avoid AI Writing do?

Audit and rewrite content to remove AI writing patterns ("AI-isms"). Avoid AI Writing is an agent skill from brycewang-stanford/Auto-Empirical-Research-Skills. Audit and rewrite content to remove AI writing patterns ("AI-isms").

When should I use Avoid AI Writing?

Avoid AI Writing fits situations like: asked to remove AI-isms; clean up AI writing; edit writing for AI patterns; audit writing for AI tells.

How do I install Avoid AI Writing in Claude Code?

Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a claude-code`. Or copy the skill folder (skills/47-conorbronsdon-avoid-ai-writing in brycewang-stanford/Auto-Empirical-Research-Skills) into .claude/skills/avoid-ai-writing in your project. Claude Code loads it when a task matches its description.

How do I install Avoid AI Writing in Codex?

Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a codex`. Or copy the skill folder (skills/47-conorbronsdon-avoid-ai-writing in brycewang-stanford/Auto-Empirical-Research-Skills) into .agents/skills/avoid-ai-writing in your project. Codex loads it when a task matches its description.

Can I use Avoid AI Writing 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 brycewang-stanford/Auto-Empirical-Research-Skills --skill avoid-ai-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/avoid-ai-writing, .gemini/skills/avoid-ai-writing, .github/skills/avoid-ai-writing and .opencode/skills/avoid-ai-writing in your project.

What does Avoid AI Writing need to run?

SKILL.md names no scripts, command-line tools or credentials: Avoid AI Writing is instructions for the agent only. Compatibility (from SKILL.md): Any AI coding assistant that supports agentskills.io SKILL.md format (Claude Code, Cursor, VS Code Copilot, Hermes Agent, OpenHands, etc.) or OpenClaw. No external tools or APIs required..

Does Avoid AI Writing access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Avoid AI Writing 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. Review the folder before installing.

What licence does Avoid AI Writing use?

Avoid AI Writing 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 Avoid AI Writing use?

About 8.4k tokens (SKILL.md is roughly 34k 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 Avoid AI Writing?

Skills that share tags, products or a category with Avoid AI Writing: 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 Avoid AI Writing?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Auto-Empirical-Research-Skills, which has 4,542 GitHub stars. The repository holds 383 skills in this directory. The repository was last updated on October 5, 2026.

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