Reminders
steipete/agent-scripts
Apple Reminders via rem CLI: add, list, search, update, complete, delete.
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V.
MITAuto-check passed
Install Eos Style
$ npx skills add neurofoo/agent-skills --skill eos-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install neurofoo/agent-skills eos-style --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-style .claude/skills/eos-style && 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-style" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-style into .claude/skills/eos-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-style", 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-styleType 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-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install neurofoo/agent-skills eos-style --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-style .agents/skills/eos-style && 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-style" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-style into .agents/skills/eos-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-style", 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-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install neurofoo/agent-skills eos-style --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-style .cursor/skills/eos-style && 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-style" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-style into .cursor/skills/eos-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-style", 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-style--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-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install neurofoo/agent-skills eos-style --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-style .gemini/skills/eos-style && 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-style" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-style into .gemini/skills/eos-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-style", 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-styleInstalls 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-style -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-style .github/skills/eos-style && 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-style" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-style into .github/skills/eos-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-style", 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-style -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-style --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-style .opencode/skills/eos-style && 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-style" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-style into .opencode/skills/eos-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-style", 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-style- GitHub stars
- 119
- Token cost
- ~1.3k tokens
- SKILL.md length
- 660 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V.
- Works in 12 steps: Place yourself in the background — Write… → Write naturally — Don't consciously… → Work from suitable design — Plan your… → …
- Reviewing drafts
- SKILL.md covers Instructions, Style Review, Key Issues Found and Principle Reference, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Eos Style is an agent skill from neurofoo/agent-skills. 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.
Its SKILL.md is about 1.3k 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
- Reviewing drafts
- Improving writing clarity and tone
Example prompts
- “Elements of Style”
- “/eos-style”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Place yourself in the background — Write to serve the reader, not to show off. Style emerges from content, not from the writer's ego.
- Write naturally — Don't consciously imitate others or force an affected style. Write as you would speak to an intelligent friend.
- Work from suitable design — Plan your piece. Know your scope and structure before writing extensively.
- Write with nouns and verbs — These give writing strength. Adjectives and adverbs are not your principal weapons.
- Revise and rewrite — Good writing is rewriting. Don't expect first drafts to be final.
- Don't overwrite — Avoid ornate, flowery prose. Rich prose is hard to digest.
- Don't overstate — Avoid superlatives and exaggeration. A single overstatement can undermine your credibility.
- Avoid qualifiers — Words like "very," "rather," "quite," "pretty," and "little" weaken prose.
- Don't affect breeziness — Forced casualness and flip remarks suggest the writer values cleverness over substance.
- Use orthodox spelling — Follow standard conventions unless you have good reason not to.
- Don't explain too much — Trust the reader. Avoid excessive adverbs after "said" and over-explanatory dialogue tags.
- Don't construct awkward adverbs — Avoid forcing "-ly" onto words that don't take it naturally.
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 Style loads about 1.3k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 660 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). 660 words, ~1,333 tokens.
Download SKILL.mdSave it as
.claude/skills/eos-style/SKILL.md (or your agent's skills folder).- name
- eos-style
- description
- 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.
- user-invocable
- true
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
Place yourself in the background — Write to serve the reader, not to show off. Style emerges from content, not from the writer's ego.
Write naturally — Don't consciously imitate others or force an affected style. Write as you would speak to an intelligent friend.
Work from suitable design — Plan your piece. Know your scope and structure before writing extensively.
Write with nouns and verbs — These give writing strength. Adjectives and adverbs are not your principal weapons.
Revise and rewrite — Good writing is rewriting. Don't expect first drafts to be final.
Don't overwrite — Avoid ornate, flowery prose. Rich prose is hard to digest.
Don't overstate — Avoid superlatives and exaggeration. A single overstatement can undermine your credibility.
Avoid qualifiers — Words like "very," "rather," "quite," "pretty," and "little" weaken prose.
Don't affect breeziness — Forced casualness and flip remarks suggest the writer values cleverness over substance.
Use orthodox spelling — Follow standard conventions unless you have good reason not to.
Don't explain too much — Trust the reader. Avoid excessive adverbs after "said" and over-explanatory dialogue tags.
Don't construct awkward adverbs — Avoid forcing "-ly" onto words that don't take it naturally.
Make sure speakers are clear — In dialogue, readers must always know who is speaking.
Avoid fancy words — Prefer the plain word to the fancy one. "Home" not "domicile."
Use dialect sparingly — The best dialect writers use minimal deviation from standard language.
Be clear — Clarity is the foundation. Muddiness is not depth; obscurity is not profundity.
Don't inject opinion — Keep personal opinions out unless they serve the work. They mark the egoist.
Use figures of speech sparingly — Metaphors and similes need space. Constant comparison exhausts the reader.
Don't sacrifice clarity for shortcuts — Strong, precise words are better than clever abbreviations.
Avoid foreign languages — Write in English. Foreign phrases can seem pretentious.
Prefer standard to offbeat — Choose established words over trendy or invented ones.
Show full SKILL.md (66 more words)Show less
Summary
Overall Assessment: [Strong/Needs Revision/Major Issues]
Top 3 Improvements:
- [Most impactful change]
- [Second priority]
- [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
© 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-style of neurofoo/agent-skills.
Open the folder on GitHubat commit 0e7ac2a
Compare with similar skills
Eos Style 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 Style this skillneurofoo/agent-skills | 119 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Reminderssteipete/agent-scripts | 7.3k | — | ~661 | Automated safety check: Pass | MIT | |
| Decorative Elementsthedaviddias/Front-End-Checklist | 74k | — | ~672 | Automated safety check: Pass | MIT | |
| Scaffold Elementremotion-dev/remotion | 62k | — | ~202 | Automated safety check: Pass | Custom licence | |
| Reminddavidondrej/skills | 4.1k | — | ~266 | Automated safety check: Pass | MIT | |
| Html5 Semantic Elementsthedaviddias/Front-End-Checklist | 74k | — | ~449 | Automated safety check: Pass | MIT |
Similar skills
Decorative Elements
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Hide decorative elements from assistive technology.
- Official
Scaffold Element
remotion-dev/remotion
Scaffold a new Remotion Element for development in the docs Remotion Studio.
Remind
davidondrej/skills
Rewrite the last response simpler and shorter in plain English, prefixed with a 3-5 sentence TLDR of the conversation so far.
Html5 Semantic Elements
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements.
Custom Element Accessibility
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing custom element class definitions or Web Component source code to check for missing ARIA reflection, keyboard handling, and form association.
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 Style
What does Eos Style do?
Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V. Eos Style is an agent skill from neurofoo/agent-skills. Strunk & White style review using the 21 reminders from "Elements of Style" Chapter V.
When should I use Eos Style?
Eos Style fits situations like: reviewing drafts; improving writing clarity and tone.
How do I install Eos Style in Claude Code?
Run `npx skills add neurofoo/agent-skills --skill eos-style -a claude-code`. Or copy the skill folder (eos-style in neurofoo/agent-skills) into .claude/skills/eos-style in your project. Claude Code loads it when a task matches its description.
How do I install Eos Style in Codex?
Run `npx skills add neurofoo/agent-skills --skill eos-style -a codex`. Or copy the skill folder (eos-style in neurofoo/agent-skills) into .agents/skills/eos-style in your project. Codex loads it when a task matches its description.
Can I use Eos Style 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-style -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-style, .gemini/skills/eos-style, .github/skills/eos-style and .opencode/skills/eos-style in your project.
What does Eos Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Eos Style is instructions for the agent only.
Does Eos Style 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 Style 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 Style use?
Eos Style 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 Style use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Style?
Skills that share tags, products or a category with Eos Style: Reminders (steipete/agent-scripts, 7.3k stars), Decorative Elements (thedaviddias/Front-End-Checklist, 74k stars), Scaffold Element (remotion-dev/remotion, 62k stars) and Remind (davidondrej/skills, 4.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eos Style?
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.