Menu

Individual skill

unslop

Rewrite prose so it stops reading as machine-generated, using EndoStack's numbered catalog of AI-writing tells. Use on /unslop, "de-AI this", "clean up this draft", "make this plain", and whenever another skill sends text here for a slop pass.

plugins/requie/endostack/skills/unslop/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# unslop

Edit the given text so a reader cannot tell a model wrote it. Keep the author's meaning, every real qualification, and the register they chose. This file is the canonical catalog of writing tells for EndoStack. Other skills cite its rule ids (`U1`, `U2`, and so on), so ids are permanent. A retired rule keeps its id and is marked retired. New rules get the next unused number.

Do not use this skill on product UI copy that has its own style guide, on code or configuration, or on text that must stay verbatim (quotations, legal wording, error strings that code matches on).

## Procedure

1. Read the whole text once. Work out what it claims, who it is for, and what tone it uses. If the caller named a tone or audience, use theirs.
2. Walk the catalog below against every sentence. Each rule names the pattern and the fix.
3. Rewrite each flagged span. The rewrite says the same thing in plainer form and keeps every condition, number, and caveat. If a sentence has no recoverable fact, instruction, or number once the tell is removed, delete the sentence.
4. Keep the tone. Formal text stays formal; a casual note stays casual. Plain does not mean curt.
5. Scan the result again from the top. Fixes create new tells (a deleted em dash often becomes a colon hinge).
6. Write the edit back to the file, or return the text. If the caller asked for a summary, list the rule ids that fired and how many times.