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.
What this skill does
# 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 in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.