mcpbeat Sign in

Eos Composition Agent Skill

Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
106
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/neurofoo/agent-skills --skill eos-composition

The instruction itself

12 sections, as written by the author

Elements of Style: 11 Composition Principles

Review writing against Strunk & White's 11 elementary principles of composition from Chapter II.

Instructions

Analyze the provided text for structural and compositional issues. Provide specific examples with before/after suggestions where improvements are needed.

Output Format

Text Under Review: [title or brief description]


Composition Review

| # | Principle | Status | Notes |

|---|-----------|--------|-------|

| 1 | Choose a suitable design and stick to it | Pass/Needs Work/N/A | [feedback] |

| 2 | Make the paragraph the unit of composition | Pass/Needs Work/N/A | [feedback] |

| 3 | Use the active voice | Pass/Needs Work/N/A | [feedback] |

| 4 | Put statements in positive form | Pass/Needs Work/N/A | [feedback] |

| 5 | Use definite, specific, concrete language | Pass/Needs Work/N/A | [feedback] |

| 6 | Omit needless words | Pass/Needs Work/N/A | [feedback] |

| 7 | Avoid a succession of loose sentences | Pass/Needs Work/N/A | [feedback] |

| 8 | Express coordinate ideas in parallel form | Pass/Needs Work/N/A | [feedback] |

| 9 | Keep related words together | Pass/Needs Work/N/A | [feedback] |

| 10 | In summaries, keep to one tense | Pass/Needs Work/N/A | [feedback] |

| 11 | Place the emphatic words at the end | Pass/Needs Work/N/A | [feedback] |


Detailed Findings

Principle 3: Active Voice

Passive voice found:

| Original | Suggested |

|----------|-----------|

| [passive construction] | [active alternative] |

Principle 4: Positive Form

Negative constructions found:

| Original | Suggested |

|----------|-----------|

| "He was not very often on time" | "He usually arrived late" |

Principle 6: Omit Needless Words

Wordy phrases found:

| Original | Suggested |

|----------|-----------|

| "the reason why is that" | "because" |

| "in spite of the fact that" | "although" |

| "the fact that he had arrived" | "his arrival" |

Principle 8: Parallel Form

Non-parallel constructions:

| Original | Suggested |

|----------|-----------|

| [non-parallel] | [parallel version] |


Principle Reference

  • Choose a suitable design and stick to it — Plan your structure. Know whether you're building a tent or a cathedral. The design may change, but have one.
  • Make the paragraph the unit of composition — Each paragraph should develop one topic. Begin with a topic sentence; end with emphasis. Don't chop into single sentences or let paragraphs run too long.
  • Use the active voice — "The active voice is usually more direct and vigorous than the passive." Write "I shall always remember my first visit" not "My first visit will always be remembered by me."
  • Put statements in positive form — Say what is, not what isn't. "He usually came late" is stronger than "He was not very often on time." Avoid not un- constructions.
  • Use definite, specific, concrete language — Prefer the specific to the general, the definite to the vague, the concrete to the abstract. "A period of unfavorable weather set in" → "It rained every day for a week."
  • Omit needless words — "Vigorous writing is concise." Every word should tell. Common offenders:
  • "the question as to whether" → "whether"
  • "there is no doubt but that" → "no doubt" / "doubtless"
  • "the fact that" → often deletable
  • "who is" / "which was" → often deletable
  • Avoid a succession of loose sentences — Don't string together clauses with "and," "but," "so." Vary sentence structure. Use subordination.
  • Express coordinate ideas in parallel form — Similar content deserves similar form. "The French, the Italians, Spanish, and Portuguese" → "The French, the Italians, the Spanish, and the Portuguese."
  • Keep related words together — Place modifiers near what they modify. "He only found two mistakes" → "He found only two mistakes."

10. In summaries, keep to one tense — When summarizing a work, use present tense throughout. Don't shift between present and past.

11. Place the emphatic words at the end — The end of a sentence is its most prominent position. Build toward the key word. "Humanity has hardly advanced in fortitude since that time, though it has advanced in many other ways" → weak ending. Revise for emphasis.


Summary

Overall Structure: [Well-organized/Needs Work/Disorganized]

Word Economy: [Tight/Some bloat/Verbose]

Top 3 Improvements:

  • [Most impactful structural change]
  • [Second priority]
  • [Third priority]

Guidelines

  • Focus on patterns rather than isolated instances
  • Active voice isn't always better—passive is appropriate when the actor is unknown or unimportant
  • "Omit needless words" doesn't mean "omit all words"—rhythm and clarity sometimes need extra words
  • Technical writing may legitimately need longer explanations

$ARGUMENTS

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Writing Plans
by ZhanlinCui
×4

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Crafting Effective Readmes
by softaworks
×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

15k tokens
Humanizer
by softaworks
×3

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

6k tokens
Opentrons Integration
by christophacham
×3

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

9k tokens scripts

How to use it

Copy the folder

Take neurofoo/eos-composition from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.