Automated summary
This skill proofreads a text against Strunk & White's 11 elementary rules of usage from Chapter I of Elements of Style and returns a compliance table plus the specific errors it finds.
Strengths
- Walks through all 11 rules in a Pass / Needs Work / N/A table, making the review easy to scan
- Quotes each error with its location and offers a correction, often with more than one acceptable rewrite
- Includes a full rule reference section, so the review doubles as a learning aid
- Fixed output format makes results consistent across repeated reviews
Limitations
- Limited to Chapter I mechanics and punctuation — no guidance on style, concision, or word choice from later chapters
- Enforces Strunk & White conventions (serial comma, 's possessives) that may clash with a house style guide such as AP
- Quote and line-number accuracy depends on the model rather than a real parser
Use it for a final grammar and punctuation pass over an article, README, or documentation draft that is already written.
Skip it when you want style, tone, or structural advice, or when your style guide mandates different punctuation conventions.
Security analysis
SafeThe skill contains only text-analysis instructions for grammar review and declares no tools. It does not execute code, access files, make network calls, or handle secrets, so listing it presents no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Review drafts/seo-post.md against Strunk & White's 11 rules of usage. Fill in the compliance table and list every comma splice or sentence fragment with a suggested fix.Run the 11 Elements of Style usage rules over this README and flag any subject-verb agreement errors or dangling modifiers.Check this paragraph for punctuation and grammar errors using the Strunk & White rules: "The team shipped the release, it was a big milestone for everyone involved."name: eos-usage description: Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness. user-invocable: true
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
-
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).
-
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.
-
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.
-
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).
-
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."
-
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.
-
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."
-
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.
-
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."
-
Use the proper case of pronoun — "between you and I" is wrong; use "between you and me." In compound constructions, test each pronoun alone.
-
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:
- [Highest priority fix]
- [Second priority]
- [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
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 filesThis 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.mdFrom the root of a test project, save the file as .skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/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/elements-of-style-11-rules-of-usage-mrzxuq6i' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/elements-of-style-11-rules-of-usage-mrzxuq6i/download' --output '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md.part' && mv '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md.part' '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/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/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md' && test -s '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/eos-usage' && cp -R '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i' '.claude/skills/eos-usage'Cursor
test -f '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md' && test -s '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/eos-usage' && cp -R '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i' '.cursor/skills/eos-usage'Codex
test -f '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md' && test -s '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/eos-usage' && cp -R '.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i' '.agents/skills/eos-usage'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 installationopenskills install './.skill-downloads/elements-of-style-11-rules-of-usage-mrzxuq6i'openskills read 'elements-of-style-11-rules-of-usage-mrzxuq6i'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 syncManual 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/elements-of-style-11-rules-of-usage-mrzxuq6i/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.
Writing Fragments
Content
Mine raw writing fragments through a relentless interview, without imposing structure. Capture ideas, quotes, and leading words for later use.
UI Copywriting & Auditing
Content
Write or audit user-facing UI copy including buttons, errors, empty states, and tooltips across the monorepo, following the design system source of truth.
Music MIDI Extraction
Content
Extracts the MIDI or score from an existing music production via the CogMusic MCP tool and confirms availability.