eos-style
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.
Best use case
eos-style is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using eos-style should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/eos-style/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How eos-style Compares
| Feature / Agent | eos-style | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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
Related Skills
37signals-rails-style
Apply 37signals/DHH Rails conventions when writing Ruby on Rails code. Use when building Rails applications, reviewing Rails code, or making architectural decisions. Covers various aspects of Rails application architecture, design and dependencies.
academic-writing-style
Personalized academic writing assistant for university assignments in Chinese and English. Use when users need help writing/revising academic reports, project docs, technical analyses, research reviews, or case studies. Produces natural prose avoiding AI markers. Triggers: academic writing, assignment, report, technical analysis, research review, case study. | 个性化学术写作助手,适用于中英文大学作业。触发词:学术写作、作业、报告、技术分析、研究综述、案例研究、项目文档。
innozverse-api-style
Follow API development conventions including RESTful design, Fastify patterns, Zod validation, error handling, and versioning. Use when building API endpoints, adding routes, or working with API code.
button-styles
Sistema de estilos de botones consistentes para iqEngi (Cards, CTAs, Formularios)
api-style-guide
Style and formatting rules for API/SDK documentation, samples, and tutorials.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".
obsidian-additions
Create supplementary materials attached to existing notes: experiments, meetings, reports, logs, conspectuses, practice sessions, annotations, AI outputs, links collections. Two-step process: (1) create aggregator space, (2) create concrete addition in base/additions/. INVOKE when user wants to attach any supplementary material to an existing note. Triggers: "addition", "create addition", "experiment", "meeting notes", "report", "conspectus", "log", "practice", "annotations", "links", "link collection", "аддишн", "конспект", "встреча", "отчёт", "эксперимент", "практика", "аннотации", "ссылки", "добавь к заметке".
observe
Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.
observability-review
AI agent that analyzes operational signals (metrics, logs, traces, alerts, SLO/SLI reports) from observability platforms (Prometheus, Datadog, New Relic, CloudWatch, Grafana, Elastic) and produces practical, risk-aware triage and recommendations. Use when reviewing system health, investigating performance issues, analyzing monitoring data, evaluating service reliability, or providing SRE analysis of operational metrics. Distinguishes between critical issues requiring action, items needing investigation, and informational observations requiring no action.
nvidia-nim
NVIDIA NIM inference microservices for deploying AI models with OpenAI-compatible APIs, self-hosted or cloud
numpy-string-ops
Vectorized string manipulation using the char module and modern string alternatives, including cleaning and search operations. Triggers: string operations, numpy.char, text cleaning, substring search.