conorbronsdon/avoid-ai-writing

▲ 42 stars today★ 5,542⑂ 477

Skill that audits and rewrites content to remove AI writing patterns. Use it with your favorite agents including Claude Code, OpenClaw, Codex, and Hermes.

About conorbronsdon/avoid-ai-writing

conorbronsdon/avoid-ai-writing is an open-source project on GitHub, mainly written in JavaScript. Skill that audits and rewrites content to remove AI writing patterns. Use it with your favorite agents including Claude Code, OpenClaw, Codex, and Hermes. It currently holds 5,542 stars and 477 forks with 17 open issues, and was last pushed on 2026-11-09 (repository created 2026-03-06).

Project Overview

Git Homed tracks it on the Today's Trending board, currently at rank #88 with 42 new stars today.

GitHub Repository Details

Repository conorbronsdon/avoid-ai-writing · default branch main · size 6081 KB · watchers 24 · source: GitHub REST API and repository README

README

avoid-ai-writing

Audit & rewrite content to remove AI writing patterns. A practical skill for any AI agent. Supports detect-only and edit-in-place modes, plus voice profiles.

GitHub stars License: MIT npm version detector Podcast X

https://github.com/conorbronsdon/avoid-ai-writing/blob/HEAD/The bundled detector engine flagging 13 AI-writing patterns by category in a sample paragraph, then scoring the clean rewrite 0/100

---

A portable writing skill for Claude Code, Codex, OpenClaw, Hermes, and any other agentskills.io-compatible agent. Audits and rewrites content to remove AI writing patterns ("AI-isms").

The rules and bundled detector are calibrated for English. See community language adaptations for independently maintained versions in other languages.

Three modes:

Use --iterate 1|2 to set the editing-pass ceiling. --iterate 1 allows the initial rewrite only. --iterate 2 uses the default maximum of an initial rewrite plus one correction or preservation repair, and stops early when no justified in-scope edit remains. Checks do not consume a pass, but any change they prompt does. The skill reports how many editing passes it used and any intentional, protected, or unresolved finding.

An optional voice profile (casual / professional / technical / warm / blunt) sets how the prose should sound, independent of the audience context profile.

The glossary defines the terms these docs use: word tiers, severity tiers, modes, profiles, and detector options.

Table of contents

Quick demo

Input:

Certainly! Acme Analytics, a vibrant startup nestled in the heart of Boulder's thriving tech ecosystem, has secured $40M in Series B funding — marking a watershed moment for the observability landscape. The platform serves as a unified hub, featuring real-time dashboards, boasting sub-second queries, and presenting a seamless integration layer. Moreover, experts believe Acme is poised to disrupt the market. In conclusion, the future looks bright!

Final rewrite:

Acme Analytics, a Boulder-based startup, raised a $40M Series B. Its observability platform has real-time dashboards, runs queries in under a second, and includes an integration layer.

Verification: One editing pass. Review found no further justified in-scope edit; no deterministic preservation check ran in this prose-only demo.

What it caught: the chatbot opener ("Certainly!"), promotional modifiers, inflated significance, roundabout verbs, vague attribution, and the generic conclusion. The rewrite keeps the funding, location, and three product capabilities. It removes the unsupported market prediction without inventing an investor or an integration mechanism.

Why a skill, not just a prompt

A one-shot "make this sound human" prompt catches the obvious stuff. This skill is different:

Installation & Usage

Install the complete skill directory

Use the plugin install below or clone the repository into your agent's skills directory. Keep SKILL.md with references/patterns.md: the entry file loads the catalog before auditing. The bundled scripts/, detector/, and examples/ provide optional mechanical verification.

For a single-file rules field, use dist/avoid-ai-writing.md (about 138 KB). It includes every rule and profile, with manual fallbacks for commands unavailable outside the bundle. Some rules and instructions fields hold far less than that, so check the size limits under Other agents before pasting. Do not copy the slim entry file alone. Older installers that fetch only root SKILL.md omit its required reference; use a directory install instead.

Claude Code

Option 1: Clone into skills directory

git clone https://github.com/conorbronsdon/avoid-ai-writing ~/.claude/skills/avoid-ai-writing

Then invoke it with /avoid-ai-writing .

Option 2: Copy a self-contained file

