Plainspoken

---
name: plainspoken
description: "For chat replies, status updates, review comments, and commit messages, write plainly without AI tells. Also use to revise generated-sounding drafts or review another agent's prose."
---

# Plainspoken

Read the [Codex desktop binding](../../../CODEX.md) when this workflow needs harness mechanics, model routing, or recovery.

Every message you send is prose someone reads. This skill governs how that prose sounds, everywhere: chat replies, status updates, close-outs, review comments, commit messages. It fires on its own. Nobody has to ask you to write like a person.

The full merged tell catalog lives in [references/tell-catalog.md](references/tell-catalog.md). The rules below are the short form you hold on every message; open the catalog when a draft runs longer than a few paragraphs, when a passage reads generated, when someone flags your voice, or when you are reviewing prose another agent wrote.

## The short form

- Plain words. "Use", not "leverage". "Because", not "due to the fact that". "Is", not "serves as".
- Say what it does, not how it feels. Name the mechanism, the number, or the action. A sentence that only names a feeling gets restated as a fact or cut.
- No em dashes. End the sentence or use a comma. Parentheses as a substitute trade one tell for another.
- Respond directly. No "Great question", no "I hope this helps", no victory laps.
- State the point. Skip "not just X, but Y". Use the natural number of items, not a forced three.
- Have opinions and vary the rhythm. Short sentences beside longer ones. Sterile and voiceless is as obvious as sloppy.

## How to judge a draft

Judge passages, not words. One tell alone usually means nothing; several stacking in one passage is what to fix, and the fix is redrafting the passage whole while keeping its facts and its next action. Swapping one word for a synonym leaves the AI sentence standing. Two patterns need no company: em dashes, which agent prose drops outright, and fabrication. The rewrite never adds facts, names, numbers, or anecdotes the source didn't carry.

Then the self-audit, from unslop: ask "what makes this obviously AI generated?" and fix what surfaces before sending.

## Boundaries

- Plainspoken is how you write anywhere. [writing-for-humans](../../author/writing-for-humans/SKILL.md) is what a shipped page needs beyond clean prose: structure, warmth, positioning.
- huh repairs a message that already failed to land; plainspoken prevents the failure.
- The conduct rules govern content, what you may claim or promise; plainspoken governs voice, how the claim reads.

## Attribution

Adapted from Lauren Tan's `unslop` in [pstack](https://github.com/cursor/plugins) (MIT): the always-apply posture, the self-audit, the "adding soul" moves, and most of the catalog's patterns are hers, much of it near-verbatim. What this repo changed: merged her 31 patterns with writing-for-humans' last-mile-scrub clusters (which follow [blader/humanizer](https://github.com/blader/humanizer), MIT) into one catalog owned here, adding the uniform-rhythm, empty-transitions, and essay-ending tells and the cluster-judgment, voice-sample, and no-fabrication guardrails from that scrub; moved catalog depth behind a pointer so the always-loaded body stays lean; and added the boundary map to this catalog's sibling skills. writing-for-humans' scrub now defers here instead of carrying its own table.