de-slopify

Identify and remove AI slop patterns from technical documentation.

Updated Aug 23, 2026

Search Tags:#documentation #tone #editing #patterns #manual-review #em-dash #deslopify

Ready to run

npx skills add https://github.com/Dunc4nJ/agent-skills --skill de-slopify-dunc4nj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: de-slopify
Source: https://github.com/Dunc4nJ/agent-skills/tree/main/skills/de-slopify
Command: npx skills add https://github.com/Dunc4nJ/agent-skills --skill de-slopify-dunc4nj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Remove telltale signs of AI-generated "slop" writing from documentation to ensure an authentic human voice across README files, API docs, and other public-facing content.

Core Features & Use Cases

Manual review guidance for identifying patterns like emdash overuse, "Here's why" phrases, and "It's not X, it's Y" formulas, with recommended rewrites to sound natural.
Centralized reference to common AI slop patterns in PATTERNS.md to guide consistent revisions.
Tone consistency checks and publication-readiness guidance to ensure docs read as human-authored before release.

Quick Start

Review the target documentation and manually revise lines that show AI-like writing to replace emdashes and clichés with natural phrasing.

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 technical documentation?▼

Remove AI writing patterns from technical documentation by manually reviewing text for em-dash overuse and clichés, then revising lines to restore a natural, human tone before publication.

What are common AI slop artifacts in README files and API docs?▼

Common AI slop artifacts in README files and API docs include em-dash overuse, "Here's why" phrases, and "It's not X, it's Y" formulas that make technical writing sound artificially generated.

What is the best way to make AI generated text sound human?▼

The best way to make AI generated text sound human is to prioritize manual revision over automated regex fixes, focusing on context and readability to ensure an authentic voice.

Can I automate tone consistency checks for public-facing software docs?▼

Tone consistency checks for public-facing software docs emphasize manual review guidance and centralized pattern references rather than full automation, ensuring docs read as human-authored before release.

Why manually revise AI text instead of using regex-based fixes?▼

Manual revision is preferred over regex-based fixes because it prioritizes context and readability, preventing unnatural phrasing that automated replacements often introduce into documentation.