writing-clearly-and-concisely

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

6|1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/mgajewskik/opencode-config --skill writing-clearly-and-concisely-mgajewskik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/mgajewskik/opencode-config/tree/main/skills/writing-clearly-and-concisely
Command: npx skills add https://github.com/mgajewskik/opencode-config --skill writing-clearly-and-concisely-mgajewskik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps writers produce clearer, more professional prose by applying William Strunk Jr.'s timeless rules to cut fluff and avoid common AI writing patterns.

Core Features & Use Cases

  • Applies Strunk's core principles (active voice, positive form, concrete language, omission of needless words) to human-facing writing.
  • Supports use in documentation, commit messages, error messages, UI copy, and reports with practical examples.
  • Provides reference sections and best practices to minimize puffery and overlong phrasing while preserving meaning.

Quick Start

Draft a paragraph and ask this skill to apply Strunk's rules to improve clarity and remove AI-pattern fluff.

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 improve prose clarity and remove fluff from technical documentation?

To improve prose clarity, this Skill applies Strunk's core principles such as active voice, positive form, and omission of needless words to refine technical documentation. It edits human-facing text to ensure concrete language and minimize puffery while preserving original meaning.

What are common AI writing patterns and how do I avoid them in commit messages?

Common AI writing patterns include overlong phrasing and unnecessary puffery. This Skill avoids these patterns in commit messages by applying Strunk's rules to enforce active voice and concrete language, guiding copyediting workflows to produce clear, professional text.

Can I use this approach to edit UI copy and error messages?

Yes, you can edit UI copy and error messages using this approach. The Skill supports use across documentation, error messages, and reports, applying the Elements of Style rules to ensure your human-facing writing remains concise and free of needless words.

What is the best way to enforce active voice and concrete language in reports?

The best way to enforce active voice and concrete language in reports is applying Strunk's timeless rules. This Skill loads core principles from the Elements of Style and fetches reference guides as needed to actively guide edits and remove passive constructions.

Does this copyediting workflow require any external dependencies or reference modules?

No external dependencies are required for this copyediting workflow. The Skill operates independently, loading core rules from the Elements of Style internally and fetching reference guides only as needed to ensure concise writing without requiring external components.