Download dist/avoid-ai-writing.md and place it in any directory that Claude Code can read. Reference it in your CLAUDE.md:

- Editing for AI patterns → read path/to/avoid-ai-writing.md

Option 3: Use as a slash command

Optional alias. Claude Code names a command after its file, so use a different name from avoid-ai-writing. If you've done Option 1, the skill already answers to /avoid-ai-writing and a command file with the same name would collide with it. Create a command file (e.g., ~/.claude/commands/clean-ai-writing.md):

---
description: Audit and rewrite content to remove AI writing patterns
---

$ARGUMENTS

Read and follow the instructions in ~/.claude/skills/avoid-ai-writing/SKILL.md

Then use /clean-ai-writing in Claude Code.

Claude Cowork — install as a plugin

Cowork loads skills only from installed plugins — it doesn't scan ~/.claude/skills/, so a bare clone (the Claude Code steps above) won't be discovered there. This repo doubles as a single-plugin marketplace, so install it as a plugin instead:

/plugin marketplace add conorbronsdon/avoid-ai-writing
/plugin install avoid-ai-writing@conorbronsdon-skills
/reload-plugins   # or restart the session, to activate the skill

In the Cowork desktop app, do the same from Customize → Plugins → Add marketplace from GitHub (conorbronsdon/avoid-ai-writing), then install avoid-ai-writing. The skill auto-triggers from phrases like "remove AI-isms." New releases arrive when the plugin's version is bumped — run /plugin marketplace update to pull them.

The same plugin install works in Claude Code if you'd rather have a versioned, updatable plugin than the file clone above.

Prefer not to install a plugin? Copy dist/avoid-ai-writing.md into a folder connected to your Cowork session and tell the agent to follow ./avoid-ai-writing.md — works as a one-off, no auto-trigger.

OpenClaw

Option 1: Install from ClawHub

clawhub install avoid-ai-writing

Option 2: Clone into skills directory

git clone https://github.com/conorbronsdon/avoid-ai-writing ~/.openclaw/skills/avoid-ai-writing

Cursor

Drop the ported rule into your project's .cursor/rules/:

mkdir -p .cursor/rules
curl -o .cursor/rules/avoid-ai-writing.mdc \
  https://raw.githubusercontent.com/conorbronsdon/avoid-ai-writing/main/cursor-rules/avoid-ai-writing.mdc

See cursor-rules/README.md for activation globs and trigger phrases. Functionally identical to the Claude Code skill — same tier vocabulary, same context profiles, same modes.

Hermes

Drop the skill into Hermes's skills directory — it then appears automatically as /avoid-ai-writing, no registration needed:

git clone https://github.com/conorbronsdon/avoid-ai-writing ~/.hermes/skills/writing/avoid-ai-writing

OpenAI Codex

Codex reads Agent Skills in the same SKILL.md format. Put it in .agents/skills/ at the repo root, or ~/.agents/skills/ to use it across all your projects:

git clone https://github.com/conorbronsdon/avoid-ai-writing .agents/skills/avoid-ai-writing

Native ChatGPT and Codex plugin package

Published in the OpenAI Plugins Directory; install it there for ChatGPT or Codex.

The plugin package keeps the canonical SKILL.md as its editorial authority and provides seven focused Skills:

From a cloned checkout, build and validate the package with:

python3 scripts/package-openai-plugin.py . /tmp/avoid-ai-writing.zip --json
python3 scripts/validate-openai-plugin.py . --json

Other agents

Use the destination below for your tool. Measure the downloaded file with wc -c dist/avoid-ai-writing.md for its exact UTF-8 byte count before comparing byte limits; character limits count characters instead.

| Tool | Where to put it | Size limit | |------|-----------------|------------| | Windsurf | clone the skill directory into .devin/skills/avoid-ai-writing/ (.windsurf/skills/avoid-ai-writing/ is also supported) (skills docs) | Workspace rule files are limited to 12,000 characters (rules docs), so the single file does not fit in .windsurf/rules/ | | Cline | .clinerules/avoid-ai-writing.md | None documented; rules use context tokens on every task (docs) | | GitHub Copilot (VS Code) | paste into .github/copilot-instructions.md | None documented (docs) | | Claude.ai Projects | paste dist/avoid-ai-writing.md into the project's custom instructions | None documented (docs) | | ChatGPT | install the native plugin package, or upload dist/avoid-ai-writing.md as a Custom GPT Knowledge file | A Custom GPT's Instructions field holds far less than the file; do not paste it there |

