eos-usage
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Best use case
eos-usage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Teams using eos-usage 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-usage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How eos-usage Compares
| Feature / Agent | eos-usage | 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 grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
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: 11 Rules of Usage Review writing against Strunk & White's 11 elementary rules of usage from Chapter I. ## Instructions Analyze the provided text for grammatical and mechanical errors. Flag specific violations with line numbers or quotes where possible. ### Output Format **Text Under Review**: [title or brief description] --- ## Usage Review | # | Rule | Status | Issues Found | |---|------|--------|--------------| | 1 | Form possessive singular with 's | Pass/Needs Work/N/A | [issues] | | 2 | Use serial comma | Pass/Needs Work/N/A | [issues] | | 3 | Enclose parenthetic expressions in commas | Pass/Needs Work/N/A | [issues] | | 4 | Comma before conjunction + independent clause | Pass/Needs Work/N/A | [issues] | | 5 | No comma splice | Pass/Needs Work/N/A | [issues] | | 6 | No sentence fragments | Pass/Needs Work/N/A | [issues] | | 7 | Use colon to introduce lists/appositives | Pass/Needs Work/N/A | [issues] | | 8 | Use dash for abrupt breaks | Pass/Needs Work/N/A | [issues] | | 9 | Subject-verb agreement | Pass/Needs Work/N/A | [issues] | | 10 | Proper pronoun case | Pass/Needs Work/N/A | [issues] | | 11 | Dangling modifiers | Pass/Needs Work/N/A | [issues] | --- ## Errors Found ### Rule 5: Comma Splices | Location | Error | Correction | |----------|-------|------------| | [line/quote] | "It is cold, we should go inside" | "It is cold; we should go inside" OR "It is cold, so we should go inside" | ### Rule 6: Sentence Fragments | Location | Fragment | Suggested Fix | |----------|----------|---------------| | [line/quote] | [fragment] | [complete sentence] | ### Rule 11: Dangling Modifiers | Location | Error | Correction | |----------|-------|------------| | [line/quote] | "Walking down the street, the trees were beautiful" | "Walking down the street, I noticed the beautiful trees" | --- ## Rule Reference 1. **Form the possessive singular by adding 's** — Charles's friend, Burns's poems, the witch's malice. Exceptions: ancient proper names ending in -es or -is (Jesus', Moses'), and common idioms (for conscience' sake). 2. **In a series of three or more, use a comma after each term except the last** — red, white, and blue. The serial comma prevents ambiguity. 3. **Enclose parenthetic expressions between commas** — "The best way to see a country, unless you are pressed for time, is to travel on foot." If the interruption is slight, commas may be omitted. 4. **Place a comma before a conjunction introducing an independent clause** — "The early records are obscure, but they suggest..." This rule applies when both clauses are independent (could stand alone). 5. **Do not join independent clauses with a comma** — This error is the "comma splice." Wrong: "It is cold, we should go inside." Right: "It is cold; we should go inside" or "It is cold. We should go inside." 6. **Do not break sentences in two** — Avoid sentence fragments. "I met them on a Cunard liner many years ago. Coming home from Liverpool to New York." The second part should not stand alone. 7. **Use a colon after an independent clause to introduce a list, appositive, amplification, or illustrative quotation** — "The situation is perilous: our enemies are many, our supplies few." 8. **Use a dash to set off an abrupt break or to announce a long appositive or summary** — "His first thought on getting out of bed—if he had any thought at all—was to get back in again." Use sparingly; frequent dashes give writing a breathless quality. 9. **The subject and verb must agree in number** — "The bittersweet flavor of youth—its trials, its joys, its adventures, its challenges—are not soon forgotten" is wrong; use "is." 10. **Use the proper case of pronoun** — "between you and I" is wrong; use "between you and me." In compound constructions, test each pronoun alone. 11. **A participial phrase at the beginning of a sentence must refer to the grammatical subject** — "Walking down the street, the trees were beautiful" is wrong (trees weren't walking). Fix: "Walking down the street, I noticed the beautiful trees." --- ## Summary **Grammar Accuracy**: [Clean/Minor Issues/Significant Errors] **Most Common Error Type**: [error category] **Corrections Needed**: 1. [Highest priority fix] 2. [Second priority] 3. [Third priority] ## Guidelines - Not all comma usage is covered by these rules—focus on the specific patterns described - Rule 2 (serial comma) is a style choice in some guides; Strunk & White advocate for it - Some fragments are intentional for effect in creative writing - Technical writing may have different conventions for colons and lists $ARGUMENTS
Related Skills
Fossil SCM Usage
This skill should be used when the user asks to "fossil commit", "fossil branch", "fossil merge", "fossil clone", "fossil sync", "fossil ticket", "fossil stash", "fossil timeline", mentions working with a Fossil repository, asks about Fossil vs Git differences, or needs help with Fossil SCM commands and workflows.
context7-usage
Patterns for using Context7 MCP for library documentation (v2.25)
comment-usage
This rule dictates how comments should be used within the codebase to enhance understanding and avoid clutter.
anthropic-usage
Check Anthropic API usage and costs for any time period. Use when the user asks about API costs, usage, spending, or billing for their Anthropic account. Supports natural language periods like "last week", "yesterday", "january 2025", specific dates, or date ranges.
alpine-js-usage-rules
Guidelines for using Alpine.js for declarative JavaScript functionality.
virtual-environment-usage
Mandates the use of virtual environments for isolating project dependencies and ensuring reproducibility.
ai-usage-coach
Help users get more value from AI assistants by suggesting better prompting techniques, surfacing underused features, and identifying workflow improvements. Use when users ask things like "how can I use Claude better?", "what features am I missing?", "give me tips for prompting", "what can you do?", "I feel like I'm not getting the most out of this", or when they explicitly ask for help improving their AI usage. Also use when users seem frustrated with results or are clearly using suboptimal patterns.
ffmpeg-usage
ffmpeg recipes and best practices: convert, concatenate, merge, resize, compress, GIF creation, audio extraction, subtitles, optimize for social platforms.
mongodb_usage
This skill should be used when user asks to "query MongoDB", "show database collections", "get collection schema", "list MongoDB databases", "search records in MongoDB", or "check database indexes".
openai-usage
Report current OpenAI usage/rate-limit health from Codex ChatGPT limits.
ai-usage
Check AI CLI usage/quota for Claude Code, OpenAI Codex, Google Gemini CLI, and Z.AI. Use when user asks about remaining quota, usage limits, rate limits, or wants to check how much capacity is left.
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.