writing-clearly-and-concisely

Apply Strunk's rules to prose for clear, concise writing.

29|1|Updated Jul 18, 2015
One-click install
npx skills add https://github.com/joshmanders/dotfiles --skill writing-clearly-and-concisely-joshmanders
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/joshmanders/dotfiles/tree/main/claude/skills/writing-clearly-and-concisely
Command: npx skills add https://github.com/joshmanders/dotfiles --skill writing-clearly-and-concisely-joshmanders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert ambiguous, verbose prose into clear, concise communication by applying Strunk's rules to everyday writing tasks such as documentation, commit messages, error messages, and UI text.

Core Features & Use Cases

  • Apply elementary rules of usage and principles of composition to improve sentences and paragraphs.
  • Provide a structured approach to editing that emphasizes active voice, positive form, concrete language, and omission of needless words.
  • Use cases include documentation, READMEs, code comments, error messages, and UI copy.

Quick Start

Paste your draft and request a Strunk-style copyedit for clarity and conciseness.

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 apply Strunk's rules to edit commit messages and READMEs?

To edit commit messages and READMEs, paste your draft text to apply Strunk's rules, enforcing active voice, positive form, and omission of needless words for concise documentation.

What is the best way to rewrite verbose UI text for clarity?

The best way to rewrite verbose UI text is applying Strunk's principles of composition, transforming ambiguous prose into definite, concrete language while omitting redundant words.

How do I make error messages more concise without losing context?

Make error messages concise by applying Strunk's rules to enforce definite language and active voice, stripping needless words while retaining essential context for clear communication.

Can I use this style guide for both short-form UI copy and long-form documentation?

Yes, you can use this style guide for both short-form UI copy and long-form documentation, applying elementary rules of usage and composition to improve sentences and paragraphs across formats.

Why does my technical writing sound passive and how do I fix it?

Technical writing sounds passive when lacking active voice; fix it by applying Strunk's rules to enforce positive form, definite language, and omission of needless words in your prose.