---
name: unslop
description: "Edit agent prose and documentation for clear factual communication while preserving the requested voice and evidence."
---

# Unslop

Follow the consuming project's instructions and requested scope; use the
[portable defaults](../orbyn-workflow/references/project-policy.md) only where guidance is missing.

Lead with the concrete result or action. Use familiar words and verbs, one main
idea per paragraph, and headings only when they help navigation. Remove filler,
repetition, inflated claims, forced contrasts and decorative formatting.

Preserve the user's writing style when editing their material. Preserve exact
names, measured results, caveats, attribution and uncertainty. Do not manufacture
metrics or remove evidence to make prose sound stronger. Code comments should
explain non-obvious constraints rather than narrate the next line.

Use [content design](../orbyn-content-design/SKILL.md) for product copy. Do not
rewrite user-authored product content as a side effect of UI simplification.
Read the edited passage as a whole; a checklist of forbidden words cannot prove
clear writing.

Use [social-content](../social-content/SKILL.md) for social post strategy, author
voice, platform adaptation and carousel copy; this skill supplies the prose pass.
Use [social-preview](../social-preview/SKILL.md) for rendered feed mockups and
attached visuals. Editing a caption does not require generating visual assets.

## Operational method

Use the [local operating method](references/operating-method.md) for the execution
sequence, concrete failure case, expected result and stopping condition. It is
Orbyn-authored guidance; historical source notices remain in provenance.