Stats
Actions
Tags
From workflows
Applies Strunk & White writing rules (omit needless words, active voice, concrete language) to prose. Use for tightening and clarifying any written text.
How this skill is triggered — by the user, by Claude, or both
Slash command
/workflows:writing-generalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Foundational style guide for clear, concise prose based on Strunk & White's Elements of Style.
Foundational style guide for clear, concise prose based on Strunk & White's Elements of Style.
Omit needless words.
Every word must earn its place. Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences.
| Rule | Explanation |
|---|---|
| Write in prose | Avoid bullet points and lists unless explicitly requested |
| Use active voice | "The committee approved the plan" not "The plan was approved" |
| Be concrete | Specific details over vague abstractions |
| Put statements in positive form | Say what something is, not what it isn't |
| Use definite language | Avoid hedging, qualifiers, and weasel words |
If you catch yourself writing ANY of these, DELETE THE SENTENCE and START FRESH:
| Anti-Pattern | Restart Approach |
|---|---|
| "It is [adjective] that..." | Rewrite as direct assertion |
| "There are [X] reasons" | Replace with direct list or synthesis |
| "In order to" | Replace with "to" |
| Sentence > 40 words with nested clauses | Break into 2-3 sentences |
| Passive voice hiding the actor | Name the actor, use active voice |
After deleting, restart the sentence with THE POINT first, then evidence.
Skipping the deletion pass is NOT HELPFUL — the user publishes bloated prose that buries their argument. Identify violations and purge them.
| Weak | Strong |
|---|---|
| utilize | use |
| in order to | to |
| due to the fact that | because |
| at this point in time | now |
| in the event that | if |
| prior to | before |
| subsequent to | after |
| with regard to | about |
| a large number of | many |
| is able to | can |
For comprehensive guidance, consult:
references/elements-of-style.md - Complete Strunk & White guide covering:
Weak original:
It is important to note that there are a variety of different factors that contribute to the overall success of the project in question.
Strong revision:
Several factors determine project success.
Weak original:
The report was written by the team and was subsequently reviewed by management prior to being distributed to stakeholders.
Strong revision:
The team wrote the report, management reviewed it, and stakeholders received it.
After completing any writing task, invoke /ai-anti-patterns to check for AI writing indicators.
npx claudepluginhub edwinhu/workflows --plugin workflowsApplies Strunk's Elements of Style principles to writing or editing prose: omit needless words, use active voice, prefer positive form, and keep related words together.
Applies Strunk's Elements of Style rules to edit documentation, commit messages, error messages, UI text, reports, and explanations for clarity and conciseness.
Applies Strunk's Elements of Style rules to edit documentation, commit messages, error messages, UI text, reports, and explanations for clarity and conciseness.