writing-clearly-and-concisely

Apply Strunk's writing rules to improve clarity and conciseness in prose.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/hasparus/claude-skills-dotfiles --skill writing-clearly-and-concisely-hasparus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/hasparus/claude-skills-dotfiles/tree/main/writing-clearly-and-concisely
Command: npx skills add https://github.com/hasparus/claude-skills-dotfiles --skill writing-clearly-and-concisely-hasparus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps writers improve clarity and conciseness in any prose by applying Strunk's timeless rules.

Core Features & Use Cases

  • Provides actionable, rule-based guidance drawn from The Elements of Style for editing and rewriting text.
  • Suitable for documentation, commit messages, error messages, UI copy, reports, and general prose.
  • Enables focused, time-saving copyediting by targeting brevity, concrete language, and positive phrasing.

Quick Start

Provide a copyedit of the given draft using active voice and concrete language per Strunk's rules.

Frequently Asked Questions about writing-clearly-and-concisely

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make my documentation and reports more concise and professional?

You can improve clarity and conciseness by applying Strunk's timeless rules, which target brevity, active voice, and concrete language to produce focused, professional copyediting results for any prose.

How do I apply Strunk's writing rules to edit commit messages and UI text?

Apply Strunk's writing rules to edit commit messages and UI text by requesting a copyedit that enforces active voice and concrete language, ensuring technical explanations and interface copy remain brief and clear.

What is the best way to copyedit error messages for clarity and brevity?

The best way to copyedit error messages for clarity is through rule-based guidance drawn from The Elements of Style, using active voice and positive phrasing to make technical explanations direct and actionable.

Can I use this approach for general prose editing beyond technical documentation?

Yes, you can use this rule-based approach for general prose editing beyond technical documentation, as it provides actionable guidance for improving clarity and conciseness across any writing format.

When should I not use Strunk's rules for copyediting my writing?

You should avoid using Strunk's rules for copyediting when your writing requires stylistic flexibility, specialized formatting, or creative phrasing that intentionally deviates from strict brevity and active voice conventions.