Unslop
Remove the patterns that read as machine-made, then put a voice back in. Both halves are the job.
What this skill is - and isn't
| Skill | Question it answers | Output |
|---|---|---|
vd:unslop |
"Does this read like a human wrote it?" | Rewritten prose, meaning preserved |
vd:copywriting |
"Does this convert?" | Formula-driven marketing copy |
vd:docs (incl. site) |
"Is this documented correctly?" | Structured docs / docs site |
vd:code-review --refactor |
"Is this code slop?" | Diff review report |
vd:simplify |
"Is this code hard to read?" | Behavior-preserving refactor |
Unslop edits prose. It changes wording and rhythm, never facts, claims, links, or code blocks.
Hard rules
- Meaning is frozen. Rewrite the sentence, never the claim. If a fact looks wrong, flag it - don't fix it silently. Why: an edit pass that changes meaning is a new draft nobody reviewed.
- Match the intended register. A PR body, a launch tweet, and an incident report don't share a voice. Why: "human" is not one tone.
- Cut before you decorate. Most fixes are deletions. Adding personality to filler still leaves filler.
- Self-audit before returning. Ask "what still makes this obviously AI-generated?" and fix it. One pass is never enough.
- House dash rule. No em dashes, no en dashes, no curly quotes. Plain
-with spaces is the separator. Why: this catalog and its owner's global style ban them; the em dash is also the single strongest tell.
Process
- Scan against the pattern catalog below. Mark every hit.
- Rewrite. Preserve meaning, match the register.
- Add soul (next section).
- Self-audit: "What makes this obviously AI generated?" Fix the remainder.
Adding soul
Removing patterns is half the job. Sterile, voiceless text is just as obvious.
- Have opinions. React to facts instead of neutrally listing pros and cons.
- Vary rhythm. Short sentences. Then longer ones that take their time.
- Acknowledge complexity. "Impressive but also kind of unsettling" beats "impressive."
- Use "I" when it fits. First person isn't unprofessional.
- Let some mess in. Perfect structure looks machine-made.
- Be specific. Not "this is concerning" but "there's something unsettling about agents churning away at 3am."
Pattern catalog
Content
- Puffery. "pivotal moment", "testament to", "evolving landscape", "setting the stage for". Cut it, state what happened.
- Name-dropping. Listing outlets or tools without context. Pick one, say what it said.
- Superficial -ing phrases. "highlighting...", "ensuring...", "showcasing...", "fostering...". Delete or expand with a real source.
- Promotional language. "nestled", "vibrant", "breathtaking", "groundbreaking", "renowned", "must-visit". Use neutral description.
- Vague attributions. "Experts believe", "Industry reports suggest". Name the source or delete.
- Formulaic challenges. "Despite challenges... continues to thrive." Replace with specific facts.
Language
- AI vocabulary. Additionally, crucial, delve, enduring, enhance, fostering, garner, interplay, intricate, landscape (abstract), pivotal, showcase, tapestry, testament, underscore, vibrant. Use plain words.
- Fancy "is". "serves as", "stands as", "boasts", "features". Say "is" or "has".
- "Not just X, but Y." State the point directly.
- Rule of three. Forcing ideas into triads. Use the natural number.
- Synonym cycling. Protagonist, main character, central figure in one paragraph. Pick one, repeat it.
- False ranges. "from X to Y" where X and Y aren't on a scale. List the items.
Style
- Em/en dashes and curly quotes. Banned (Hard rule 5). End the sentence, use a comma, or use plain
-. - Colon as mid-sentence connector. Fine before a list or example, not as a crutch. Rewrite so the point stands alone.
- Boldface overuse. Don't bold every proper noun or acronym.
- Inline-header restating lists. "Performance: Performance improved..." - convert to prose. A bold lead-in followed by genuinely new detail is fine.
- Title Case Headings. Use sentence case.
- Decorative emojis in headings and bullets. Remove.
Communication artifacts
- Chatbot phrases. "I hope this helps!", "Let me know if...", "Certainly!", "Found the smoking gun!" Remove.
- Cutoff disclaimers. "While specific details are limited..." Find the source or remove.
- Sycophancy. "Great question! You're absolutely right!" Respond directly.
Filler
- Filler phrases. "In order to" → "To". "Due to the fact that" → "Because". "It is important to note that" → delete.
- Hedging stacks. "could potentially possibly be argued" → "may".
- Generic conclusions. "The future looks bright." State the plan or the fact.
Jargon
- Abstract metaphor nouns. Substrate, wedge, vector, locus, nexus, primitive (noun), harness (metaphor), bedrock, modality, paradigm, north star, flywheel, endgame. Pick the concrete word: "substrate" → "base", "wedge in" → "add", "endgame" → "the last phase".
Plain speech
- Say what it does, not how it feels. "SQL you can read" names a feeling. Name the mechanism or number: "
.toSQL()returns the exact string sent to the database". If the sentence could appear unchanged in another project's docs, it says nothing - cut it. - One idea per sentence. If the reader backtracks to parse it, split it.
- Active voice. "queries are validated" → "the compiler validates queries". Passive only when the actor is unknown or truly irrelevant.
- Cut adverbs or use a stronger verb. "significantly improves" → the measured delta.
- Prefer the plain word. "utilize" → "use", "leverage" → "use", "facilitate" → "help", "numerous" → "many".
Workflow position
Typically follows: any prose-producing skill - vd:devlog, vd:ship (PR bodies), vd:docs (incl. site), vd:journal, vd:show-off, vd:copywriting, vd:code-review summaries
Compares to: vd:copywriting owns conversion structure; unslop owns de-AI voice. Run copywriting first, unslop last.
Rationalizations to catch
| Thought | Reality |
|---|---|
| "It's just a PR body, skip the pass" | PR bodies are the most-read prose you ship. Two minutes. |
| "The draft is already concise" | Concise slop is still slop. Check the catalog, especially 7, 13, 19. |
| "I'll add personality by adding words" | Rule 3. Most fixes are deletions. |
| "The em dash reads fine here" | Hard rule 5. No exceptions - it is the number-one tell. |
| "Rewriting might change the meaning slightly" | Then you are drafting, not unslopping. Hard rule 1 - flag, don't drift. |