Strunk & White Style Review

VerifiedSafe

Strunk & White style review using the 21 reminders from 'Elements of Style' Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone.

Sby Skills Guide Bot
ContentIntermediate
7/28/2026
Claude Code
#writing#editing#style-review#prose#clarity

Recommended for

Automated summary

This skill reviews writing against the 21 style reminders from Chapter V of Strunk & White's "The Elements of Style" and returns a structured review table with specific feedback.

Strengths

  • Provides a structured 21-principle checklist with Pass/Needs Work/N/A status for each item.
  • Offers actionable feedback tied to examples from the submitted text rather than broad commentary.
  • Separates high-priority and medium-priority issues to guide revision.

Limitations

  • Uses a prescriptive Strunk & White approach that may not suit deliberately experimental or highly literary prose.
  • Produces a review rather than a full rewrite of the text.
  • Some principles may be marked N/A, which can reduce depth for very short or specialized pieces.
When to use it

Use this skill when you need a structured, prioritized style review of a draft, article, or documentation passage.

When not to use it

Avoid this skill for open-ended creative rewriting, academic literary analysis, or writing where stylistic rule-breaking is intentional and central.

Security analysis

Safe
Quality score88/100

The skill is purely a prose-editing checklist. It declares no allowed tools, contains no bash/docker/network instructions, no file or secret access, and no obfuscated payloads. Its only action is instructing the model to analyze supplied text and emit a markdown table, so there is no meaningful execution risk.

No concerns found

How this analysis is made

Examples

Review a blog draft
Review this blog draft against the 21 Elements of Style reminders. Give me the status table, high-priority issues, and concrete fixes: [paste draft here]
Tighten documentation prose
Use the eos-style skill to review this documentation section for clarity, qualifiers, overwriting, and awkward phrasing. Mark N/A where a principle does not apply: [paste section here]
Prioritize edits before publishing
Run a Strunk & White style review on this article and tell me which medium- and high-priority issues I should fix before publishing: [paste article here]

name: eos-style description: Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Use when editing prose, reviewing drafts, or improving writing clarity and tone. user-invocable: true

Elements of Style: 21 Style Reminders

Review writing against Strunk & White's 21 style principles from Chapter V "An Approach to Style."

Instructions

Analyze the provided text against each of the 21 style reminders. Focus on actionable feedback with specific examples from the text. Not all principles apply to every piece—mark N/A when appropriate.

Output Format

Text Under Review: [title or brief description]


Style Review

| # | Principle | Status | Notes | |---|-----------|--------|-------| | 1 | Place yourself in the background | Pass/Needs Work/N/A | [specific feedback] | | 2 | Write naturally | Pass/Needs Work/N/A | [specific feedback] | | 3 | Work from suitable design | Pass/Needs Work/N/A | [specific feedback] | | 4 | Write with nouns and verbs | Pass/Needs Work/N/A | [specific feedback] | | 5 | Revise and rewrite | Pass/Needs Work/N/A | [specific feedback] | | 6 | Don't overwrite | Pass/Needs Work/N/A | [specific feedback] | | 7 | Don't overstate | Pass/Needs Work/N/A | [specific feedback] | | 8 | Avoid qualifiers | Pass/Needs Work/N/A | [specific feedback] | | 9 | Don't affect breeziness | Pass/Needs Work/N/A | [specific feedback] | | 10 | Use orthodox spelling | Pass/Needs Work/N/A | [specific feedback] | | 11 | Don't explain too much | Pass/Needs Work/N/A | [specific feedback] | | 12 | Don't construct awkward adverbs | Pass/Needs Work/N/A | [specific feedback] | | 13 | Make sure speakers are clear | Pass/Needs Work/N/A | [specific feedback] | | 14 | Avoid fancy words | Pass/Needs Work/N/A | [specific feedback] | | 15 | Use dialect sparingly | Pass/Needs Work/N/A | [specific feedback] | | 16 | Be clear | Pass/Needs Work/N/A | [specific feedback] | | 17 | Don't inject opinion | Pass/Needs Work/N/A | [specific feedback] | | 18 | Use figures of speech sparingly | Pass/Needs Work/N/A | [specific feedback] | | 19 | Don't sacrifice clarity for shortcuts | Pass/Needs Work/N/A | [specific feedback] | | 20 | Avoid foreign languages | Pass/Needs Work/N/A | [specific feedback] | | 21 | Prefer standard to offbeat | Pass/Needs Work/N/A | [specific feedback] |


Key Issues Found

High Priority

  • [Issue with specific example and suggested fix]

Medium Priority

  • [Issue with specific example and suggested fix]

Principle Reference

  1. Place yourself in the background — Write to serve the reader, not to show off. Style emerges from content, not from the writer's ego.

  2. Write naturally — Don't consciously imitate others or force an affected style. Write as you would speak to an intelligent friend.

  3. Work from suitable design — Plan your piece. Know your scope and structure before writing extensively.

  4. Write with nouns and verbs — These give writing strength. Adjectives and adverbs are not your principal weapons.

  5. Revise and rewrite — Good writing is rewriting. Don't expect first drafts to be final.

  6. Don't overwrite — Avoid ornate, flowery prose. Rich prose is hard to digest.

  7. Don't overstate — Avoid superlatives and exaggeration. A single overstatement can undermine your credibility.

  8. Avoid qualifiers — Words like "very," "rather," "quite," "pretty," and "little" weaken prose.

  9. Don't affect breeziness — Forced casualness and flip remarks suggest the writer values cleverness over substance.

  10. Use orthodox spelling — Follow standard conventions unless you have good reason not to.

  11. Don't explain too much — Trust the reader. Avoid excessive adverbs after "said" and over-explanatory dialogue tags.

  12. Don't construct awkward adverbs — Avoid forcing "-ly" onto words that don't take it naturally.

  13. Make sure speakers are clear — In dialogue, readers must always know who is speaking.

  14. Avoid fancy words — Prefer the plain word to the fancy one. "Home" not "domicile."

  15. Use dialect sparingly — The best dialect writers use minimal deviation from standard language.

  16. Be clear — Clarity is the foundation. Muddiness is not depth; obscurity is not profundity.

  17. Don't inject opinion — Keep personal opinions out unless they serve the work. They mark the egoist.

  18. Use figures of speech sparingly — Metaphors and similes need space. Constant comparison exhausts the reader.

  19. Don't sacrifice clarity for shortcuts — Strong, precise words are better than clever abbreviations.

  20. Avoid foreign languages — Write in English. Foreign phrases can seem pretentious.

  21. Prefer standard to offbeat — Choose established words over trendy or invented ones.


Summary

Overall Assessment: [Strong/Needs Revision/Major Issues]

Top 3 Improvements:

  1. [Most impactful change]
  2. [Second priority]
  3. [Third priority]

Guidelines

  • Focus on patterns, not isolated instances
  • Some rules can be broken intentionally for effect—note when this seems intentional
  • "Needs Work" means a pattern of violations, not a single instance
  • Technical or specialized writing may legitimately use jargon
  • Creative writing may intentionally break rules for voice

$ARGUMENTS

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/strunk-white-style-review-ms47vpk6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/strunk-white-style-review-ms47vpk6/download' --output '.skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md.part' && mv '.skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md.part' '.skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md' && test -s '.skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/eos-style' && cp -R '.skill-downloads/strunk-white-style-review-ms47vpk6' '.claude/skills/eos-style'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/strunk-white-style-review-ms47vpk6'

openskills read 'strunk-white-style-review-ms47vpk6'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/strunk-white-style-review-ms47vpk6/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills