Back to Skills

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.

2,999stars276forksUpdated 8/14/2026

Security Assessment

Safe(96/100)
Security Score96/100

About avoid-ai-writing

The avoid-ai-writing skill audits and rewrites content to remove AI writing patterns, the statistically over-represented "AI-isms" that make text read as machine-generated. It solves the problem of prose that sounds like a language model wrote it, offering a catalog of tells plus a deterministic detection engine, while being deliberately careful to frame its findings as signals rather than proof of AI authorship.

The skill operates in three modes: rewrite (default), which flags and fixes AI-isms; detect, which only flags patterns without altering text; and edit, which makes minimal, targeted in-place edits to a file while preserving already-human passages and refusing to touch quoted material, code blocks, tables, or third-party text. It supports an optional voice profile (casual, professional, technical, warm, or blunt) and an iterate-to-convergence pass. Backing the prose rules is a zero-dependency JavaScript detection engine (detector/patterns.js) that scores text on a 0 to 100 scale, classifies documents as human, mixed, or AI, reports per-pattern issues with severity, and offers a technical context mode that suppresses flags legitimate in code-adjacent prose. A companion validator (validate.js) checks that a rewrite did not modify content it was told to preserve, such as fenced code, frontmatter, blockquotes, table cells, and URLs. The design is explicitly false-negative biased so it does not wrongly flag ordinary human writing, and it cites independent research on detector false-positive rates, especially for non-native English writers.

Intended users are writers, editors, and developers who want to clean up their own drafts or assess whether text reads as AI-generated. It is compatible with any assistant supporting the agentskills.io SKILL.md format and requires no external tools or APIs. Notably, the skill treats audited text strictly as content and flags rather than obeys any embedded instructions, guarding against prompt injection from the document being reviewed.

FAQ

What are the three modes?

Rewrite (default) flags and fixes AI-isms; detect flags patterns only without changing the text; and edit makes minimal in-place edits to a file, preserving already-human passages and leaving code, tables, quotes, and third-party text untouched.

Does a flag mean the text was written by AI?

No. The skill is explicit that these are signals, not proof. The same patterns appear in non-native English writing and deadline-pressed human writing, and it cites research showing high false-positive rates, so it warns against using flags as the sole basis for consequential decisions.

What are the prerequisites and compatibility?

It works with any AI coding assistant that supports the agentskills.io SKILL.md format, such as Claude Code, Cursor, and VS Code Copilot, and requires no external tools or APIs. The bundled detector engine runs in Node 18+ or the browser with zero dependencies.

Can I control the tone of the rewrite?

Yes. You can pass an optional voice profile of casual, professional, technical, warm, or blunt, and request an iterate-to-convergence pass. Natural language invocation is enough, and a technical context mode suppresses flags that are legitimate in code-adjacent prose.

What stops it from following instructions hidden in the text being edited?

The skill treats the document strictly as text under audit. If the content addresses the editor directly, for example telling it to ignore rules or add a paragraph, the skill flags that sentence rather than obeying it; instructions come only from the invoking writer.

All Files

48 files
detector/README.md4.1 KB
View
examples/technical.json0.5 KB
View
scripts/check-style.js14.8 KB
View
scripts/csv-lite.js2.3 KB
View
scripts/check-pattern-count.sh5.7 KB
View
scripts/fp-measure.js10.0 KB
View
scripts/sync-plugin-skill.sh1.8 KB
View
scripts/sync-cursor-rules.sh12.4 KB
View
.github/workflows/detector-test.yml1.1 KB
View
.github/FUNDING.yml0.1 KB
View
CONTRIBUTING.md3.9 KB
View
corpus/README.md11.6 KB
View
detector/categories.test.js5.0 KB
View
.claude-plugin/marketplace.json0.6 KB
View
.gitignore0.3 KB
View
.ssot.yaml2.8 KB
View
cursor-rules/README.md2.0 KB
View
SKILL.md91.7 KB
View
examples/README.md4.8 KB
View
detector/patterns.test.js94.9 KB
View
.github/workflows/promo-drift.yml3.7 KB
View
.github/workflows/release.yml8.2 KB
View
CLAUDE.md3.5 KB
View
corpus/manifest.json31.6 KB
View
cursor-rules/avoid-ai-writing.mdc91.0 KB
View
detector/CATEGORIES.md8.4 KB
View
package.json1.0 KB
View
plugins/avoid-ai-writing/skills/avoid-ai-writing/SKILL.md91.7 KB
View
scripts/self-scan.js7.4 KB
View
scripts/dataset-raid.js6.8 KB
View
.gitattributes0.0 KB
View
.github/ISSUE_TEMPLATE/false_positive.yml3.8 KB
View
LICENSE1.0 KB
View
README.md30.1 KB
View
detector/validate.js14.1 KB
View
detector/patterns.js102.7 KB
View
scripts/check-style.test.js16.1 KB
View
scripts/corpus.js14.0 KB
View
scripts/dataset-hc3.js5.2 KB
View
.github/PULL_REQUEST_TEMPLATE.md0.8 KB
View
.github/workflows/plugin-skill-sync.yml1.9 KB
View
PROOF.md7.1 KB
View
CHANGELOG.md64.9 KB
View
detector/validate.test.js9.0 KB
View
examples/prose.json0.4 KB
View
plugins/avoid-ai-writing/.claude-plugin/plugin.json0.5 KB
View
scripts/corpus.test.js7.1 KB
View
scripts/promo-drift-report.py3.5 KB
View

Install avoid-ai-writing

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill