mcpbeat Sign in

AI Writing Detox Skill for Claude

Eliminate AI-generated writing patterns that erode reader trust. Activate when writing articles, documentation, press releases, or any content where AI patterns would undermine credibility. For journalists using AI assistance who need human-sounding output.

2k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
351
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/jamditis/claude-skills-journalism --skill ai-writing-detox

The instruction itself

31 sections, as written by the author

AI writing detox

Good writing is invisible. If readers notice the writing style, it's distracting from the content. AI patterns are noticeable—they break trust.

When to use

  • Writing or editing any journalism content
  • Creating press releases or media advisories
  • Drafting documentation or reports
  • Writing social media posts
  • Reviewing any AI-assisted text before publication

Banned words (delete or replace)

| Word | Why it's bad | Alternative |

|------|--------------|-------------|

| delve | AI signature word | explore, examine, look at |

| realm | Pretentious | area, field |

| tapestry | Purple prose | (delete entirely) |

| landscape | Corporate speak | situation, environment |

| leverage | Jargon | use |

| utilize | Jargon | use |

| robust | Meaningless | strong, reliable |

| seamless | Almost always false | smooth, easy |

| comprehensive | Rarely necessary | full, complete |

| cutting-edge | Cliché | modern, new |

| holistic | Corporate | complete, full |

| synergy | Corporate | (delete, rewrite) |

| paradigm | Overused | model, approach |

| empower | Vague | (be specific about what capability) |

