clear-writing
Makes your writing clearer, stronger, and more professional. Use this skill when the user says "write clearly", "clear writing", "improve writing" or for ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text.
When & Why to Use This Skill
This Claude skill enhances the clarity, impact, and professionalism of any written text by applying rigorous composition principles. Grounded in classic style guides like 'The Elements of Style', it focuses on using active voice, omitting needless words, and replacing jargon with direct language to ensure prose is concise, readable, and reader-centric.
Use Cases
- Technical Documentation: Refining README files, API documentation, and technical explanations to be more accessible and precise for developers.
- Developer Communication: Crafting clear, professional commit messages and pull request descriptions that effectively communicate code changes.
- UI/UX Copywriting: Improving error messages, tooltips, and help text to provide a better user experience through concise and helpful language.
- Business Reporting: Polishing reports, summaries, and internal memos by removing filler words and clichés to maintain an authoritative professional tone.
- Content Editing: Transforming loose or wordy drafts into punchy, direct prose suitable for public-facing blogs or documentation.
| name | clear-writing |
|---|---|
| description | Makes your writing clearer, stronger, and more professional. Use this skill when the user says "write clearly", "clear writing", "improve writing" or for ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. |
Writing Clearly and Concisely
Overview
William Strunk Jr.'s The Elements of Style (1918) teaches you to write clearly and cut ruthlessly.
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.
All 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
Custom rules
- Preserve every idea and fact unless clarity demands a change
- Keep paragraphs short (no more than three brief sentences)
- Vary sentence length to avoid monotony
- Replace jargon and complex words with plain, direct language; use contractions
- Remove clichés, filler adverbs, and stock metaphors (e.g., "navigate," "journey," "roadmap")
- Avoid bullet points unless essential for scan-ability
- Never add a summary or recap at the end—finish on a crisp, final line
- Do not use em dashes; use commas, periods, or rewrite as needed
- Add dry humor or an idiom if it fits, but never sound like an infomercial
- After rewriting, review and fix any sentence that still feels machine-made