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.
npx skills add https://github.com/jamditis/claude-skills-journalism --skill 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.
| 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 |
| 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 |
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 |
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
Avoid: "This fundamentally transforms how newsrooms operate"
Avoid: "This represents a fundamental shift in journalism"
Do instead: Describe the actual change without hyperbole
Avoid: "A bombshell revelation"
Avoid: "A major milestone"
Avoid: "A groundbreaking investigation"
Do instead: Let the facts speak. Readers judge significance.
Avoid: "With that in mind..."
Avoid: "Building on this foundation..."
Avoid: "Taking this a step further..."
Do instead: Just make the next point
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.
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.
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.
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.
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.
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.
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.
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.
Read your text aloud. Does it sound like:
Search your text for:
Found any? Your writing needs another pass.
Before accepting any AI-assisted text, ask:
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.*
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.
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.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| 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.
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.
Take jamditis/ai-writing-detox from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.