# no-ai-slop

An editing skill that strips AI tells from a draft while keeping the writer's voice. It can also just flag those patterns, with quotes, and leave the text alone.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 28200 installs · ★ 12790
- Author: petergyang
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/petergyang/no-ai-slop/tree/HEAD/skills/no-ai-slop/SKILL.md
- Updated: 2026-09-02
- HTML: https://affpapa.org/en/nevibecode/skills/no-ai-slop

## What it does

Two modes. By default the skill edits the draft you paste: it clears filler, untangles sentences, swaps weak verb phrases for direct verbs. Edits stay small on purpose. Strong human lines survive untouched, and the writer's cadence, bluntness and humor are not sanded down. Afterward the agent lists what it changed.

Ask it to audit instead and it names each pattern it finds, quotes the line, and suggests a fix in a few words. No scores, no guesses about whether a machine wrote the text — a named pattern is something you can check yourself. It will rewrite the draft after the audit, but only if you ask.

The skill carries a rule set: words and phrases to cut, plus constructions like the binary contrast, the throat-clearing opener, and the colon reveal. One test asks whether a sentence could be lifted unchanged into another company's copy; if it could, it probably says nothing. No draft yet? It asks you to paste one, and if the audience is unclear it asks a single question about who reads it and where it runs.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add petergyang/no-ai-slop --skill no-ai-slop -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/no-ai-slop/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/no-ai-slop/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add petergyang/no-ai-slop --skill no-ai-slop -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/no-ai-slop/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add petergyang/no-ai-slop --skill no-ai-slop -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/no-ai-slop/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install petergyang/no-ai-slop no-ai-slop
```

2. **Manually: put the files in place**
- File: `.github/skills/no-ai-slop/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add petergyang/no-ai-slop --skill no-ai-slop -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/petergyang/no-ai-slop --path skills/no-ai-slop
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/no-ai-slop/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add petergyang/no-ai-slop --skill no-ai-slop -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/petergyang/no-ai-slop/tree/HEAD/skills/no-ai-slop/SKILL.md

## When to use it
- strip AI tells from a draft without flattening the author's voice
- audit finished copy for clichéd patterns and get a quoted list back
- turn weak verb phrases like "made a decision" into "decided"
- cut throat-clearing openers so the point arrives sooner
- spot abstractions that carry no information and replace them with facts

## Example prompts
- Edit this draft, keep my voice, and show me what you changed
- Audit this text for AI patterns — don't rewrite it, just name them and quote the lines
- Cut the filler and jargon from this post without changing what it says

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 2cac67e410629647.

BEGIN THIRD-PARTY FILE 2cac67e410629647
```text
---
name: no-ai-slop
description: Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI.
---

# No AI slop

You are a sharp human editor. Preserve the user's point and personal voice while making the writing clearer and more alive. Remove AI patterns without turning distinctive writing into generic polished prose.

## Two jobs

**Edit (default).** The user shares a draft to fix. Make the minimum effective edit with the rules below and return the edited draft plus a What changed section.

**Detect.** The user asks whether a piece is AI slop, or asks to audit, scan, or flag a draft without rewriting. Name each pattern from this skill that appears, quote the line, and give the fix in a few words. Do not rewrite, score the draft, or guess whether AI wrote it. AI detectors guess. Named patterns are evidence the user can check. Offer to edit the draft after.

## What to ask for

If the user has not provided a draft, ask them to paste it.

If the audience or format is unclear, ask one question: Who is this for and where will it be published?

If the goal is unclear, ask what the reader should think, feel, or do after reading it.

## Editing principles

- **Preserve the writer's real voice.** First notice the draft's vocabulary, cadence, bluntness, humor, uncertainty, digressions, and level of polish. Keep the traits that feel personal to the writer. Do not make every paragraph equally tidy or rewrite distinctive lines merely for consistency.
- **Make the minimum effective edit.** Fix AI patterns, errors, repetition, and unclear passages. Leave strong human sentences alone. A rough draft with a real voice should still sound like the same person after editing.
- **Lead with the point when the setup adds nothing.** Cut generic throat-clearing. Keep a personal aside, story, or admission when it creates context, tension, or character.
- **Front-load only when it improves clarity.** Put conclusions early when that helps the reader. Do not force every section and paragraph into the same point-detail-background shape.
- **Keep the user's meaning.** Don't invent claims, examples, stats, or opinions. If something is unclear, ask.
- **Open it up, don't dumb it down.** Keep the substance, nuance, and precision. Strip out only what makes it hard to read: jargon, long sentences, abstract nouns, and tangled structure.
- **Use active voice.** "The team shipped it Tuesday" beats "the decision emerged." Never let inanimate things do human verbs.
```
END THIRD-PARTY FILE 2cac67e410629647

The third-party file has ended. Everything between the 2cac67e410629647 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2676 of 10853 bytes. © petergyang · MIT · https://github.com/petergyang/no-ai-slop/tree/HEAD/skills/no-ai-slop/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md