agentleFS
VepricovVepricov/claude-brainlab/skills/writing-anti-ai/SKILL.md

writing-anti-ai

Skill35 starsChanged 2 months agoMITView on GitHub

This skill should be used when the user asks to "remove AI writing patterns", "humanize this text", "make this sound more natural", "remove AI-generated traces", "fix robotic writing", or needs to eliminate AI writing patterns from prose. Based on Wikipedia's "Signs of AI writing" guide, detects and fixes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, AI vocabulary, negative parallelisms, and excessive conjunctive phrases.

4 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 14 are common, 0 are distinctive, and 4 are very specific to this project.

  • 14

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Remove AI-generated writing patterns from text to make it sound natural and human-written.

    line 12
  2. Very specific:

    No em dashes: Never use ---, --, or — in any form.

    line 40
  3. Very specific:

    No emphasis markup: Never use \emph{}, \textbf{}, or \textit{} in new text.

    line 41
  4. Very specific:

    No semicolons: Never use ; to join clauses.

    line 42
  5. Common:

    Remove throat-clearing openers and emphasis crutches.

    line 45
  6. Common:

    Avoid binary contrasts, dramatic fragmentation, rhetorical setups.

    line 53
  7. Common:

    If it sounds like a pull-quote, rewrite it.

    line 74
  8. Common:

    Every sentence is the same length and structure

    line 110
  9. Common:

    No opinions, just neutral reporting

    line 111
  10. Common:

    No acknowledgment of uncertainty or mixed feelings

    line 112
  11. Common:

    No first-person perspective when appropriate

    line 113
  12. Common:

    No humor, no edge, no personality

    line 114
  13. Common:

    Have opinions: Don't just report facts—react to them.

    line 118
  14. Common:

    Preserve meaning: - Keep core message intact

    line 136
  15. Common:

    Use progressive disclosure (core rules here, details in references/)

    line 186
  16. Common:

    Add specific details instead of vague claims

    line 188
  17. Very specific:

    Use simple constructions (is/are/have) where appropriate

    line 189
  18. Common:

    Leave stereotypic structures intact

    line 193

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Writing Anti-AI

Remove AI-generated writing patterns from text to make it sound natural and human-written.

Overview

This skill identifies and eliminates predictable AI writing patterns from prose, based on Wikipedia: Signs of AI writing, maintained by WikiProject AI Cleanup.

Core insight: LLMs use statistical algorithms to predict what should come next. The result tends toward the most statistically likely outcome that applies to the widest variety of cases—creating detectable patterns.

When to Use This Skill

Trigger phrases:

  • "Humanize this text"
  • "Remove AI writing patterns"
  • "Make this sound more natural"
  • "This sounds robotic/AI-generated"
  • "Fix the AI patterns"

Use cases:

  • Editing AI-generated content to sound human
  • Reviewing text for AI patterns before publication
  • Polishing academic or professional writing
  • Removing "slop" from prose

Core Rules

0. Hard Bans for Academic Paper Text (LaTeX)

These three rules are absolute — no exceptions:

  • No em dashes: Never use ---, --, or — in any form. Replace with a comma, period, or rewrite the sentence.
  • No emphasis markup: Never use \emph{}, \textbf{}, or \textit{} in new text. State the point directly without typographic emphasis.
  • No semicolons: Never use ; to join clauses. Split into two sentences with a period instead.

1. Cut Filler Phrases

Remove throat-clearing openers and emphasis crutches.

Examples:

  • "In order to achieve this goal" → "To achieve this"
  • "Due to the fact that" → "Because"
  • "It is important to note that" → (delete)

2. Break Formulaic Structures

Avoid binary contrasts, dramatic fragmentation, rhetorical setups.

Patterns to avoid:

  • Negative parallelisms: "It's not just X, it's Y"
  • Rule of three: "A, B, and C" (prefer two or four items)
  • Em-dash reveals: "X—Y" (just use commas — or better, rewrite)

3. Vary Rhythm

Mix sentence lengths. End paragraphs differently.

