Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes...
npx skills add neurofoo/agent-skills --skill "eos-composition"
Install specific skill from multi-skill repository
# Description
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
# SKILL.md
name: eos-composition
description: Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
user-invocable: true
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."
-
In summaries, keep to one tense โ When summarizing a work, use present tense throughout. Don't shift between present and past.
-
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:
1. [Most impactful structural change]
2. [Second priority]
3. [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
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.