unslop

Detect and rewrite AI writing patterns in text using numbered style rules.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill unslop-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: unslop
Source: https://github.com/NalinDalal/skillset/tree/main/skills/quality/unslop
Command: npx skills add https://github.com/NalinDalal/skillset --skill unslop-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated text carries recognizable tells like vague attributions, em dash overuse, chatbot phrases, and filler that make writing feel generic and untrustworthy. This Skill scans any text for those patterns and rewrites it to sound direct and human while preserving meaning and tone. ## Core Features & Use Cases - Pattern Detection: Scans text against a numbered rule set covering content, language, style, filler, jargon, and plain-speech issues. - Meaning-Preserving Rewrites: Replaces AI vocabulary, hedging, and mannered prose with plain words without changing the intended message. - Use Case: You drafted a README or blog post with an AI assistant and it reads like marketing copy. Run this Skill to strip phrases like "delve", "furthermore", and "I hope this helps" and get back direct, concrete prose. ## Quick Start Review this document and remove all AI writing patterns while keeping the meaning and tone intact.

Frequently Asked Questions about unslop

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

FAQPage Schema
How do I remove AI writing patterns from my text?▼

Scan the text for known AI tells such as superficial -ing phrases, vague attributions, and chatbot closers, then rewrite each instance with plain direct wording. The rewrite preserves the original meaning and matches the intended tone.

What are common signs of AI-generated writing?▼

Common signs include words like delve, crucial, and tapestry, forced rule-of-three groupings, em dash and colon overuse, boldface on every noun, sycophantic openers like "Great question!", and generic conclusions like "The future looks bright."

Does this work on technical documentation and READMEs?▼

Yes. The rules cover jargon and abstract metaphor nouns common in technical docs, such as substrate, vector, and scaffolding, replacing them with concrete words. It also fixes over-compressed fragments and passive voice typical of generated documentation.

Will rewriting change the meaning of my content?▼

No. The process explicitly preserves meaning and matches the intended tone. It only replaces vague or decorative phrasing with plainer equivalents, deletes filler, and restructures dense sentences for readability.

When should I not apply these writing rules?▼

Avoid applying them when a stylistic choice is deliberate, such as a bold lead-in that names an item and adds genuinely new detail, or passive voice where the actor is unknown. The rules note exceptions for legitimate colon and boldface use.