plain-writing
Revise prose for clarity, or draft a document in Charlie's plain style. Not for routine replies or code.
SKILL.mdskills/plain-writing/SKILL.md
GitHubPlain writing
Apply the Writing section of ~/.pi/agent/AGENTS.md. Read that file if it is not already loaded. This shared baseline applies in Pi, Codex, and Claude. This skill adds a focused editing pass.
Revise
When the draft may have been machine-written, or the user says it reads as generated, read references/ai-tells.md first and check the text against its pattern list before editing.
- Preserve the facts, uncertainty, and intended meaning. Do not turn an estimate into a measured result or a suggestion into a decision.
- Give each sentence one main point. Split cramped sentences, but keep the explanation complete. Shorter is useful only when the reader still understands the claim.
- Name the person or tool doing the work. Explain necessary technical terms on first use. Replace invented compounds with ordinary phrasing.
- Remove empty emphasis and repeated explanations. Use one example when it helps. Do not pad lists to three items for rhythm.
- Read the result as a newcomer. Check that each clause adds needed information and that causes, contrasts, and exceptions remain clear.
Example
Before
The feature index is like a card catalog that the optimizer can flip through.
After
The feature index is a list of named features. The optimizer can look up which feature matches a request.