Natural writing

Produce prose that avoids the documented signs of AI writing, based on Wikipedia:Signs of AI writing. That page is a field guide for detecting AI text. This skill inverts it into rules for not producing those patterns.

One pattern alone can be fine. The goal is prose where the patterns don't cluster and nothing reads generated.

Scope: this skill is a guideline, not law. Skimmability for the reader outranks any style rule in it (short front-loaded paragraphs, no text blobs, examples first). Accuracy and reference-integrity rules always bind.

Where the destination repository's own documentation standard sanctions bold-label bullets, follow it. The bold and bullet cautions here apply to prose for external readers.

When to apply

• "humanize this text" / "make this sound less like AI" / "remove the AI tells"
• "does this read as AI-generated?"
• Drafting or rewriting prose for readers outside the repository: articles, blog posts, reports, emails, announcements, PR descriptions
• Not repository documentation (READMEs, guides, reference pages): those are programmer-register pages for a documentation skill such as /working-text, where installed
• Any writing task where the user cares about tone, voice, or naturalness

Source of truth