Grammar and Flow Checker
phuryn/pm-skills
Reviews a draft for grammar, logic and flow problems and returns located, prioritized fix suggestions without rewriting the whole text.
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I.
MITAuto-check passed
Install Eos Usage
$ npx skills add neurofoo/agent-skills --skill eos-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install neurofoo/agent-skills eos-usage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/eos-usage .claude/skills/eos-usage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "eos-usage" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-usage into .claude/skills/eos-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-usage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/neurofoo/agent-skills/tree/main/eos-usageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add neurofoo/agent-skills --skill eos-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install neurofoo/agent-skills eos-usage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/eos-usage .agents/skills/eos-usage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eos-usage" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-usage into .agents/skills/eos-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-usage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add neurofoo/agent-skills --skill eos-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install neurofoo/agent-skills eos-usage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/eos-usage .cursor/skills/eos-usage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "eos-usage" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-usage into .cursor/skills/eos-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-usage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/neurofoo/agent-skills.git --path eos-usage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add neurofoo/agent-skills --skill eos-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install neurofoo/agent-skills eos-usage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/eos-usage .gemini/skills/eos-usage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "eos-usage" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-usage into .gemini/skills/eos-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-usage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install neurofoo/agent-skills eos-usageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add neurofoo/agent-skills --skill eos-usage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/eos-usage .github/skills/eos-usage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "eos-usage" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-usage into .github/skills/eos-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-usage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add neurofoo/agent-skills --skill eos-usage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install neurofoo/agent-skills eos-usage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/eos-usage .opencode/skills/eos-usage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "eos-usage" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-usage into .opencode/skills/eos-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-usage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
eos-usage- GitHub stars
- 119
- Token cost
- ~1.2k tokens
- SKILL.md length
- 647 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I.
- Works in 11 steps: Form the possessive singular by adding… → In a series of three or more, use a… → Enclose parenthetic expressions between… → …
- Checking mechanics
- SKILL.md covers Instructions, Usage Review, Errors Found and Rule Reference, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Eos Usage is an agent skill from neurofoo/agent-skills. Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Agent Skills for Claude Code and OpenCode. The licence is MIT.
When your agent uses it
- Checking mechanics
- Grammatical correctness
Example prompts
- “Elements of Style”
- “/eos-usage”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- Form the possessive singular by adding 's — Charles's friend, Burns's poems, the witch's malice. Exceptions: ancient proper names ending…
- 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."…
- Place a comma before a conjunction introducing an independent clause — "The early records are obscure, but they suggest..." This rule…
- 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…
- 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…
- Use a colon after an independent clause to introduce a list, appositive, amplification, or illustrative quotation — "The situation is…
- 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…
- The subject and verb must agree in number — "The bittersweet flavor of youth—its trials, its joys, its adventures, its challenges—are not…
- 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…
What it can do on your machine
Read from SKILL.md and the folder at commit 0e7ac2a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Eos Usage loads about 1.2k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 647 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from neurofoo/agent-skills at commit 0e7ac2a, republished under its MIT licence (© neurofoo). 647 words, ~1,215 tokens.
Download SKILL.mdSave it as
.claude/skills/eos-usage/SKILL.md (or your agent's skills folder).- 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."
Show full SKILL.md (75 more words)Show less
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
© neurofoo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in eos-usage of neurofoo/agent-skills.
Open the folder on GitHubat commit 0e7ac2a
Compare with similar skills
Eos Usage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Eos Usage this skillneurofoo/agent-skills | 119 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Grammar and Flow Checkerphuryn/pm-skills | 27k | — | ~2.4k | Automated safety check: Pass | MIT | |
| HTML Ppt Xhs White Editorialnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Add Grammarafnanenayet/diffsitter | 2.4k | — | ~1.9k | Automated safety check: Notes | MIT | |
| Traction Eoswondelai/skills | 2.4k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Grammarly Access Readinessjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
HTML Ppt Xhs White Editorial
nexu-io/open-design
A staff-engineer promotion packet — scope, the proof moments, the artifacts, and the impact that clears the bar.
Add Grammar
afnanenayet/diffsitter
Step-by-step guide for adding a new tree-sitter language grammar to diffsitter.
Traction Eos
wondelai/skills
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company.
Grammarly Access Readiness
jeremylongshore/tons-of-skills-marketplace
Audit a Grammarly API OAuth configuration offline for recognized organization access, least-privilege scopes, and documented API coverage.
Grammarly API Reliability
jeremylongshore/tons-of-skills-marketplace
Analyze a sanitized Grammarly asynchronous job receipt without sending requests, reading document content, or guessing provider SLAs.
More from neurofoo/agent-skills
All 22 skills in this repoFive Whys Analysis
neurofoo/agent-skills
Runs a Five Whys root cause analysis, asking why repeatedly from the stated problem until it reaches an actionable cause, then lists corrective actions and verification.
Eisenhower Matrix Prioritizer
neurofoo/agent-skills
Sorts a task list into the four Eisenhower quadrants (do, schedule, delegate, eliminate) with reasons, a time distribution check and first actions.
OODA Loop Analysis
neurofoo/agent-skills
Walks a problem or decision through the OODA loop: observe the facts, orient on causes and assumptions, decide among at least three options, and plan the execution.
Cynefin Problem Classifier
neurofoo/agent-skills
Sorts a problem into the Cynefin domains of simple, complicated, complex, chaotic or confused, then recommends a way of working that fits that domain.
Wardley Map Analysis
neurofoo/agent-skills
Maps a user need's value chain against evolution stages to guide build-versus-buy decisions and show competitive dynamics.
Jtbd
neurofoo/agent-skills
Jobs to Be Done analysis to understand what customers really want.
Questions about Eos Usage
What does Eos Usage do?
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Eos Usage is an agent skill from neurofoo/agent-skills. Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I.
When should I use Eos Usage?
Eos Usage fits situations like: checking mechanics; grammatical correctness.
How do I install Eos Usage in Claude Code?
Run `npx skills add neurofoo/agent-skills --skill eos-usage -a claude-code`. Or copy the skill folder (eos-usage in neurofoo/agent-skills) into .claude/skills/eos-usage in your project. Claude Code loads it when a task matches its description.
How do I install Eos Usage in Codex?
Run `npx skills add neurofoo/agent-skills --skill eos-usage -a codex`. Or copy the skill folder (eos-usage in neurofoo/agent-skills) into .agents/skills/eos-usage in your project. Codex loads it when a task matches its description.
Can I use Eos Usage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add neurofoo/agent-skills --skill eos-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eos-usage, .gemini/skills/eos-usage, .github/skills/eos-usage and .opencode/skills/eos-usage in your project.
What does Eos Usage need to run?
SKILL.md names no scripts, command-line tools or credentials: Eos Usage is instructions for the agent only.
Does Eos Usage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Eos Usage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Eos Usage use?
Eos Usage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Eos Usage use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Eos Usage?
Skills that share tags, products or a category with Eos Usage: Grammar and Flow Checker (phuryn/pm-skills, 27k stars), HTML Ppt Xhs White Editorial (nexu-io/open-design, 100k stars), Add Grammar (afnanenayet/diffsitter, 2.4k stars) and Traction Eos (wondelai/skills, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eos Usage?
neurofoo (a GitHub user) maintains it in neurofoo/agent-skills, which has 119 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on January 19, 2026.
Source: neurofoo/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.