For a Custom GPT Knowledge upload, add a short instruction directing the GPT to consult avoid-ai-writing.md when auditing or rewriting prose. Knowledge files supply reference material; uploading one alone does not activate the skill. Test the GPT in Preview with an example from this README before relying on it (GPT configuration docs).

Triggering the skill

Once installed, ask your assistant to clean up AI writing:

In rewrite mode (default), the skill completes its review and available verification before returning the rewritten text exactly once:

1. Final rewrite — the verified or honestly qualified final version 2. Changes — a short summary when edits were made and the summary is useful 3. Verification — editing passes used, checks that ran, stop reason, and any intentional, protected, source-blocked, or unresolved findings

Ask for a detailed or exhaustive audit to add quoted findings before the final rewrite. The response still contains one full version. Clean input can be returned unchanged with zero editing passes.

In detect mode, the skill returns two sections:

1. Issues found — every AI-ism identified, grouped by severity (P0/P1/P2) 2. Assessment — which flags are clear problems vs. patterns that may be intentional or effective in context

Trigger detect mode with: "detect," "flag only," "audit only," "just flag," "scan," or similar.

Pattern reference

Representative examples from the catalog — not the exhaustive list (that's references/patterns.md). The skill's human-facing prose catalog and the detector engine use different counts on purpose: the engine implements 54 type categories because it splits the vocabulary tiers and adds stylometric/fingerprint signals (punctuation distribution, function-word entropy, bypass-trick detection) that work as math over a document rather than as a rule you'd look up. The two are mapped in detector/CATEGORIES.md; don't "fix" one count to match the other.

Content Patterns

| # | Pattern | Before | After | |---|---------|--------|-------| | 1 | Significance inflation | "marking a pivotal moment in the evolution of..." | State the supported event; do not invent a date or purpose | | 2 | Notability name-dropping | "cited in NYT, BBC, and Wired" | Keep supported citations; remove claims that they prove importance | | 3 | Superficial -ing analyses | "symbolizing... reflecting... showcasing..." | Replace with specific facts or cut | | 4 | Promotional language | "nestled within the breathtaking region" | Keep the supplied location; remove promotional modifiers | | 5 | Vague attributions | "Experts believe it plays a crucial role" | Request the source, or flag the claim for verification | | 6 | Formulaic challenges | "Despite challenges... continues to thrive" | Name the challenge and the response | | 7 | Novelty inflation | "He introduced a term I hadn't heard before" | Keep the personal observation if it matters; do not invent an explanation |

Language Patterns

| # | Pattern | Before | After | |---|---------|--------|-------| | 8 | Word/phrase replacements (3 tiers) | "leverage... robust... seamless... utilize" | "use... reliable... smooth... use" | | 9 | Copula avoidance | "serves as... features... boasts" | "is... has" | | 10 | Synonym cycling | "developers... engineers... practitioners... builders" | "developers" (repeat the clear word) | | 11 | Template phrases | "a [adj] step towards [adj] infrastructure" | Describe the specific outcome | | 12 | Filler phrases | "In order to," "Due to the fact that" | "To," "Because" | | 13 | False ranges | "from the Big Bang to dark matter" | List the actual topics | | 14 | Parenthetical hedging | "tools (like X and Y)" | Name them directly or cut |

Structure Patterns

| # | Pattern | Before | After | |---|---------|--------|-------| | 15 | Formatting | Em dashes (— and --), bold overuse, emoji headers, bullet-heavy | Commas/periods, prose paragraphs | | 16 | Sentence structure | "It's not X, it's Y" + hollow intensifiers + hedging | Direct positive statements | | 17 | Structural issues | Uniform paragraphs, formulaic openings, too-clean grammar | Varied length, lead with the point | | 18 | Transition phrases | "Moreover," "Furthermore," "In today's [X]" | "and," "also," or restructure | | 19 | Inline-header lists | "Speed: Speed improved by..." | Write the point directly | | 20 | Title case headings | "Strategic Negotiations And Partnerships" | "Strategic negotiations and partnerships" | | 21 | Numbered list inflation | "Here are 7 reasons why..." | Cut to the 2-3 that matter | | 22 | False concession | "While X has limitations, it's still remarkable" | State the real tradeoff | | 23 | Rhetorical question openers | "What if there were a better way to...?" | Lead with the claim |

Communication Patterns

| # | Pattern | Before | After | |---|---------|--------|-------| | 24 | Chatbot artifacts | "I hope this helps! Let me know if..." | Remove entirely | | 25 | "Let's" constructions | "Let's explore," "Let's break this down" | Just start with the point | | 26 | Cutoff disclaimers | "While details are limited in available sources..." | Find sources or remove | | 27 | Generic conclusions | "The future looks bright," "Only time will tell" | Specific closing thought or cut | | 28 | Stock reaction framing | "What surprised me most," "I was fascinated to discover" | Keep specific, authentic reactions; cut empty stock framing or make the reaction concrete | | 29 | Reasoning chain artifacts | "Let me think step by step," "Breaking this down" | State conclusion, then evidence | | 30 | Sycophantic tone | "Great question!", "You're absolutely right!" | Remove entirely | | 31 | Acknowledgment loops | "You're asking about," "To answer your question" | Just answer directly | | 32 | Confidence calibration | "It's worth noting," "Interestingly," "Surprisingly" | Let the fact speak for itself |

Meta Patterns

| # | Pattern | Before | After | |---|---------|--------|-------| | 33 | Excessive structure | 5 headers in 200 words, "Overview:", "Key Points:" | Merge sections, use specific headers | | 34 | Rhythm and uniformity | All sentences 15–25 words, all paragraphs same length | Mix short/long, fragments, questions | | 35 | Over-polishing | Every irregularity sanded away, perfectly uniform prose | Keep natural disfluency, varied rhythm | | 36 | Rewrite-vs-patch threshold | 5+ vocabulary flags + 3+ pattern categories + uniform rhythm | Advise full rewrite, not patching |

Structural Detection (v3.4)

Added in v3.4 to catch LLM output that sidesteps the vocabulary tables by substituting synonyms but still leans on structural shapes detectors can identify. Crypto/web3/AI-infra content is where these patterns concentrate most heavily, but the rules generalize to any social-length post.

| # | Pattern | Before | After | |---|---------|--------|-------| | 37 | Tier 3 phrases (multi-word boilerplate) | "the integration of," "decentralized compute," "community-driven," "long-term sustainability" stacked across a piece | Replace the repeated phrase with a specific claim, or vary genuinely. Flagged per-phrase at ≥2 hits, or as a cluster when ≥3 distinct phrases appear | | 38 | Future-narrative closers | "may become one of the most important narratives of the next market cycle" | Pick the falsifiable version. "X may exceed Y by 2027" is a prediction; the template form is not | | 39 | Hedge-stacked predictions | "could potentially create," "may eventually unlock" | Pick

GitHub Stars & Activity

5,542Stars
477Forks
17Open issues
JavaScriptLanguage

GitHub Popularity

GitHub stars5,542
Forks477
Open issues17
Primary languageJavaScript
LicenseMIT
Stars gained today42
Created2026-03-06
Last pushed2026-11-09

Trending History

Daily boardrank #88 · ▲ 42 stars

Related GitHub Projects

1

DietrichGebert / ponytail

JavaScript★ 188,055⑂ 10,437▲ 898 stars
→
2

addyosmani / agent-skills

JavaScript★ 114,755⑂ 11,993▲ 465 stars
→
3

cloudflare / security-audit-skill

JavaScript★ 68,554⑂ 4,515▲ 1,206 stars
→
4

bilawalsidhu / gods-eye-view

JavaScript★ 64,034⑂ 12,615▲ 318 stars
→
5

chinese-poetry / chinese-poetry

JavaScript★ 54,227⑂ 10,931▲ 61 stars
→
6

Anil-matcha / Open-Generative-AI

JavaScript★ 33,758⑂ 6,417▲ 313 stars
→
7

DeanChensj / jiangshan-map

JavaScript★ 5,183⑂ 605▲ 265 stars
→
8

mattpocock / skills

Shell★ 320,257⑂ 26,819▲ 1,223 stars
→

More Trending Repositories