Agent skill / hvpandya
Remove AI writing patterns from prose to enhance clarity and authenticity.
Core file
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstop-slopExecute the skills CLI command in your project's root directory to begin installation:
Package manager
npx skills add https://github.com/hvpandya/stop-slop --skill stop-slopFetches stop-slop from hvpandya/stop-slop and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate stop-slop. Access via /stop-slopin your agent's command palette.
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.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Copy the command for your terminal
Package manager
npx skills add https://github.com/hvpandya/stop-slop --skill stop-slopWorks with
| 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) |
Eliminate predictable AI writing patterns from prose.
Cut filler phrases. Remove throat-clearing openers, emphasis crutches, and all adverbs. See references/phrases.md.
Break formulaic structures. Avoid binary contrasts, negative listings, dramatic fragmentation, rhetorical setups, false agency. See references/structures.md.
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").
Be specific. No vague declaratives ("The reasons are structural"). Name the specific thing. No lazy extremes ("every," "always," "never") doing vague work.
Put the reader in the room. No narrator-from-a-distance voice. "You" beats "People." Specifics beat abstractions.
Vary rhythm. Mix sentence lengths. Two items beat three. End paragraphs differently. No em dashes.
Trust readers. State facts directly. Skip softening, justification, hand-holding.
Cut quotables. If it sounds like a pull-quote, rewrite it.
Before delivering prose:
Rate 1-10 on each dimension:
| Dimension | Question |
|---|---|
| Directness | Statements or announcements? |
| Rhythm | Varied or metronomic? |
| Trust | Respects reader intelligence? |
| Authenticity | Sounds human? |
| Density | Anything cuttable? |
Below 35/50: revise.
See references/examples.md for before/after transformations.
MIT
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
whyashthakker/agent-skills-marketing
AminBlg/SimpleEnglish
aaron-he-zhu/seo-geo-claude-skills
jamditis/claude-skills-journalism
sipengxie2024/helios-writing
anthropics/skills
We added stop-slop from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
stop-slop fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
stop-slop has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in stop-slop — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: stop-slop is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added stop-slop from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
stop-slop is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in stop-slop — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
stop-slop reduced setup friction for our internal harness; good balance of opinion and flexibility.
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