Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
softaworks avatar

Writing Clearly And Concisely

  • 4k installs
  • 2.2k repo stars
  • Updated March 5, 2026
  • softaworks/agent-toolkit

How to write clear, concise, professional prose for humans using Strunk's 18 core rules and by avoiding LLM anti-patterns.

About

This skill applies William Strunk Jr.'s Elements of Style to make human-readable prose clearer and stronger. Developers use it when writing documentation, README files, commit messages, pull request descriptions, error messages, UI text, reports, and explanations. The skill covers 18 core rules: grammar and punctuation basics, paragraph structure, active voice, positive statements, concrete language, word economy, and emphasis placement. It also identifies AI writing patterns to avoid - puffery, empty '-ing' phrases, promotional adjectives, and overused vocabulary. The skill includes reference files organized by topic (grammar, composition, formatting, word choice), with a limited-context strategy that dispatches single sections to subagents to preserve token budget. 18 core writing rules from Strunk covering grammar, composition, active voice, and concision Specific anti-patterns for LLM-generated prose: puffery, empty phrases, promotional adjectives Modular reference files

  • 18 core writing rules from Strunk covering grammar, composition, active voice, and concision
  • Specific anti-patterns for LLM-generated prose: puffery, empty phrases, promotional adjectives
  • Modular reference files (grammar, composition, formatting, word choice) sized 1k-4.5k tokens each
  • Limited-context subagent strategy: dispatch single section (~1k-4.5k tokens) instead of full docs
  • Applies to documentation, commit messages, error messages, UI copy, reports, and all human-readable prose

Writing Clearly And Concisely by the numbers

  • 4,017 all-time installs (skills.sh)
  • +27 installs in the week ending Jul 28, 2026 (Skillselion tracking)
  • Ranked #98 of 1,901 Documentation skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

writing-clearly-and-concisely capabilities & compatibility

Capabilities
apply strunk's 18 rules to prose · identify and eliminate ai writing anti patterns · dispatch copyediting subagents with context effi · improve active voice, concision, and specificity
Use cases
documentation · code review
From the docs

What writing-clearly-and-concisely says it does

If you're writing sentences for a human to read, use this skill.
skill:softaworks/agent-toolkit#writing-clearly-and-concisely
npx skills add https://github.com/softaworks/agent-toolkit --skill writing-clearly-and-concisely

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4k
repo stars2.2k
Security audit3 / 3 scanners passed
Last updatedMarch 5, 2026
Repositorysoftaworks/agent-toolkit

What it does

Improve clarity and concision in prose - documentation, commit messages, error messages, UI copy, and reports - by applying Strunk's timeless writing rules.

Who is it for?

Writing documentation, README files, technical explanations, commit messages, pull request descriptions, error messages, UI copy, help text, reports, and summaries.

Skip if: Code generation, creative fiction, marketing copy with intentional brand voice, non-prose deliverables.

When should I use this skill?

Drafting or editing any prose intended for humans to read.

What you get

Written prose is clear, specific, concrete, active, and free of needless words and promotional language.

  • revised documentation prose
  • clearer README or instruction text

By the numbers

  • 18 core writing rules from Strunk
  • 4 reference files covering grammar, composition, formatting, and word choice
  • Section files range 1,000-4,500 tokens

Files

SKILL.mdMarkdownGitHub ↗

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:

SectionFile~Tokens
Grammar, punctuation, comma rules02-elementary-rules-of-usage.md2,500
Paragraph structure, active voice, concision03-elementary-principles-of-composition.md4,500
Headings, quotations, formatting04-a-few-matters-of-form.md1,000
Word choice, common errors05-words-and-expressions-commonly-misused.md4,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.

Related skills

Forks & variants (2)

Writing Clearly And Concisely has 2 known copies in the catalog totaling 205 installs. They canonicalize to this original listing.

How it compares

Use writing-clearly-and-concisely for prose style in docs; use dedicated linter or code-review skills for syntax and logic issues.

FAQ

When should I use this skill?

Use it whenever you write prose for humans: documentation, commit messages, error messages, UI text, reports, or explanations. If a human will read it as sentences, use this skill.

What is the limited-context strategy?

Instead of loading all docs, write your draft, then dispatch a subagent with your draft and one relevant section file (1k-4.5k tokens). This saves significant context while getting targeted copyediting.

What AI writing patterns should I avoid?

Avoid puffery (pivotal, crucial, enduring legacy), empty '-ing' phrases (ensuring reliability, showcasing features), promotional adjectives (seamless, cutting-edge), and overused vocabulary (delve, leverage, multifaceted, realm, tapestry).

Is Writing Clearly And Concisely safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.