Menu

Individual skill

anti-ai-slop-writing

0upvotes

Use this skill when any GTM copy needs to stop reading like AI before it ships - a LinkedIn post, a cold email, a newsletter, a landing page, a case study, an exec's thought-leadership draft. Produces the same copy with the machine tells stripped out, back to a clean baseline. Reach for it when someone says "this sounds like AI", "make it less robotic", "remove the AI tells", "de-slop this", or when a draft is technically fine but reads like a competent bot wrote it.

skills/gali-firon/anti-ai-slop-writing/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Applies to any prose before it ships. Produces copy with the recognisable AI patterns removed, in two disciplined passes.

The core idea: AI writing fails in two different ways, and each needs its own pass. Some patterns are rhetorical moves with no human upside - they are wrong every time they appear. Others are ordinary words and structures that read fine once but scream machine when they cluster. Scan for each separately.

This skill is the subtractive half of a two-pass writing standard. It takes tells out. Its companion, the human-mannerisms pass, does the opposite job - it puts voice in, so clean copy does not read flat. They are deliberately kept as two skills, not one, because the two jobs do not always both apply. Every piece that ships should have its AI tells removed; not every piece should be made to sound casual. A formal announcement, a compliance note, or a technical one-pager needs to be clean, not chatty - run this pass and stop. A LinkedIn post, a founder's thought leadership, or a personal email needs voice on top - run this pass first, then the mannerisms pass. Bundling them would force a casual register onto writing that should stay plain. Keeping them separate lets you apply the floor everywhere and the texture only where it fits.

## The two passes

Run both, in order, before returning any prose.

**Pass one - zero-instance patterns.** Scan for rhetorical moves that are a tell every time. Any hit gets rewritten, not softened. The full catalogue is in `references/zero-instance-patterns.md`; the ones that slip through most often:

1. **Negative parallelism** - asserting what something IS by first saying what it ISN'T about the same subject: "It's not X, it's Y", "Not just X, Y", "We don't just X, we Y". The test: remove the negated half. If the point still stands, the negation was scaffolding - cut it and state the claim directly.
2. **False-suspense transitions** - "Here's the thing", "Here's what nobody tells you", "Here's what changed". The whole class, not set phrases. Does it name the revelation in the same beat, or just tease one? If it teases, cut it.
Back to top