How does it provide feedback?

It generates a structured table reviewing your text against each principle, followed by a prioritized list of key issues and suggested improvements.

Does it work for creative writing?

While it follows standard prose rules, the skill includes guidelines to recognize when creative writing or voice intentionally breaks certain rules for effect.

Can I use this for technical README files?

Yes, it is specifically designed to help developers turn dense technical jargon into clear, actionable documentation.

What is the eos-style Claude Code skill?

It is a specialized tool that analyzes your writing using the 21 stylistic reminders from Strunk & White's 'The Elements of Style' to ensure clarity and professional tone.

Elements of Style Reviewer

Name: Elements of Style Reviewer
Author: neurofoo

byneurofoo

•

Content Management

Reviews prose and documentation against Strunk & White's 21 classic style principles to improve writing clarity and tone.

About

The Elements of Style Reviewer skill brings the legendary writing guidance of Strunk & White directly into your development workflow. By analyzing text against the 21 core principles found in Chapter V of 'The Elements of Style,' this skill provides a structured audit of your prose. It helps writers eliminate wordiness, avoid unnecessary qualifiers, and strengthen their message using nouns and verbs. Whether you are drafting technical documentation, README files, or project proposals, this skill ensures your writing is professional, concise, and impactful.

Key Features

Structured feedback table with status indicators for each principle
Automated 21-point writing audit based on Strunk & White's Chapter V
Prioritized issue reporting categorized by impact level
Analysis of word choice, including 'fancy words' and awkward adverbs
Actionable suggestions for rewriting verbose or flowery prose
35 GitHub stars

Use Cases

Polishing technical documentation and README files for better readability
Reviewing blog post drafts or internal reports for a professional tone
Identifying and removing weak qualifiers and overstatements in project proposals

About

Key Features

Structured feedback table with status indicators for each principle
Automated 21-point writing audit based on Strunk & White's Chapter V
Prioritized issue reporting categorized by impact level
Analysis of word choice, including 'fancy words' and awkward adverbs
Actionable suggestions for rewriting verbose or flowery prose
35 GitHub stars

Use Cases

Polishing technical documentation and README files for better readability
Reviewing blog post drafts or internal reports for a professional tone
Identifying and removing weak qualifiers and overstatements in project proposals