Yọ Slop

Make supplied prose clearer and less machine-shaped while preserving its contract. Keep exact identifiers, quotations, facts, citations, schemas, required formats, accepted terminology, and the owning artifact's decisions.

This is a direct or conditional cleanup outcome, not a mandatory tail stage after technical-writing or another writing owner. Use it when cleanup/pruning is explicitly requested or a material filler, AI-tell, repetition, vague-abstraction, or instruction-noise problem remains in otherwise settled prose.

Choose the pass

Use the normal cleanup pass for local clarity and voice problems. When the request explicitly asks to shorten prose, reduce verbosity, remove repetition, or lower instruction load, use prune and read prune prose. Do not infer prune from an ordinary editing or final-pass request.

Establish the pass

Identify the reader, artifact owner, purpose, language and locale, intended voice, and text that must remain exact. If these are unclear, fix only unambiguous filler and ask before a change that could alter meaning or tone.

Use the owning skill for content structure, evidence, technical truth, accessibility, localization, or acceptance. technical-writing owns human-facing developer documentation, technical communication, and applicable artifact copy. ko-skill owns skill behavior and proof. Yọ Slop owns cleanup and explicit pruning of settled prose, not structural or factual changes.

Match the reader

For human-facing prose, sound direct and specific. Vary sentence length naturally. Use a point of view only when the artifact permits one. Keep reference material neutral. Do not add deliberate mess, personality, or opinion to simulate humanity.