eos-composition
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Best use case
eos-composition is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Teams using eos-composition should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/eos-composition/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How eos-composition Compares
| Feature / Agent | eos-composition | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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. 2. **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. 3. **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." 4. **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. 5. **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." 6. **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 7. **Avoid a succession of loose sentences** — Don't string together clauses with "and," "but," "so." Vary sentence structure. Use subordination. 8. **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." 9. **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**: 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
Related Skills
team-composition-analysis
This skill should be used when the user asks to \\\"plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests...
memory-forensics
Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating inciden...
malware-analyst
Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification.
loki-mode
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations,...
llm-security
LLM and AI application security testing skill for prompt injection, jailbreaking, and AI system vulnerabilities. This skill should be used when testing AI/ML applications for security issues, performing prompt injection attacks, testing LLM guardrails, analyzing AI system architectures for vulnerabilities, or assessing RAG pipeline security. Triggers on requests to test LLM security, perform prompt injection, jailbreak AI systems, test AI guardrails, or audit AI application security.
linux-privilege-escalation
This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "ex...
libfuzzer
Coverage-guided fuzzer built into LLVM for C/C++ projects. Use for fuzzing C/C++ code that can be compiled with Clang.
libafl
LibAFL is a modular fuzzing library for building custom fuzzers. Use for advanced fuzzing needs, custom mutators, or non-standard fuzzing targets.
laravel-security-audit
Security auditor for Laravel applications. Analyzes code for vulnerabilities, misconfigurations, and insecure practices using OWASP standards and Laravel security best practices.
k8s-security-policies
Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or ...
insecure-defaults
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.
influence-psychology
Apply the six principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users don't convert", or "ethical persuasion". For deal negotiation tactics, see negotiation. For viral word-of-mouth, see contagious.