no-ai-slop

Apply Louis Rossmann's anti-AI-slop writing rules to prose.

66|13|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/uplbtools/room-tba --skill no-ai-slop-uplbtools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-ai-slop
Source: https://github.com/uplbtools/room-tba/tree/main/.cursor/skills/no-ai-slop
Command: npx skills add https://github.com/uplbtools/room-tba --skill no-ai-slop-uplbtools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures your prose adheres to Louis Rossmann's anti-AI-slop writing rules, improving the clarity and effectiveness of user-facing text.

Core Features & Use Cases

  • Apply Anti-AI-Slop Rules: Follow Louis Rossmann's guidelines for writing.
  • Quick Fixes: Provides direct solutions for common writing issues.
  • Use Case: Use this Skill to review and improve your README, documentation, or marketing copy to avoid overly complex or unclear language.

Quick Start

Apply the no-ai-slop skill to your documentation and review the suggested changes.

Frequently Asked Questions about no-ai-slop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove AI slop from my README and documentation prose?

To remove AI slop from README and documentation prose, apply Louis Rossmann's anti-AI-slop writing rules, which enforce clarity and directness in user-facing text.

What is AI slop in writing and how do Rossmann's rules fix it?

AI slop in writing is overly complex or unclear language generated by AI. Rossmann's rules fix it by providing direct solutions that ensure prose clarity and directness.

Can I use anti-AI-slop rules to review marketing copy?

Yes, you can use anti-AI-slop rules to review marketing copy. The skill evaluates user-facing text like marketing copy, READMEs, and documentation to improve clarity.

Does the no-ai-slop skill apply to code or commit messages?

No, the no-ai-slop skill does not apply to code or one-line commit messages. It specifically targets prose clarity for user-facing text like documentation and READMEs.

What's the best way to ensure clarity and directness in technical documentation?

The best way to ensure clarity and directness in technical documentation is applying a dedicated set of anti-AI-slop writing rules that review prose and eliminate overly complex language.