skills.rest
georgekhananaev
georgekhananaevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

elements-of-style

Rewrite human-facing prose for clarity and conciseness using Strunk's Elements of Style.

27|9|Updated Jan 4, 2026
Search Tags:#documentation#editing#clarity#prose#conciseness#style-guides#Elements of Style
One-click install
npx skills add https://github.com/georgekhananaev/claude-skills-vault --skill elements-of-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: elements-of-style
Source: https://github.com/georgekhananaev/claude-skills-vault/tree/main/.claude/skills/elements-of-style
Command: npx skills add https://github.com/georgekhananaev/claude-skills-vault --skill elements-of-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps writers produce clear, concise prose by applying Strunk's Elements of Style to human-facing content such as documentation, README files, commit messages, PR descriptions, error messages, and UI copy.

Core Features & Use Cases

  • Active voice enforcement: Rewrites sentences to use active voice where appropriate.
  • Omit needless words: Eliminates redundant phrasing to tighten prose.
  • Concrete language: Converts vague terms into specific, tangible language.
  • Use case: A developer needs to turn a long README paragraph into succinct guidance for users.

Quick Start

Rewrite the following paragraph to be clear and concise using Strunk's Elements of Style: "The investigation of the issue was conducted by the team in a manner that demonstrated a comprehensive awareness of the potential problems."

Frequently Asked Questions about elements-of-style

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

FAQPage Schema
How do I make my README documentation more clear and concise?▼

You can improve README and documentation clarity by enforcing active voice, omitting needless words, and replacing vague phrasing with concrete language to tighten your prose.

What is the best way to rewrite commit messages and PR descriptions for clarity?▼

The best way to rewrite commit messages and PR descriptions for clarity is by applying Strunk's Elements of Style guidelines, actively enforcing active voice and eliminating redundant phrasing.

How does active voice enforcement improve UI copy and error messages?▼

Active voice enforcement improves UI copy and error messages by rewriting passive sentences into direct statements, converting vague terms into specific tangible language, and omitting needless words.

Can I use this prose editing approach to tighten a long README paragraph?▼

Yes, you can use this prose editing approach to turn a long README paragraph into succinct guidance by ruthlessly eliminating redundant phrasing and applying Elements of Style principles.

When should I not use automated prose editing for technical documentation?▼

You should avoid using automated prose editing for technical documentation when preserving the original passive tone is intentionally required or when specific structural vocabulary must remain unchanged.

Related Skills

Explore More Content & Communication Skills→
CygnusfearCygnusfear
5

writing-clearly-and-concisely

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

Community
Basic
mkobitmkobit
3

Technical writing

Enforce ventilated prose and concise writing standards in Markdown and AsciiDoc files.

Community
Basic
JayRHaJayRHa
3

proofreader

Edit prose for grammar, spelling, punctuation, clarity, and concision.

Community
Intermediate
lmorchardlmorchard
9

writing-clearly

Apply Strunk's Elements of Style rules to tighten prose drafts.

Community
Intermediate