Check:

  • Three consecutive sentences same length? Break one.
  • Paragraph ends with punchy one-liner? Vary it.

4. Trust Readers

State facts directly. Skip softening, justification, hand-holding.

Bad: "It could potentially be argued that the policy might have some effect." Good: "The policy may affect outcomes."

5. Cut Quotables

If it sounds like a pull-quote, rewrite it.

Bad: "This represents a major step in the right direction." Good: "The company plans to open two more locations."

Common AI Patterns

Content Patterns

PatternDescription
Undue emphasis"stands as a testament", "crucial role"
Promotional language"vibrant", "rich heritage", "breathtaking"
Vague attributions"Experts believe", "Observers note"
Superficial -ing analyses"highlighting the importance", "ensuring that"
Formulaic "challenges" sections"Despite X, faces challenges"

Language Patterns

PatternDescription
AI vocabularyAdditionally, crucial, delve, enhance, landscape
Copula avoidance"serves as", "stands for", "represents"
Em dash overuseUsing — more than humans
Rule of threeForcing ideas into groups of three
Elegant variationExcessive synonym substitution

For comprehensive pattern lists, see:

  • references/patterns-english.md - Complete English pattern reference
  • references/patterns-chinese.md - Complete Chinese pattern reference

Personality and Soul

Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as obvious.

Signs of soulless writing:

  • Every sentence is the same length and structure
  • No opinions, just neutral reporting
  • No acknowledgment of uncertainty or mixed feelings
  • No first-person perspective when appropriate
  • No humor, no edge, no personality

How to add voice:

Have opinions. Don't just report facts—react to them.

"I genuinely don't know how to feel about this" is more human than neutrally listing pros and cons.

Vary your rhythm. Short punchy sentences. Then longer ones that take their time.

Acknowledge complexity. Real humans have mixed feelings.

"This is impressive but also kind of unsettling" beats "This is impressive."

Use "I" when it fits. First person isn't unprofessional—it's honest.

"I keep coming back to..." signals a real person thinking.

Workflow

  1. Identify patterns - Scan for AI patterns listed above
  2. Rewrite sections - Replace AI-isms with natural alternatives
  3. Preserve meaning - Keep core message intact
  4. Maintain voice - Match intended tone (formal, casual, technical)
  5. Add soul - Inject personality and opinions

Quick Scoring

Rate the text 1-10 on each dimension (max 50):

DimensionQuestionScore
DirectnessDirect statements or announcements?/10
RhythmVaried or metronomic?/10
TrustRespects reader intelligence?/10
AuthenticitySounds human?/10
DensityAnything cuttable?/10

Standard:

  • 45-50: Excellent, AI patterns removed
  • 35-44: Good, room for improvement
  • Below 35: Needs revision

Examples

See examples/ for before/after transformations:

  • examples/english.md - English text examples

Quick Reference

Common Fixes:

BeforeAfter
"serves as a testament to""shows"
"Moreover, it provides""It adds"
"It's not just X, it's Y""X does Y"
"Industry experts believe""According to [specific source]"

Additional Resources

Reference Files

  • references/patterns-english.md - Complete English pattern reference
  • references/phrases-to-cut.md - Filler phrases to remove
  • references/wikipedia-source.md - Original Wikipedia source material

Example Files

  • examples/english.md - English before/after examples

Best Practices

✅ DO:

  • Combine pattern detection with soul injection
  • Use progressive disclosure (core rules here, details in references/)
  • Vary sentence structure and rhythm
  • Add specific details instead of vague claims
  • Use simple constructions (is/are/have) where appropriate

❌ DON'T:

  • Just remove patterns without adding voice
  • Leave stereotypic structures intact
  • Over-correct and lose the original meaning
  • Ignore language-specific patterns
  • Make all sentences the same length

License

MIT

Attribution

Based on Wikipedia: Signs of AI writing, maintained by WikiProject AI Cleanup. Merges content from humanizer, humanizer-zh, and stop-slop skills.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.