stop-slop

Remove AI writing patterns from prose to enhance clarity and authenticity.

hvpandya/stop-slopUpdated Jun 19, 2026

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

20

total installs

20

this week

0

upvotes

Install Skill

Run in your terminal

$npx skills add https://github.com/hvpandya/stop-slop --skill stop-slop

20

installs

20

this week

stars

Installation Guide

How to use stop-slop on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add stop-slop
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/hvpandya/stop-slop --skill stop-slop

Fetches stop-slop from hvpandya/stop-slop and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/stop-slop

Restart Cursor to activate stop-slop. Access via /stop-slop in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

name
stop-slop
description
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
metadata
trigger: Writing prose, editing drafts, reviewing content for AI patterns author: Hardik Pandya (https://hvpandya.com)

Stop Slop

Eliminate predictable AI writing patterns from prose.

Core Rules

  1. Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See references/phrases.md.

  2. Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See references/structures.md.

  3. Use active voice. Every sentence needs a human subject doing something. No passive constructions. No inanimate objects performing human actions ("the complaint becomes a fix").

  4. Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.

  5. Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.

  6. Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.

  7. Trust readers. State facts directly. Skip softening, justification, hand-holding.

  8. Cut quotables. If it sounds like a pull-quote, rewrite it.

Quick Checks

Before delivering prose:

  • Any adverbs? Kill them.
  • Any passive voice? Find the actor, make them the subject.
  • Inanimate thing doing a human verb ("the decision emerges")? Name the person.
  • Sentence starts with a Wh- word? Restructure it.
  • Any "here's what/this/that" throat-clearing? Cut to the point.
  • Any "not X, it's Y" contrasts? State Y directly.
  • Three consecutive sentences match length? Break one.
  • Paragraph ends with punchy one-liner? Vary it.
  • Em-dash anywhere? Remove it.
  • Vague declarative ("The implications are significant")? Name the specific implication.
  • Narrator-from-a-distance ("Nobody designed this")? Put the reader in the scene.
  • Meta-joiners ("The rest of this essay...")? Delete. Let the essay move.

Scoring

Rate 1-10 on each dimension:

DimensionQuestion
DirectnessStatements or announcements?
RhythmVaried or metronomic?
TrustRespects reader intelligence?
AuthenticitySounds human?
DensityAnything cuttable?

Below 35/50: revise.

Examples

See references/examples.md for before/after transformations.

License

MIT

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Steps

  1. 1Install skill using provided installation command
  2. 2Test with simple use case relevant to your work
  3. 3Evaluate output quality and relevance
  4. 4Iterate on prompts to improve results
  5. 5Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use when

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid when

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Related Skills

Reviews

4.540 reviews
  • G
    Ganesh MohaneDec 28, 2024

    We added stop-slop from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • L
    Luis BansalDec 28, 2024

    stop-slop fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • A
    Arjun WhiteDec 12, 2024

    stop-slop has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • N
    Naina HuangDec 4, 2024

    Useful defaults in stop-slop — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • A
    Aarav MenonDec 4, 2024

    Keeps context tight: stop-slop is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • N
    Nikhil GhoshNov 23, 2024

    We added stop-slop from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • I
    Isabella ChenNov 23, 2024

    stop-slop is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • S
    Sakshi PatilNov 19, 2024

    Useful defaults in stop-slop — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • C
    Chen AndersonOct 14, 2024

    stop-slop reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • A
    Arya SethiOct 14, 2024

    Solid pick for teams standardizing on skills: stop-slop is focused, and the summary matches what you get after install.

showing 1-10 of 40

1 / 4

Discussion

Comments — not star reviews
  • No comments yet — start the thread.