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.

23 stars

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

$curl -o ~/.claude/skills/eos-usage/SKILL.md --create-dirs "https://raw.githubusercontent.com/christophacham/agent-skills-library/main/skills/game-dev/eos-usage/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/eos-usage/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How eos-usage Compares

Feature / Agenteos-usageStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/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

copilot-usage-metrics

23
from christophacham/agent-skills-library

Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.

repo-story-time

23
from christophacham/agent-skills-library

Generate a comprehensive repository summary and narrative story from commit history

release-notes

23
from christophacham/agent-skills-library

Generates structured release notes from git history between two references (tags, commits, branches). Groups changes by type (features, fixes, docs, breaking), extracts PR references, and produces a publish-ready document.

release-it

23
from christophacham/agent-skills-library

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "timeout strategy", "deployment pipeline", or "chaos engineering". Covers capacity planning, health checks, and anti-fragility patterns. For data systems, see ddia-systems. For system architecture, see system-design.

pyzotero

23
from christophacham/agent-skills-library

Interact with Zotero reference management libraries using the pyzotero Python client. Retrieve, create, update, and delete items, collections, tags, and attachments via the Zotero Web API v3. Use this skill when working with Zotero libraries programmatically, managing bibliographic references, exporting citations, searching library contents, uploading PDF attachments, or building research automation workflows that integrate with Zotero.

pydicom

23
from christophacham/agent-skills-library

Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.

pr-ready

23
from christophacham/agent-skills-library

Prepares a feature branch for pull request. Runs all checks, generates PR description, verifies documentation is updated, creates changelog entry, and suggests labels.

perf-theory-gatherer

23
from christophacham/agent-skills-library

Use when generating performance hypotheses backed by git history and code evidence.

open-source-maintainer

23
from christophacham/agent-skills-library

End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.

git:notes

23
from christophacham/agent-skills-library

Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.

my-pull-requests

23
from christophacham/agent-skills-library

List my pull requests in the current repository

multi-stage-dockerfile

23
from christophacham/agent-skills-library

Create optimized multi-stage Dockerfiles for any language or framework