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

Eos Style

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

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.

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

Install

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

✓ 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-style)

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 Style? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

  1. Place yourself in the background — Write to serve the reader, not to show off. Style emerges from content, not from the writer's ego.
  1. Write naturally — Don't consciously imitate others or force an affected style. Write as you would speak to an intelligent friend.
  1. Work from suitable design — Plan your piece. Know your scope and structure before writing extensively.
  1. Write with nouns and verbs — These give writing strength. Adjectives and adverbs are not your principal weapons.
  1. Revise and rewrite — Good writing is rewriting. Don't expect first drafts to be final.
  1. Don't overwrite — Avoid ornate, flowery prose. Rich prose is hard to digest.
  1. Don't overstate — Avoid superlatives and exaggeration. A single overstatement can undermine your credibility.
  1. Avoid qualifiers — Words like "very," "rather," "quite," "pretty," and "little" weaken prose.
  1. Don't affect breeziness — Forced casualness and flip remarks suggest the writer values cleverness over substance.
  1. Use orthodox spelling — Follow standard conventions unless you have good reason not to.
  1. Don't explain too much — Trust the reader. Avoid excessive adverbs after "said" and over-explanatory dialogue tags.
  1. Don't construct awkward adverbs — Avoid forcing "-ly" onto words that don't take it naturally.
  1. Make sure speakers are clear — In dialogue, readers must always know who is speaking.
  1. Avoid fancy words — Prefer the plain word to the fancy one. "Home" not "domicile."
  1. Use dialect sparingly — The best dialect writers use minimal deviation from standard language.
  1. Be clear — Clarity is the foundation. Muddiness is not depth; obscurity is not profundity.
  1. Don't inject opinion — Keep personal opinions out unless they serve the work. They mark the egoist.
  1. Use figures of speech sparingly — Metaphors and similes need space. Constant comparison exhausts the reader.
  1. Don't sacrifice clarity for shortcuts — Strong, precise words are better than clever abbreviations.
  1. Avoid foreign languages — Write in English. Foreign phrases can seem pretentious.
  1. Prefer standard to offbeat — Choose established words over trendy or invented ones.

Summary

Overall Assessment: [Strong/Needs Revision/Major Issues]

Top 3 Improvements:

  1. [Most impactful change]
  2. [Second priority]
  3. [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

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.