Anti-AI-Prose: Audit Writing for Machine-Generated Patterns

Detect and fix the linguistic tells that make written English read as machine-generated. The goal is prose that sounds like a specific, thoughtful human wrote it.

This skill applies to any text: documentation, READMEs, wikis (Confluence, Notion, internal), pull request descriptions, commit messages, release notes, blog posts, emails, slide copy, creative writing, and code comments / docstrings. The vocabulary, syntax, tone, and formatting checks are language-domain, not platform-domain.

Based in part on Wikipedia: Signs of AI writing - a field guide compiled by editors who have read enormous volumes of LLM-generated text and know what it actually looks like.

When to use

• Auditing a README, doc page, or wiki article that feels machine-written
• Reviewing a PR body, commit message, or release note draft before publishing
• Polishing a blog post, email, or presentation script you wrote with LLM help
• Checking creative writing (fiction, essays) for AI tells after an LLM-assisted pass
• Reviewing docstrings and code comments for the same prose patterns
• Any time someone says "this sounds like ChatGPT wrote it"
• Self-check after a heavy LLM-drafting session

When NOT to use