Anti-Slop Kit: editorial taste with a linter

Summary

slopcheck.py found 19 tells in a 225-word launch post. Most are rule 5 (abstractions where a fact should be). The opening never says what the product does.

What the checker printed

examples/before.md
     3  SLOP   rule 1  cliffhanger — say what happened
     3  SLOP   rule 5  banned abstraction: 'fast-paced world'
     3  SLOP   rule 12 throat-clearing — start at the first concrete fact
     4  SLOP   rule 1  the reader has no idea what changed
     7  SLOP   rule 2  deliver the found thing, not the finding of it
     7  SLOP   rule 2  nobody ordered the story of you working
     8  SLOP   rule 3  vending-machine profundity
     9  SLOP   rule 5  banned abstraction: 'tapestry'
    12  SLOP   rule 5  banned abstraction: 'cutting-edge'
    12  SLOP   rule 5  banned abstraction: 'robust'
    12  SLOP   rule 5  banned abstraction: 'seamless'
    13  SLOP   rule 5  banned abstraction: 'testament to'
    13  SLOP   rule 5  banned abstraction: 'unlock'
    14  SLOP   rule 5  banned abstraction: 'delve'
    18  SLOP   rule 5  banned abstraction: 'game-changer'
    18  SLOP   rule 9  stacked hedges (might, could, possibly)
    23  SLOP   rule 7  3 three-item lists in 225 words
    24  SLOP   rule 5  banned abstraction: 'empowering'
    24  SLOP   rule 5  banned abstraction: 'ever-evolving'

The rewrite (examples/after.md, first paragraphs)

Support tickets at Verso repeated themselves 41% of the time. The same eleven questions, asked by new people, answered from scratch by whoever was on rotation.

Meadowlark indexes what a team has already written and answers from it. It reads Notion, Google Docs, Slack, and a folder of Markdown files, then returns the passage and the link, not a summary.

Next steps

1. Fix by line number, starting with rule 1 and rule 12: the opening.
2. Replace each abstraction with a number, a name or a date you can stand behind.
3. Run the checker again until it prints nothing.