Agent skill

writing-clearly-and-concisely

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.

Stars 1,357
Forks 105

Install this agent skill to your Project

npx add-skill https://github.com/softaworks/agent-toolkit/tree/main/dist/plugins/writing-clearly-and-concisely/skills/writing-clearly-and-concisely

SKILL.md

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:

  1. One paragraph per topic
  2. Begin paragraph with topic sentence
  3. Use active voice
  4. Put statements in positive form
  5. Use definite, specific, concrete language
  6. Omit needless words
  7. Avoid succession of loose sentences
  8. Express co-ordinate ideas in similar form
  9. Keep related words together
  10. Keep to one tense in summaries
  11. 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.

Expand your agent's capabilities with these related and highly-rated skills.

softaworks/agent-toolkit

crafting-effective-readmes

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

1,357 105
Explore
softaworks/agent-toolkit

frontend-to-backend-requirements

Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

1,357 105
Explore
softaworks/agent-toolkit

feedback-mastery

Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts.

1,357 105
Explore
softaworks/agent-toolkit

meme-factory

Generate memes using the memegen.link API. Use when users request memes, want to add humor to content, or need visual aids for social media. Supports 100+ popular templates with custom text and styling.

1,357 105
Explore
softaworks/agent-toolkit

openapi-to-typescript

Converts OpenAPI 3.0 JSON/YAML to TypeScript interfaces and type guards. This skill should be used when the user asks to generate types from OpenAPI, convert schema to TS, create API interfaces, or generate TypeScript types from an API specification.

1,357 105
Explore
softaworks/agent-toolkit

plugin-forge

Create and manage Claude Code plugins with proper structure, manifests, and marketplace integration. Use when creating plugins for a marketplace, adding plugin components (commands, agents, hooks), bumping plugin versions, or working with plugin.json/marketplace.json manifests.

1,357 105
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results