Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
npx skills add https://github.com/neurofoo/agent-skills --skill eos-composition
Review writing against Strunk & White's 11 elementary principles of composition from Chapter II.
Analyze the provided text for structural and compositional issues. Provide specific examples with before/after suggestions where improvements are needed.
Text Under Review: [title or brief description]
| # | 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] |
Passive voice found:
| Original | Suggested |
|----------|-----------|
| [passive construction] | [active alternative] |
Negative constructions found:
| Original | Suggested |
|----------|-----------|
| "He was not very often on time" | "He usually arrived late" |
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" |
Non-parallel constructions:
| Original | Suggested |
|----------|-----------|
| [non-parallel] | [parallel version] |
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.
Overall Structure: [Well-organized/Needs Work/Disorganized]
Word Economy: [Tight/Some bloat/Verbose]
Top 3 Improvements:
$ARGUMENTS
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.
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.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| 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.
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.
Take neurofoo/eos-composition from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.