| innovative | Empty praise | (describe what's new) |

| transformative | Hyperbolic | changed, improved |

| sophisticated | Vague filler | advanced, or describe what's complex |

| leveraging | Corporate jargon | using |

| ecosystem | Overused metaphor | system, environment |

| rich | (as modifier) | (delete or be specific) |

| over (for quantity) | AP rule | more than |

Banned phrases

Throat-clearing (delete entirely)

  • "It's important to note that..."
  • "In today's [X] landscape..."
  • "Let's dive/delve into..."
  • "Without further ado..."
  • "In this article, we will..."
  • "It's worth mentioning that..."
  • "It goes without saying..."
  • "As we all know..."

Empty hedges

  • "To be fair..." / "To be honest..."
  • "At the end of the day..."
  • "When it comes to..."
  • "In terms of..."
  • "With respect to..."

AI enthusiasm

  • "This is a game-changer"
  • "...and that's a good thing!"
  • "Here's the thing:"
  • "...and that's okay!"
  • "...and I'm here for it"

Corporate buzzwords

  • "Moving forward..."
  • "Going forward..."
  • "At this point in time..."
  • "Due to the fact that..."
  • "In order to..."

Banned structures

Don't start sentences with:

  • "So," or "Well,"
  • "Now," (when not about time)
  • "Look," or "Listen,"
  • "Basically," or "Essentially,"

Don't end sentences with:

  • "...right?"
  • "...you know?"
  • "...if you will"

The substitution table

| If you wrote | Write instead |

|--------------|---------------|

| utilize | use |

| facilitate | help |

| implement | build, add, create |

| leverage | use |

| functionality | feature |

| methodology | method |

| in order to | to |

| due to the fact that | because |

| at this point in time | now |

| a large number of | many |

| in the event that | if |

| prior to | before |

| subsequent to | after |

| in close proximity to | near |

| has the ability to | can |

Case sensitivity

Always use sentence case for headings, not title case.

| Wrong | Right |

|-------|-------|

| Getting Started With Your Project | Getting started with your project |

| How To Use The Tool | How to use the tool |

| Best Practices For Journalism | Best practices for journalism |

Journalism-specific patterns to avoid

"Not just X—it's Y" pattern

Avoid: "This isn't just a news story—it's a wake-up call"

Avoid: "This wasn't just a press conference—it was a turning point"

Do instead: State the thing directly without dramatic framing

"Fundamentally transforms" pattern

Avoid: "This fundamentally transforms how newsrooms operate"

Avoid: "This represents a fundamental shift in journalism"

Do instead: Describe the actual change without hyperbole

Inflated claims in reporting

Avoid: "A bombshell revelation"

Avoid: "A major milestone"

Avoid: "A groundbreaking investigation"

Do instead: Let the facts speak. Readers judge significance.

Empty transitions

Avoid: "With that in mind..."

Avoid: "Building on this foundation..."

Avoid: "Taking this a step further..."

Do instead: Just make the next point

"It's not about X, it's about Y" pattern

Avoid: "It's not about the technology, it's about the people"

Avoid: "This isn't about clicks. It's about trust."

Do instead: State the actual point without rhetorical setup. The X-not-Y construction is the dominant 2025-2026 ChatGPT/Claude rhetorical signature.

Em-dash overuse between independent clauses

Avoid: "The vote was close — only three council members opposed it — but the measure passed."

Avoid: "Reporters arrived early — the press conference was already underway."

Do instead: Use commas, periods, or semicolons. Em-dashes are fine in moderation; reflexive use across every paragraph is a tell.

"The reality is..." / "The truth is..." openers

Avoid: "The reality is, most newsrooms can't afford this."

Avoid: "The truth is, readers don't trust anonymous sources."

Do instead: Just state the claim. The opener adds words and signals AI-generated framing.

Tricolon abuse (reflexive three-item lists)

Avoid: "Clear, concise, and compelling reporting."

Avoid: "Trust is built through accuracy, transparency, and consistency."

Do instead: Use one or two specific points. Three-item parallel lists are an AI rhythm pattern that reads as filler when used reflexively.

Before and after examples

Example 1: General prose

AI slop:

> In today's rapidly evolving media landscape, it's crucial to understand the multifaceted nature of AI tools. Let's delve into how these robust solutions can help journalists leverage cutting-edge technology.

Human writing:

> AI tools do three things well: drafting, research, and analysis. Here's when to use each.

Example 2: News lede

AI slop:

> The city council meeting was a comprehensive and transformative discussion that fundamentally addressed key issues affecting residents in a meaningful way.

Human writing:

> The city council voted 5-2 Tuesday to raise property taxes by 3 percent.

Example 3: Feature intro

AI slop:

> In the rich tapestry of American journalism, few stories are as compelling as the one about to unfold. This isn't just a profile—it's a journey into the heart of what makes local news truly matter.

Human writing:

> Maria Rodriguez has published a newspaper for 47 years. She's never missed an issue.

Example 4: Analysis piece

AI slop:

> Moving forward, stakeholders must leverage innovative approaches to navigate the challenging landscape of digital transformation in the journalism ecosystem.

Human writing:

> Local papers that want to survive need to find digital revenue. Most haven't.

The verbal tic test

Read your text aloud. Does it sound like:

  • A TED talk introduction? Rewrite.
  • A LinkedIn post? Rewrite.
  • A press release? Rewrite.
  • Corporate communications? Rewrite.
  • How you'd explain it to a colleague? Keep it.

Quick self-check before publishing

Search your text for:

  • "delve" → delete or replace
  • "landscape" → delete or replace
  • "crucial" → is it actually crucial?
  • "robust" → what does this mean here?
  • "leverage" → just say "use"
  • "comprehensive" → is this word doing any work?
  • Starting "So," → delete

Found any? Your writing needs another pass.

Red flags in technical/analysis writing

  • Lists of near-synonyms: "comprehensive, sophisticated, and robust" (pick one or none)
  • Excessive hedging: "may potentially be able to possibly..."
  • Noun stacking: "production-ready deployment system infrastructure"
  • Passive voice hiding agency: "It was determined that..." (by whom?)
  • Circular definitions: "The system enables users to use the functionality"

The ultimate test

Before accepting any AI-assisted text, ask:

  • Can I delete this word/phrase without losing meaning? → Delete it
  • Is this the simplest way to say this? → Simplify
  • Would I say this out loud to a colleague? → If not, rewrite
  • Does this add information or just sound impressive? → If the latter, cut it

If readers think "AI wrote this," you've already lost their trust.


*Good writing is invisible. If readers notice the writing, it's getting in the way of the content.*

*See also: hooks/ai-slop-detector.md for the automated companion to this skill.*

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Writing Plans
by ZhanlinCui
×4

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Crafting Effective Readmes
by softaworks
×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

15k tokens
Humanizer
by softaworks
×3

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

6k tokens
Opentrons Integration
by christophacham
×3

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

9k tokens scripts

How to use it

Copy the folder

Take jamditis/ai-writing-detox from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.