skills / writing

stop-slop

what it does

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Write the first two paragraphs of a blog post arguing that teams under ten people should stop holding daily standups.”

with the skill
You have six people on your team. At 9:30 each morning, all six stop work, open a call, and take turns reciting what they did yesterday. The meeting runs fifteen minutes, which costs the team an hour and a half of work, and the only useful news is that Priya is blocked on an API key. She could have posted that in Slack at 9:05, and someone would have answered by 9:10. Small teams share context without a meeting. You sit near each other or share a channel, and you see pull requests land as they come in. A ritual built to coordinate forty people across five squads adds nothing when you can read the whole team's work in one tab. It also splits the stretch of focus a developer builds early in the day. Drop the daily call, hold one planning session each week, and have people post blockers in a shared thread the moment they hit one.
without
# Stop Holding Daily Standups Somewhere along the way, the daily standup stopped being a tool and became a ritual. Nobody remembers who decided it had to happen at 9:30 every morning, but everyone dutifully shows up, shuffles through their updates, and nods along to things they already knew. If your team has fewer than ten people, I'd argue that meeting is costing you far more than it returns. The standup was designed to solve a coordination problem: too many people working on too many interrelated things to keep track of informally. A team of six doesn't have that problem. You sit near each other, or share a Slack channel, or both. You already know that Priya is wrestling with the payment API and that Marcus is waiting on design assets. Asking everyone to recite this aloud at a fixed time is like holding a town hall to announce the weather. The real cost isn't the fifteen minutes on the calendar. It's the interruption of the two hours around them. A meeting at 9:30 makes the 9:00 hour too short to start anything deep, and the 10:00 hour a slow recovery from context-switching. Multiply that across a small team and you're burning a meaningful slice of your most productive time on status updates that a short written note could convey in seconds. Worse, the format quietly rewards performance over honesty: people say "no blockers" because raising a real problem in front of everyone feels awkward, then quietly ping a colleague afterward, which is the conversation that should have happened anyway. Small teams have a gift that large organizations would envy, which is the ability to talk to each other directly, when it matters, without ceremony. Daily standups squander it.

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 1 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 1 Nov 2026

The tasks

written by Carte Blanche
essay-opening

“Write the first two paragraphs of a blog post arguing that teams under ten people should stop holding daily standups.”

explain-retries

“Explain to a new engineer why our service retries failed webhook deliveries with exponential backoff. Two short paragraphs.”

launch-post

“Write a LinkedIn post announcing that we shipped offline mode for our note-taking app. About 150 words.”

price-change-email

“Write a short email telling our customers we're raising the Pro plan price, and why.”

tighten-blog-paragraph

“Tighten this paragraph for our company blog.”

Install

Download the .zip and unzip it. Put its files, in a folder named stop-slop, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.