no-slop

Enforce stylistic guidelines to eliminate AI-generated writing patterns in technical prose.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill no-slop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-slop
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/no-slop
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill no-slop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill removes the tell-tale signs of AI-generated text, ensuring your prose sounds human, direct, and professional rather than robotic or promotional.

Core Features & Use Cases

  • Anti-AI Pattern Enforcement: Automatically flags and corrects banned vocabulary, em-dash usage, and structural formulas like the rule of three.
  • Prose Optimization: Enforces a direct, journalist-style tone by stripping promotional fluff, vague attributions, and present-participle filler.
  • Use Case: Use this when drafting PR descriptions, technical documentation, or emails to ensure your writing is concise, evidence-based, and free of common AI stylistic crutches.

Quick Start

Apply the no-slop rules to the current draft of the project proposal to ensure it meets our human-writing standards.

Frequently Asked Questions about no-slop

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

FAQPage Schema
How do I remove AI-generated writing patterns from technical documentation?

To remove AI-generated writing patterns from technical documentation, apply strict stylistic guidelines that flag banned vocabulary, correct em-dash usage, and eliminate structural formulas. This enforces a direct, human-sounding, evidence-based communication style.

What is AI slop in technical writing and how do I identify it?

AI slop in technical writing consists of promotional filler, vague attributions, present-participle phrases, and structural formulas like the rule of three. Identifying it involves checking text against banned vocabulary lists and stylistic constraints.

Can I use prose linting for PR descriptions and emails?

Yes, you can use prose linting for PR descriptions and emails. The process applies structural constraints and specific formatting rules to external-facing text, ensuring concise, journalist-style, and evidence-based communication.

Do I need Node.js to enforce human-sounding writing standards?

Yes, Node.js is required to run the scripts that enforce human-sounding writing standards. The environment executes the linting rules and processes the text against the banned vocabulary and formatting constraints.

What is the best way to eliminate promotional filler in technical prose?

The best way to eliminate promotional filler in technical prose is by applying automated prose optimization that enforces a direct, journalist-style tone. This strips away vague attributions and promotional fluff while ensuring evidence-based text.

Why does my technical writing still sound robotic after editing?

Technical writing often still sounds robotic after editing because common AI stylistic crutches like present-participle filler, em-dash usage, and the rule of three remain. Enforcing strict stylistic guidelines and banned vocabulary lists resolves this.