de-slopify

Name: de-slopify
Availability: InStock
Author: Nightstream

Edit documentation prose to remove AI writing artifacts like emdash overuse.

29|8|Updated Aug 17, 2025

Search Tags:#documentation #writing #tone #editing #readme #content quality #humanization

Ready to run

npx skills add https://github.com/LFDT-Nightstream/Nightstream --skill de-slopify-lfdt-nightstream

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: de-slopify
Source: https://github.com/LFDT-Nightstream/Nightstream/tree/main/.agents/skills/de-slopify
Command: npx skills add https://github.com/LFDT-Nightstream/Nightstream --skill de-slopify-lfdt-nightstream

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

De-slopify removes common AI-generated writing artifacts so your documentation reads with a more natural, human tone.

Core Features & Use Cases

Emdash cleanup: reduces overuse of emdashes and replaces them with commas, semicolons, or sentence recasts where appropriate.
Tropes detection and rewrites: flags and rewrites patterns like “Here’s why” and “It’s not X, it’s Y” into clearer, more direct prose.
Manual, line-by-line editing guidance: emphasizes systematic human review rather than brittle find-and-replace.

Quick Start

Paste the README text you want to polish into your AI and ask it to de-slopify by removing emdash overuse and common AI writing tropes while rewriting sentences to sound authentically human.

Frequently Asked Questions about de-slopify

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

FAQPage Schema

How do I remove AI writing patterns from my README files?▼

To remove AI writing patterns from README files, apply manual line-by-line editing to eliminate emdash overuse and boilerplate tropes, replacing them with clearer, direct prose. This humanization process restores a natural tone and improves documentation credibility.

What are common AI writing artifacts in technical documentation?▼

Common AI writing artifacts in technical documentation include emdash overuse, boilerplate lead-ins, and recognizable tropes like “Here’s why” or “It’s not X, it’s Y.” These patterns reduce text credibility and signal automated generation to readers.

How do I rewrite AI-generated API docs to sound more human?▼

To rewrite AI-generated API docs to sound more human, systematically review the text line by line. Recast sentences to remove telltale tropes and emdashes, replacing them with commas, semicolons, or direct phrasing for authentic clarity.

Can I use automated find-and-replace to fix AI tone in documentation?▼

You should not use automated find-and-replace to fix AI tone in documentation. Effective humanization requires manual revision guided by specific pattern eliminations and replacement heuristics, ensuring natural sentence recasts rather than brittle substitutions.

When should I edit documentation for AI slop removal?▼

You should edit documentation for AI slop removal when preparing public-facing text like README files and API docs. If patterns like emdash overuse or boilerplate lead-ins reduce credibility, manual line-by-line revision ensures a genuinely human tone.