AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Eos Composition

skill-neurofoo-agent-skills-eos-composition · by neurofoo

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

No reviews yet
0 installs
42 views
0.0% view→install

Install

$ agentstack add skill-neurofoo-agent-skills-eos-composition

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-neurofoo-agent-skills-eos-composition)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
8mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Eos Composition? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

  1. 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.
  1. 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.
  1. 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."
  1. 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.
  1. 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."
  1. 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
  1. Avoid a succession of loose sentences — Don't string together clauses with "and," "but," "so." Vary sentence structure. Use subordination.
  1. 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."
  1. Keep related words together — Place modifiers near what they modify. "He only found two mistakes" → "He found only two mistakes."
  1. In summaries, keep to one tense — When summarizing a work, use present tense throughout. Don't shift between present and past.
  1. 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.