writing-clearly-and-concisely

Convert vague prose into clear, concise text using Strunk's rules.

Updated Mar 11, 2023
One-click install
npx skills add https://github.com/viktorvan/dot-files --skill writing-clearly-and-concisely-viktorvan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-clearly-and-concisely
Source: https://github.com/viktorvan/dot-files/tree/main/opencode/skill/elements-of-style-writing-clearly-and-concisely
Command: npx skills add https://github.com/viktorvan/dot-files --skill writing-clearly-and-concisely-viktorvan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users convert vague prose into clear, concise text by applying Strunk's timeless rules to everyday writing tasks. It is applicable to documentation, commit messages, error messages, UI copy, reports, and explanations across technical and non-technical content.

Core Features & Use Cases

  • Rule-based editing: Apply Strunk's elementary rules to improve grammar, style, and word choice.
  • Active voice & concrete language: Encourage direct, decisive communication and the omission of needless words.
  • Use Case: Draft documentation, code comments, or UI text with guidance that enhances clarity and brevity.

Quick Start

Use this skill to copyedit a paragraph by feeding it into the AI with the target text and the style guide.

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 edit vague prose to write more clearly and concisely?

You can edit vague prose by applying Strunk's timeless rules to enforce active voice, definite language, and omission of needless words. This converts vague prose into clear, concise text suitable for documentation, reports, and explanations.

Can I use this approach to improve commit messages and UI copy?

Yes, you can improve commit messages and UI copy by applying these rule-based editing techniques. The skill enforces active voice and concrete language, ensuring direct, decisive communication across everyday technical writing tasks.

What is the best way to omit needless words in technical documentation?

The best way to omit needless words in technical documentation is to apply a rule-based style guide that enforces active voice and definite language. This omits redundant phrases, converting vague prose into concise, example-driven rewrites.

Does this style guide work for non-technical reports and explanations?

Yes, this style guide works for non-technical reports and explanations by enforcing consistent style and concrete language. It applies Strunk's elementary rules to enhance clarity and brevity across both technical and non-technical content.

How do I copyedit a paragraph using Strunk's elementary rules?

To copyedit a paragraph using Strunk's elementary rules, feed the target text into the AI alongside the style guide. This process enforces active voice and omission of needless words, generating example-driven rewrites for clearer prose.