domains / families / documents / unslop

unslop

combined

Cut AI tells from text you write or edit for a human reader (commit messages, PR titles and bodies, docs, code comments, replies). Apply before committing, posting, or sending; leave prose you didn't touch alone. Post-process AI-generated text through the unslop CLI to strip AI writing patterns before publishing

When to use

• When you have AI-generated text ready to publish and want a final cleanup pass
• When working in a shell pipeline where text quality needs to be enforced automatically
• When writing commit hooks or CI steps that validate content before it ships
• When you need reproducible text normalization across multiple runs

When not to use

• Processes prose only — not code, JSON, or structured data
• Does not catch factual errors or substantive writing issues
• Some replacements may not fit every context; review the output before publishing
• Requires Python tooling such as `pipx` or `uv` for standalone CLI installation

Skill page

Conflict

The two copies describe different procedures for the same goal. The first is a manual editing skill that instructs the agent to scan, rewrite, add voice, and self-audit against a long list of AI tells. The second is a CLI-based skill that installs and pipes text through the `unslop` command for deterministic post-processing. They overlap in intent but each contains material steps the other lacks (manual pattern list vs CLI pipeline/CI integration), so crowning one would hide a real alternative.