home / skills / softaworks / agent-toolkit / writing-clearly-and-concisely

writing-clearly-and-concisely skill

/skills/writing-clearly-and-concisely

This skill helps you write clear, concise human-facing prose by applying Strunk rules to documentation, messages, and UI text.

npx playbooks add skill softaworks/agent-toolkit --skill writing-clearly-and-concisely

Review the files below or copy the command above to add this skill to your agents.

Files (8)
SKILL.md
3.7 KB
---
name: writing-clearly-and-concisely
description: Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
---

# Writing 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:

1. Write your draft using judgment
2. Dispatch a subagent with your draft and the relevant section file
3. 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)**:

1. Form possessive singular by adding 's
2. Use comma after each term in series except last
3. Enclose parenthetic expressions between commas
4. Comma before conjunction introducing co-ordinate clause
5. Don't join independent clauses by comma
6. Don't break sentences in two
7. Participial phrase at beginning refers to grammatical subject

**Elementary Principles of Composition**:

8. One paragraph per topic
9. Begin paragraph with topic sentence
10. **Use active voice**
11. **Put statements in positive form**
12. **Use definite, specific, concrete language**
13. **Omit needless words**
14. Avoid succession of loose sentences
15. Express co-ordinate ideas in similar form
16. **Keep related words together**
17. Keep to one tense in summaries
18. **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.

Overview

This skill teaches clear, concise prose for any writing humans will read. It packages Strunk-style rules and AI-specific anti-patterns to make documentation, messages, UI copy, and reports tighter and more professional. Use it to edit drafts or generate new text with human-first clarity.

How this skill works

The skill inspects prose and applies core rules: prefer active voice, use positive statements, choose concrete language, and omit needless words. It flags puffery and common AI-generated patterns, and provides focused edits when you supply a draft or a single document section. For limited context, it edits a single file or section (~1,000–4,500 tokens) to preserve intent while saving token budget.

When to use it

  • Writing or editing documentation, READMEs, and technical explanations
  • Composing commit messages, pull request descriptions, and changelogs
  • Crafting error messages, UI copy, help text, and tooltips
  • Preparing reports, summaries, or stakeholder explanations
  • Improving clarity and concision during code review or copy editing

Best practices

  • Start each paragraph with a clear topic sentence and keep one topic per paragraph
  • Prefer active voice and positive statements; avoid nominalizations and passive constructions
  • Use definite, specific, and concrete language instead of vague buzzwords
  • Omit needless words—remove redundancies, filler phrases, and empty modifiers
  • Keep related words together and place emphasis at the end of the sentence
  • When context is tight, edit one section file at a time rather than loading entire projects

Example use cases

  • Edit a README section for clarity using the principles of composition
  • Shorten and sharpen commit messages before merging a branch
  • Rewrite error messages so they tell users what happened and how to fix it
  • Revise UI help text to remove jargon and reduce length
  • Dispatch a subagent to copyedit a single document section and return a concise revision

FAQ

Which reference covers active voice and concision?

Use the section on elementary principles of composition; it focuses on active voice, positive form, concrete language, and omitting needless words.

How do I work with limited context?

Draft your text, then send only the relevant section (1,000–4,500 tokens) for copyediting to preserve intent and save token budget.