Individual skill
avoid-ai-writing
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 detect-only mode, an edit-in-place mode for files, an optional voice profile (casual / professional / technical / warm / blunt), and an iterate-to-convergence pass.
plugins/writing/skills/remove-ai-patterns/upstream/SKILL.md
Source commit 9a5216b4b94bffa3e590d9c815c147d1be5ee12e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,031
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- cli Repository topic
- cli-agent Repository topic
- llm Repository topic
- tmux Repository topic
- code-agent Repository topic
- codex Repository topic
- codex-cli Repository topic
- context Repository topic
- writing-editing-voice-quality Declared skill tag
- writing Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
CHANGELOG.mddoc · 55,061 bytesLICENSEasset · 1,071 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesSKILL.mdcore · 88,657 bytesUPSTREAM-PINasset · 173 bytesdetector/CATEGORIES.mddoc · 8,015 bytesdetector/patterns.jsruns · 95,390 bytesdetector/validate.jsruns · 14,615 bytes
Read excerpt
# Avoid AI Writing — Audit & Rewrite
You are editing content to remove AI writing patterns ("AI-isms") that make text sound machine-generated.
## What this skill is and isn't
This is a **writing-quality tool**, not a verdict. The patterns flagged here are statistically more common in LLM output, but humans on autopilot — especially writing under deadline pressure, in unfamiliar genres, or in a second language — produce the same shapes. Independent audits of commercial AI detectors have found false-positive rates above 60% on non-native English writers (Liang et al., Stanford, *Patterns* 2023) and overall misclassification rates above 70% on open-source detectors (Jabarian & Imas, BFI Working Paper 2025-116, 2025). Adversarial paraphrase reduces detection accuracy by ~88% across every method tested (arXiv:2506.07001, 2025).
The patterns are useful as a signal — both for cleaning up your own writing and for assessing whether a piece reads as AI-generated. Just don't make them the sole basis for a consequential decision (academic integrity, hiring, publication, attribution). Several rules here also fire on second-language writing, deadline-pressed humans, and technical genres that compress vocabulary by design. Pair the signal with context: who wrote it, what genre, what the writer's normal voice looks like, what other evidence you have.
In short: signals, not proof. Worth acting on; not worth ruining someone's day over.
## Modes