Principle Redesign From First Principles
cursor/plugins
Apply when integrating a new requirement into an existing design.
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II.
MITAuto-check passed
Install Eos Composition
$ npx skills add neurofoo/agent-skills --skill eos-composition -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install neurofoo/agent-skills eos-composition --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/eos-composition .claude/skills/eos-composition && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "eos-composition" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-composition into .claude/skills/eos-composition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-composition", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/neurofoo/agent-skills/tree/main/eos-compositionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add neurofoo/agent-skills --skill eos-composition -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install neurofoo/agent-skills eos-composition --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/eos-composition .agents/skills/eos-composition && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "eos-composition" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-composition into .agents/skills/eos-composition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-composition", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add neurofoo/agent-skills --skill eos-composition -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install neurofoo/agent-skills eos-composition --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/eos-composition .cursor/skills/eos-composition && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "eos-composition" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-composition into .cursor/skills/eos-composition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-composition", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/neurofoo/agent-skills.git --path eos-composition--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add neurofoo/agent-skills --skill eos-composition -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install neurofoo/agent-skills eos-composition --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/eos-composition .gemini/skills/eos-composition && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "eos-composition" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-composition into .gemini/skills/eos-composition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-composition", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install neurofoo/agent-skills eos-compositionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add neurofoo/agent-skills --skill eos-composition -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/eos-composition .github/skills/eos-composition && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "eos-composition" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-composition into .github/skills/eos-composition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-composition", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add neurofoo/agent-skills --skill eos-composition -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install neurofoo/agent-skills eos-composition --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neurofoo/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/eos-composition .opencode/skills/eos-composition && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "eos-composition" agent skill from https://github.com/neurofoo/agent-skills/tree/main/eos-composition into .opencode/skills/eos-composition/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "eos-composition", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
eos-composition- GitHub stars
- 119
- Token cost
- ~1.3k tokens
- SKILL.md length
- 641 words
- Files
- 1
- Skills in repo
- 22
- Repo updated
- First seen
- Licence
- MIT
At a glance
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II.
- Works in 11 steps: Choose a suitable design and stick to it… → Make the paragraph the unit of… → Use the active voice — "The active voice… → …
- Analyzing structure
- SKILL.md covers Instructions, Composition Review, Detailed Findings and Principle Reference, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Eos Composition is an agent skill from neurofoo/agent-skills. Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Use when analyzing structure, improving flow, or tightening prose.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Agent Skills for Claude Code and OpenCode. The licence is MIT.
When your agent uses it
- Analyzing structure
- Tightening prose
Example prompts
- “Elements of Style”
- “/eos-composition”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- 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…
- Make the paragraph the unit of composition — Each paragraph should develop one topic. Begin with a topic sentence; end with emphasis…
- Use the active voice — "The active voice is usually more direct and vigorous than the passive." Write "I shall always remember my first…
- 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."…
- Use definite, specific, concrete language — Prefer the specific to the general, the definite to the vague, the concrete to the abstract…
- Omit needless words — "Vigorous writing is concise." Every word should tell. Common offenders
- 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" →…
- 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…
What it can do on your machine
Read from SKILL.md and the folder at commit 0e7ac2a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Eos Composition loads about 1.3k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 641 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from neurofoo/agent-skills at commit 0e7ac2a, republished under its MIT licence (© neurofoo). 641 words, ~1,274 tokens.
Download SKILL.mdSave it as
.claude/skills/eos-composition/SKILL.md (or your agent's skills folder).- 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.
Show full SKILL.md (67 more words)Show less
Summary
Overall Structure: [Well-organized/Needs Work/Disorganized]
Word Economy: [Tight/Some bloat/Verbose]
Top 3 Improvements:
- [Most impactful structural change]
- [Second priority]
- [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
© neurofoo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in eos-composition of neurofoo/agent-skills.
Open the folder on GitHubat commit 0e7ac2a
Compare with similar skills
Eos Composition next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Eos Composition this skillneurofoo/agent-skills | 119 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Principle Redesign From First Principlescursor/plugins | 10k | 8 repos | ~211 | Automated safety check: Pass | None | |
| Decorative Elementsthedaviddias/Front-End-Checklist | 74k | — | ~672 | Automated safety check: Pass | MIT | |
| Scaffold Elementremotion-dev/remotion | 62k | — | ~202 | Automated safety check: Pass | Custom licence | |
| Composition Patternssickn33/agentic-awesome-skills | 47k | 1 repos | ~742 | Automated safety check: Pass | MIT | |
| Uxui Principlessickn33/agentic-awesome-skills | 47k | 2 repos | ~548 | Automated safety check: Pass | MIT |
Similar skills
- Official
Decorative Elements
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Hide decorative elements from assistive technology.
- Official
Scaffold Element
remotion-dev/remotion
Scaffold a new Remotion Element for development in the docs Remotion Studio.
Composition Patterns
sickn33/agentic-awesome-skills
A skill your agent uses when working with composition-patterns tasks or workflows
Uxui Principles
sickn33/agentic-awesome-skills
Evaluate interfaces against 168 research-backed UX/UI principles, detect antipatterns, and inject UX context into AI coding sessions.
Html5 Semantic Elements
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements.
More from neurofoo/agent-skills
All 22 skills in this repoFive Whys Analysis
neurofoo/agent-skills
Runs a Five Whys root cause analysis, asking why repeatedly from the stated problem until it reaches an actionable cause, then lists corrective actions and verification.
Eisenhower Matrix Prioritizer
neurofoo/agent-skills
Sorts a task list into the four Eisenhower quadrants (do, schedule, delegate, eliminate) with reasons, a time distribution check and first actions.
OODA Loop Analysis
neurofoo/agent-skills
Walks a problem or decision through the OODA loop: observe the facts, orient on causes and assumptions, decide among at least three options, and plan the execution.
Cynefin Problem Classifier
neurofoo/agent-skills
Sorts a problem into the Cynefin domains of simple, complicated, complex, chaotic or confused, then recommends a way of working that fits that domain.
Wardley Map Analysis
neurofoo/agent-skills
Maps a user need's value chain against evolution stages to guide build-versus-buy decisions and show competitive dynamics.
Jtbd
neurofoo/agent-skills
Jobs to Be Done analysis to understand what customers really want.
Questions about Eos Composition
What does Eos Composition do?
Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II. Eos Composition is an agent skill from neurofoo/agent-skills. Strunk & White composition review using the 11 principles from "Elements of Style" Chapter II.
When should I use Eos Composition?
Eos Composition fits situations like: analyzing structure; tightening prose.
How do I install Eos Composition in Claude Code?
Run `npx skills add neurofoo/agent-skills --skill eos-composition -a claude-code`. Or copy the skill folder (eos-composition in neurofoo/agent-skills) into .claude/skills/eos-composition in your project. Claude Code loads it when a task matches its description.
How do I install Eos Composition in Codex?
Run `npx skills add neurofoo/agent-skills --skill eos-composition -a codex`. Or copy the skill folder (eos-composition in neurofoo/agent-skills) into .agents/skills/eos-composition in your project. Codex loads it when a task matches its description.
Can I use Eos Composition in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add neurofoo/agent-skills --skill eos-composition -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eos-composition, .gemini/skills/eos-composition, .github/skills/eos-composition and .opencode/skills/eos-composition in your project.
What does Eos Composition need to run?
SKILL.md names no scripts, command-line tools or credentials: Eos Composition is instructions for the agent only.
Does Eos Composition access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Eos Composition safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Eos Composition use?
Eos Composition is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Eos Composition use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Eos Composition?
Skills that share tags, products or a category with Eos Composition: Principle Redesign From First Principles (cursor/plugins, 10k stars), Decorative Elements (thedaviddias/Front-End-Checklist, 74k stars), Scaffold Element (remotion-dev/remotion, 62k stars) and Composition Patterns (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Eos Composition?
neurofoo (a GitHub user) maintains it in neurofoo/agent-skills, which has 119 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on January 19, 2026.
Source: neurofoo/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.