writing-clearly

Apply Strunk's Elements of Style to improve prose clarity.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/opzero1/op1 --skill writing-clearly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly
Source: https://github.com/opzero1/op1/tree/main/packages/install/templates/skill/writing-clearly
Command: npx skills add https://github.com/opzero1/op1 --skill writing-clearly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prose often lacks clarity and conciseness; this Skill provides a practical framework based on Strunk's Elements of Style to help writers produce clear, concise text across documentation, UI copy, and communications.

Core Features & Use Cases

  • Apply active voice and positive form to sentences to improve directness.
  • Omit needless words and enforce concrete, specific language for documentation, commit messages, error messages, and user interfaces.
  • Ensure consistency in tense and structure to improve readability.
  • Use cases include drafting documentation, refining UI text, polishing error messages, and improving code comments.

Quick Start

Rewrite the following text to be clear and concise using Strunk's rules.

Frequently Asked Questions about writing-clearly

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

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

Improve prose clarity by applying active voice, positive form, and concrete language while omitting needless words based on Strunk's Elements of Style, ensuring your documentation is direct and easy to read.

What is the best way to write UI copy and error messages?

The best way to write UI copy and error messages is to enforce concrete, specific language and ensure consistency in tense and structure, which improves readability across user interfaces and product communications.

How do I apply active voice and positive form to technical writing?

Apply active voice and positive form to technical writing by rewriting sentences to improve directness, omitting needless words, and using concrete language for documentation, commit messages, and code comments.

Can I use this approach to refine code comments and commit messages?

Yes, you can refine code comments and commit messages by applying Strunk's rules to enforce conciseness, active voice, and concrete, specific language, ensuring consistency in tense and structure across your human-readable content.

When do I need to omit needless words in product documentation?

You need to omit needless words in product documentation when prose lacks clarity and conciseness, applying Strunk's framework to produce clear text across documentation, UI copy, and error messages.