Stop Slop

Keep the point. Cut the padding.

Find empty openings, repetitive emphasis and formulaic sentences, then edit without losing the draft’s facts or voice. Useful for articles, product copy and work emails with real material behind them.

By Hardik Pandya

Stop Slop project image

Loading routes described by the author

  • Claude Code
  • Claude Projects
  • Custom instructions / API
GitHub stars
18,451
Checked

Try one passage from a real draft.

Pick a passage that already has facts but spends too long setting them up. Include its audience and purpose, then compare what was removed before editing the whole piece. Supply missing facts first so the revision does not invent specificity.

Pick a task and get started

All three tasks use the same rules. Choose revision, review or drafting according to the material you have.

Where are you in the writing process?

The information is complete; remove padding, repetition and stock structures.

  1. Load the complete writing rules

    Get the complete stop-slop folder from the repository. Add it through your Claude Code skill setup, or add SKILL.md plus phrases.md, structures.md and examples.md from references to Claude Projects knowledge. The author also describes using the core rules in custom instructions or an API system prompt. Choose the route for your client and include the supporting rules rather than the README summary alone.

    Read the author’s setup guide

    Check that all four files are available

    SKILL.md holds the core instructions; the three reference files cover phrases, sentence structures and worked examples. Ask your assistant to confirm it can read them before sending the draft. With custom instructions or an API, you must supply the references rather than assume the model can access local files.

    Read the author’s setup routes
  2. Give your AI this first task

    These are editorial task examples written by Atlasnote. After setup, attach your draft or factual notes and state the audience, purpose and content that must stay.

    Edit this product introduction with stop-slop for readers seeing the product for the first time. Read the core instructions and all three reference files. I will provide the draft and facts that must stay. Preserve numbers, scope, conditions, quotations and the author’s position. Remove empty openings, repeated emphasis and mechanical contrasts. Return the revision and explain the most important edits against the original sentences. Flag missing facts instead of inventing details to make the prose sound concrete.

  3. Check what you receive

    • A coherent revision that makes the product’s purpose and use clear.
    • Editing reasons tied to the original sentences, with numbers, qualifications and quotations preserved.
    • Missing facts listed separately, with no new features or outcomes invented.
    Read the author’s notes for this task
More about this skill

Stop Slop turns a preference for direct, concrete prose into instructions an assistant can apply while drafting or editing. It makes a vague complaint such as “this feels empty” easier to examine: the opening may contain no information, the argument may repeat the same turn, or the sentence may hide who did the work.

The core instructions are supported by phrases.md for wording, structures.md for sentence patterns and rhythm, and examples.md for the author’s edits. Loading them together gives the assistant a more specific editing brief than a request to make prose sound human.

The rules are strict and exclude some words and constructions outright. Decide what your document must preserve before using them: technical or legal qualifications, exact quotations and intentional voice need explicit treatment. Compare the reasons for an edit with the original sentence.

The review rubric covers directness, rhythm, trust, authenticity and density. The author recommends revising below 35 out of 50. Use those scores to locate possible improvements, then check whether the result remains accurate and fits its readers.

Sources and verification

Sources checked

Reviewed the core instructions, all three reference files and the author’s setup notes. Atlasnote wrote the displayed comparison; no installed model run was tested.