# Remove AI Patterns

Remove AI-writing patterns ("AI-isms") from text using the avoid-ai-writing catalog...

- Repository: https://github.com/pchalasani/claude-code-tools (2026 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add pchalasani/claude-code-tools --skill remove-ai-patterns -g -a claude-code -y`
Codex: `npx skills add pchalasani/claude-code-tools --skill remove-ai-patterns -g -a codex -y`
Cursor: `npx skills add pchalasani/claude-code-tools --skill remove-ai-patterns -g -a cursor -y`
Gemini CLI: `npx skills add pchalasani/claude-code-tools --skill remove-ai-patterns -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add pchalasani/claude-code-tools`

## Description

Remove AI-writing patterns ("AI-isms") from text using the avoid-ai-writing catalog (conorbronsdon/avoid-ai-writing). Use ONLY when the user explicitly asks to remove AI patterns / AI-isms, "make this sound less like AI", "de-AI this text", or invokes remove-ai-patterns by name. Supports detect-only audit, edit-in-place, voice profiles (casual / professional / technical / warm / blunt), and iterate-to-convergence. NOT for clarity/composition rules or formal technical-prose polish, use agent-style for that. Do not auto-trigger for ordinary writing or editing tasks.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# remove-ai-patterns

Thin wrapper around Conor Bronsdon's `avoid-ai-writing` skill (MIT
licensed). A pinned snapshot of the upstream catalog and detector is
vendored at `upstream/` inside this skill directory (commit recorded in
`upstream/UPSTREAM-PIN`), so the skill works offline and deterministically.

## How to run

1. Read `upstream/SKILL.md` (the full pattern catalog, tiered word lists, and
   mode definitions) and follow it. It defines the modes: detect-only,
   edit-in-place for files, optional voice profile, and an
   iterate-to-convergence pass.
2. For a deterministic, machine-checkable audit, run the bundled detector
   (requires Node.js, no npm install needed). Resolve it by the skill's own
   absolute path, NOT a bare relative path: the command runs from the
   user's current working directory, so `node scripts/detect.js` would fail
   with `MODULE_NOT_FOUND`. You already know this skill's directory (you
   just read this SKILL.md from it), so set it once and reuse it. Under a
   Claude Code plugin install `${CLAUDE_PLUGIN_ROOT}` gives the plugin root;
   under Codex (where that variable is unset) or a direct skill install,
   substitute the absolute path of the directory holding this file:

   ```bash
   # Claude Code plugin install:
   SKILL_DIR="${CLAUDE_PLUGIN_ROOT}/skills/remove-ai-patterns"
   # Codex plugin or direct skill install: the absolute path of the
   # directory this SKILL.md lives in (it ends in skills/remove-ai-patterns;
   # the plugin root already is the writing plugin, so there is no extra
   # plugins/writing segment). Direct installs are simpler, e.g.
   #   SKILL_DIR="$HOME/.local/share/agent-skills/remove-ai-patterns"

   node "$SKILL_DIR/scripts/detect.js" FILE
   ```

The rest: https://github.com/pchalasani/claude-code-tools/blob/HEAD/plugins/writing/skills/remove-ai-patterns/SKILL.md