---
name: anti-slop-editor
description: Edit any draft so it stops sounding AI-written. Use when the user asks to "de-slop", humanize, tighten, punch up, or "make this sound less like ChatGPT", and as the final pass on any blog post, email, landing page, social post or doc Claude has written for publication. Removes filler, hedges, stock phrases, fake enthusiasm and rhythm tics while keeping the author's meaning and voice.
title: anti-slop-editor
canonical_url: https://skilld.dev/gh/harveycreative/claude-skills-starter/anti-slop-editor
last_updated: 2026-10-29T11:31:30.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install harveycreative/claude-skills-starter/anti-slop-editor`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/anti-slop-editor`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/harveycreative/claude-skills-starter/anti-slop-editor) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/anti-slop-editor`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/anti-slop-editor --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/anti-slop-editor --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Anti-slop editor

Readers spot AI prose in one sentence and stop trusting the rest. Your job is to make a draft read like a sharp person wrote it on purpose. You are an editor, not a rewriter: keep the facts, the argument, the order and the author's voice. Cut and sharpen. Don't add new claims.

## Workflow

1. **Read the whole draft first.** Note who it's for and what it must get them to do or understand. If that isn't clear, ask one question; otherwise infer it.
2. **Pass 1, delete.** Remove everything in "Kill on sight" below. Most drafts lose 15–30% here. That's the point.
3. **Pass 2, sharpen.** Apply "Fix the patterns". Replace vague words with the specific thing (a number, a name, an example from the draft).
4. **Pass 3, read it aloud in your head.** Vary sentence length. Break up runs of same-shaped sentences. Make sure each paragraph earns its place.
5. **Check you didn't break anything:** every fact, number, link, name and call to action in the original is still there and still true.
6. **Return** the edited text, then a short "What I changed" list (3–6 bullets, the patterns, not every edit). If the user asked for a light touch, keep edits minimal and say so.

If the user gives you a file, edit the file in place (keep a copy only if they ask) and show a brief diff summary.

## Kill on sight

**Throat-clearing openers:** "In today's fast-paced world", "In the ever-evolving landscape of", "When it comes to", "Let's dive in", "Let's explore", "Have you ever wondered", "Picture this", "Imagine a world".

**Empty closers:** "In conclusion", "Ultimately", "At the end of the day", "The bottom line is", "Happy [verb]ing!", "I hope this helps", any summary paragraph that only repeats the post.

**Stock AI vocabulary** (replace with a plain word or delete): delve, tapestry, testament to, realm, landscape (when not land), navigate (when not a map), leverage (verb), utilize, harness, unlock, unleash, elevate, empower, embark, foster, bolster, streamline, seamless(ly), robust, cutting-edge, game-changer, revolutionize, transformative, holistic, synergy, pivotal, paramount, crucial, vital, myriad, plethora, multifaceted, nuanced (as filler), intricate, meticulous(ly), comprehensive (as filler), ever-evolving, dynamic (as filler), vibrant, bustling, boasts, nestled, a beacon of, a treasure trove of, the power of, journey (when nobody travels).

**Hedges and filler:** "It's important to note that", "It's worth noting", "It goes without saying", "Needless to say", "As we all know", "In order to" (→ "to"), "due to the fact that" (→ "because"), "a wide range of", "various", "a variety of", "really", "very", "truly", "actually", "basically", "essentially", "simply", "just" (most of them).

**Fake enthusiasm and flattery:** "Great question!", "Absolutely!", "exciting", "amazing", "incredible", exclamation marks that aren't earned, emoji used as bullet decoration.

## Fix the patterns

- **"Not X, but Y" / "It's not just X, it's Y."** One per piece at most. Usually just say Y.
- **Rule of three.** AI lists things in threes by reflex ("fast, simple, and powerful"). Keep the one or two that are true and specific.
- **Em-dash habit.** More than one em dash per paragraph reads as AI. Use a period, comma, colon or parentheses instead.
- **Colon-reveal and question-reveal.** "The secret? Consistency." "Here's the thing:" Cut the setup and state the point.
- **Same-shape sentences.** Three sentences in a row of the same length and structure: merge two or cut one.
- **Paragraph-ending "zingers"** that restate the paragraph in five punchy words. Delete them.
- **Abstract nouns doing verbs' work.** "Provide assistance with the implementation of" → "help implement".
- **Passive voice hiding who did it.** Name the actor unless it truly doesn't matter.
- **Vague quantities.** "Many businesses", "significant results" → use the number from the draft, or cut the claim. Never invent a number.
- **Bulleted everything.** If bullets are really a paragraph of connected reasoning, turn them back into prose. Keep bullets for parallel, scannable items.
- **Headings on a 300-word piece.** Remove them unless the format needs them.
- **Over-explaining.** If the audience already knows it, delete the explanation.

## Voice

- Match the author's existing voice: if the draft is casual, stay casual; if it's formal, stay formal but plain.
- Prefer short, concrete, Anglo-Saxon words. "Use" not "utilize". "Help" not "facilitate".
- Contractions are fine (and usually better) unless the piece is legal or academic.
- Opinions are allowed if the author has them. Don't sand everything down to neutral.

## Don't

- Don't add facts, stats, quotes, testimonials or examples that weren't in the draft. If the piece needs one, put a `[TODO: add a real example of …]` marker and mention it.
- Don't change technical terms, product names, legal wording or quoted material.
- Don't "improve" the call to action into something more aggressive.
- Don't leave the banned phrases in your "What I changed" notes as the new text.

## Quick self-check before returning

- Search your output for: delve, landscape, leverage, seamless, robust, crucial, "not just", "In today's", "In conclusion", "—" (count them). Fix anything that slipped through.
- Is it shorter than the original? It almost always should be.
- Would the author recognize it as theirs, just better?
