writing-clearly-and-concisely
Scannednpx machina-cli add skill softaworks/agent-toolkit/writing-clearly-and-concisely --openclawWriting Clearly and Concisely
Overview
Write with clarity and force. This skill covers what to do (Strunk) and what not to do (AI patterns).
When to Use This Skill
Use this skill whenever you write prose for humans:
- Documentation, README files, technical explanations
- Commit messages, pull request descriptions
- Error messages, UI copy, help text, comments
- Reports, summaries, or any explanation
- Editing to improve clarity
If you're writing sentences for a human to read, use this skill.
Limited Context Strategy
When context is tight:
- Write your draft using judgment
- Dispatch a subagent with your draft and the relevant section file
- Have the subagent copyedit and return the revision
Loading a single section (~1,000-4,500 tokens) instead of everything saves significant context.
Elements of Style
William Strunk Jr.'s The Elements of Style (1918) teaches you to write clearly and cut ruthlessly.
Rules
Elementary Rules of Usage (Grammar/Punctuation):
- Form possessive singular by adding 's
- Use comma after each term in series except last
- Enclose parenthetic expressions between commas
- Comma before conjunction introducing co-ordinate clause
- Don't join independent clauses by comma
- Don't break sentences in two
- Participial phrase at beginning refers to grammatical subject
Elementary Principles of Composition:
- One paragraph per topic
- Begin paragraph with topic sentence
- Use active voice
- Put statements in positive form
- Use definite, specific, concrete language
- Omit needless words
- Avoid succession of loose sentences
- Express co-ordinate ideas in similar form
- Keep related words together
- Keep to one tense in summaries
- Place emphatic words at end of sentence
Reference Files
The rules above are summarized from Strunk's original text. For complete explanations with examples:
| Section | File | ~Tokens |
|---|---|---|
| Grammar, punctuation, comma rules | 02-elementary-rules-of-usage.md | 2,500 |
| Paragraph structure, active voice, concision | 03-elementary-principles-of-composition.md | 4,500 |
| Headings, quotations, formatting | 04-a-few-matters-of-form.md | 1,000 |
| Word choice, common errors | 05-words-and-expressions-commonly-misused.md | 4,000 |
Most tasks need only 03-elementary-principles-of-composition.md — it covers active voice, positive form, concrete language, and omitting needless words.
AI Writing Patterns to Avoid
LLMs regress to statistical means, producing generic, puffy prose. Avoid:
- Puffery: pivotal, crucial, vital, testament, enduring legacy
- Empty "-ing" phrases: ensuring reliability, showcasing features, highlighting capabilities
- Promotional adjectives: groundbreaking, seamless, robust, cutting-edge
- Overused AI vocabulary: delve, leverage, multifaceted, foster, realm, tapestry
- Formatting overuse: excessive bullets, emoji decorations, bold on every other word
Be specific, not grandiose. Say what it actually does.
For comprehensive research on why these patterns occur, see signs-of-ai-writing.md. Wikipedia editors developed this guide to detect AI-generated submissions — their patterns are well-documented and field-tested.
Bottom Line
Writing for humans? Load the relevant section from elements-of-style/ and apply the rules. For most tasks, 03-elementary-principles-of-composition.md covers what matters most.
Source
git clone https://github.com/softaworks/agent-toolkit/blob/main/skills/writing-clearly-and-concisely/SKILL.mdView on GitHub Overview
Write with clarity and force using Strunk's rules. This skill covers actionable guidance on what to do and what not to do, including identifying AI-writing patterns to avoid.
How This Skill Works
Root your writing in Strunk's Elements of Style and apply active voice, positive form, and concrete language. When context is tight, use the Limited Context Strategy: draft, dispatch a subagent for copyediting, and incorporate revisions.
When to Use It
- Documentation, README files, and technical explanations
- Commit messages and pull request descriptions
- Error messages, UI copy, help text, and comments
- Reports, summaries, or any explanation
- Editing to improve clarity
Quick Start
- Step 1: Draft for clarity using Strunk’s rules
- Step 2: If context is tight, dispatch a subagent with the draft and relevant section
- Step 3: Apply the subagent’s copyedit and finalize with active voice and concise wording
Best Practices
- Use active voice
- Put statements in positive form
- Use definite, specific, concrete language
- Omit needless words
- Keep related words together
Example Use Cases
- Rewrite a vague error message into a clear, actionable one
- Refactor a verbose commit message into a short, concrete summary
- Polish UI copy to remove fluff and improve clarity
- Edit a documentation paragraph to use concrete language
- Streamline a report section by trimming needless words