Unslop
Humanize AI-generated prose. Audit first. Rewrite only when the user asks for a rewrite.
For every audit or rewrite, read references/core-contract.md.
It is the single behavior contract. Command files define routing and mechanics;
presets supply optional voice, but neither can override the core contract.
Routing
When the user invokes a sub-command (/unslop teach ..., /unslop cleanup ...), you MUST read references/commands/<command>.md before acting.
Non-optional — the command file defines the flow, and skipping it drops steps the
user expects. A bare /unslop <text> with no leading command word defaults to
rewrite. If the first word does not match a command but the intent clearly maps
to one (e.g. "flag the AI tells, don't change anything" → cleanup report-only),
load that command file and proceed as if invoked.
Routing by phrase
Sub-flows are reachable by their natural names without being top-level verbs.
When the user says any of these, load the named file and jump to the flow:
Interface
Read one preset from presets/ before writing.
Rewrite, preservation, register, and validation behavior lives only in
references/core-contract.md; do not recreate or override those rules here.
Output Format
For a quick rewrite, return the cleaned text only. For audit-only (cleanup
--report):
## Issues Found
- [Quoted issue, category, severity, why it reads as AI]
## Assessment
- [Which issues are clear problems]
- [Which issues are judgment calls or context-dependent]
For strict or requested analysis:
## Transformed Text
[The humanized version]
## Validation
- Constraints: [X]/[Y] preserved
- AI patterns: [N] remaining (was [M])
- Structure: [pass/fail]
- Readability: Grade [X], sentence variance [Y]
- Change: [X]% from original
- Score: [X]/40
Reference Files
Maintenance
The eval contracts define the product. Add scanner examples eval-first in
evals/fixtures/contracts/scanner-examples.json; use
evals/adversarial-evals.json for agent behavior and routing. Do not edit legacy
evals/evals.json. New patterns need a false-negative example and a
false-positive protection example. Agent behavior changes need a skill row
and a regenerated shared benchmark. For the
concrete procedures (add a phrase or structure, list current patterns, sync with
Wikipedia's signs-of-AI-writing page), read references/maintenance.md. Found a
new AI-ism in the wild? references/commands/contribute.md turns the exact
snippet into a contract example and a structured PR, keeping both user-confirmation gates.