anti-slop-writing
Skill0 starsChanged 7 days agoMITView on GitHub
Voice rules, banned list, before/after rewrites and the "specific > generic" checklist for PocketForge manuscripts. Use before writing, revising or critiquing any chapter, blurb or listing copy.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- basaltbytes/skillstheir own version, first seen Nov 1, 2026
- Kaos599/professional-skillstheir own version, first seen Oct 13, 2026
- adewale/anti-slop-writingtheir own version, first seen Oct 13, 2026
- adenaufal/anti-slop-writingtheir own version, first seen Jul 6, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- adenaufal/anti-slop-writing★ 139same name
- adewale/anti-slop-writing★ 23same name
- Kaos599/professional-skills★ 4same name
- basaltbytes/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/pocketforge.mdcCursor rule
- ebook-structureSkill
- mascot-rigSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 51
Run node scripts/gates/run-all.mjs <file>, then reread the first and last paragraph against the checklist.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Anti-slop writing
The reader paid for this book because a free blog post was not specific enough. Every sentence must earn its place with a fact, a step, or a decision the reader can make.
Voice
- Second person, present tense, active voice. "Move the rent money first," not "Rent money should be moved."
- One idea per sentence. Average 14–18 words. Vary length; never three long sentences in a row.
- Plain words: use, help, start, cost, need. Not utilize, facilitate, commence, leverage.
- Concrete nouns: "the electricity bill due on the 15th," not "your financial obligations."
- Confidence comes from sources, not adjectives. Cut "incredibly", "truly", "powerful", "robust".
- Examples are labelled hypothetical ("Say you earn $3,000 a month…") unless they come from research with a footnote.
Banned (gate-enforced, zero hits)
delve, unlock, game-changer, landscape, seamless, "in today's fast-paced world", "it's important to note", "in conclusion", "harness the power".
Also avoid (critic flags these)
- Openers: "Have you ever wondered…", "Imagine a world…", "Let's dive in", "Picture this".
- Fake balance: "Whether you're X or Y…". Empty triads: "simple, effective, and powerful".
- Hedge stacks: "may potentially help to some extent".
- Summary paragraphs that restate the chapter. End on the next action instead.
- "Journey", "navigate", "empower", "elevate", "robust", "crucial", "tapestry", "realm", "embark", "cutting-edge", "revolutionize".
- Rhetorical questions as section transitions.
- Em-dash chains. One em dash per paragraph at most.
Specific > generic checklist
For every paragraph ask:
- Does it contain a number, a named thing, a date, a step, or a quote? If none, rewrite or cut.
- Could this sentence appear unchanged in a book on a different topic? If yes, it is generic. Replace it.
- Is the claim sourced in this chapter's research files? If not, cut it.
- Does the reader know what to do after reading it? If not, add the action.
- Is the example tied to the pocket's WHO (e.g. single-income household), not "people"?
Before / after
| Before (slop) | After (specific) |
| In today's fast-paced world, managing money can feel overwhelming. | One paycheck, four bills due before the 10th: that's the month this chapter fixes. |
| It's important to note that emergencies happen. | Car repairs are the expense readers in our gap research mention most.[^3] Plan for one per year. |
| Budgeting is a powerful tool that can unlock financial freedom. | A budget tells each dollar where to go before the paycheck lands. |
| Many experts agree that saving is crucial. | The Federal Reserve found 37% of adults could not cover a $400 expense with cash.[^4] |
| In conclusion, these strategies can help you on your journey. | Fill in the worksheet on page 42 before your next payday. |
(The footnoted figures above are format examples only. Writers use figures from their own research files.)
Self-check before saving
Run node scripts/gates/run-all.mjs <file>, then reread the first and last paragraph against the checklist. Openers and closers are where slop hides.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

