DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to remove filler and fake stats from marketing copy with Anti Slop

Run one prompt through the copywriting rules to get clear, honest text.

Who it is forA marketer or founder who has an AI draft of a homepage, email, or product description with vague claims and invented numbers.

The problemAI-written copy often includes filler phrases, stock headlines, and statistics no one can source.

The outcomeCopy that avoids fake stats and generic AI phrasing, checked against the copywriting rules, with a Delivery Gate report.

What you need first

  • An AI coding agent that antislop supports, such as Claude Code, Codex, Cursor, or Gemini CLI
  • A terminal to run the installer command (npx antislop-ai)
  • A project folder for the agent to work in
  • Optional: a DESIGN.md file that gives the visual direction, since antislop filters and does not supply direction

Steps

  1. Download the single file with curl -o antislop.md https://raw.githubusercontent.com/miqdadbadjuber/anti-slop/main/antislop.md, or download antislop.md from the repository page.
  2. Open a new chat in your AI tool and paste the contents of antislop.md at the start.
  3. Paste your draft copy below the rules and ask for a rewrite.
  4. Check that every number in the new copy also appears in your original draft or source notes.
  5. Read the Delivery Gate report before you publish the copy.

Prompt for your agent

Apply the antislop filter from the anti-slop repo (https://github.com/miqdadbadjuber/anti-slop) to the draft in <draft-file>. Return a rewritten version and the Delivery Gate PASS/FAIL report. Verify that no statistic in the output is absent from the draft.

Caveat. The single file is a complete filter for chat use, but the full skill set with the copywriting skill is installed through the installer.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page