Eos Style Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/neurofoo/agent-skills --skill eos-styleThe instruction itself
10 sections, as written by the authorElements 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
- Place yourself in the background — Write to serve the reader, not to show off. Style emerges from content, not from the writer's ego.
- Write naturally — Don't consciously imitate others or force an affected style. Write as you would speak to an intelligent friend.
- Work from suitable design — Plan your piece. Know your scope and structure before writing extensively.
- Write with nouns and verbs — These give writing strength. Adjectives and adverbs are not your principal weapons.
- Revise and rewrite — Good writing is rewriting. Don't expect first drafts to be final.
- Don't overwrite — Avoid ornate, flowery prose. Rich prose is hard to digest.
- Don't overstate — Avoid superlatives and exaggeration. A single overstatement can undermine your credibility.
- Avoid qualifiers — Words like "very," "rather," "quite," "pretty," and "little" weaken prose.
- 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:
- [Most impactful change]
- [Second priority]
- [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
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take neurofoo/eos-style from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.