Token导航 LogoToken导航

Agent Skill · 研究检索

eos-composition(EOS 组成)

eos-composition 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

eos-composition 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 53,170。

总安装 539周安装 22GitHub Stars 68下载 172核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:eos-composition(EOS 组成)
来源仓库:https://github.com/neurofoo/agent-skills
仓库路径:skills/eos-composition
安装命令:
npx skills add https://github.com/neurofoo/agent-skills --skill eos-composition
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/neurofoo/agent-skills --skill eos-composition

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

总体结构:[组织良好/需要工作/杂乱] 词经济:[紧/有些臃肿/冗长] 三大改进: [最具影响力的结构性变革] [第二优先] [第三优先] 指南 关注模式而不是孤立的实例 主动语态并不总是更好——当演员不知名或不重要时,被动语态才是合适的 “省略不必要的词语”并不意味着“省略所有词语”——节奏和清晰度有时需要额外的词语 技术写作可能需要更长的解释 $参数 每周安装量 22 存储库 Neurofoo/Agent Skill GitHub 之星 68 第一次看到 2天前 安全审计 Gen Agent Trust Hub 通行证 套接字通行证 斯尼克通行证

来源仓库内路径:skills/eos-composition

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/neurofoo/agent-skills --skill eos-composition;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

eos-composition 怎么安装?

在终端执行 npx skills add https://github.com/neurofoo/agent-skills --skill eos-composition。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

eos-composition 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

eos-composition 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

eos-composition 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

eos-composition 用的人多吗?

公开数据是累计安装 539 次,近一周安装 22 次,下载 172 次,GitHub 68 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

eos-composition 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
eos-composition

EOS 组成 · 本页

53968只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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

#PrincipleStatusNotes
1Choose a suitable design and stick to itPass/Needs Work/N/A[feedback]
2Make the paragraph the unit of compositionPass/Needs Work/N/A[feedback]
3Use the active voicePass/Needs Work/N/A[feedback]
4Put statements in positive formPass/Needs Work/N/A[feedback]
5Use definite, specific, concrete languagePass/Needs Work/N/A[feedback]
6Omit needless wordsPass/Needs Work/N/A[feedback]
7Avoid a succession of loose sentencesPass/Needs Work/N/A[feedback]
8Express coordinate ideas in parallel formPass/Needs Work/N/A[feedback]
9Keep related words togetherPass/Needs Work/N/A[feedback]
10In summaries, keep to one tensePass/Needs Work/N/A[feedback]
11Place the emphatic words at the endPass/Needs Work/N/A[feedback]

Detailed Findings

Principle 3: Active Voice

Passive voice found:

OriginalSuggested
[passive construction][active alternative]

Principle 4: Positive Form

Negative constructions found:

OriginalSuggested
"He was not very often on time""He usually arrived late"

Principle 6: Omit Needless Words

Wordy phrases found:

OriginalSuggested
"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:

OriginalSuggested
[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

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

平台分布

Claude Code

26.38%
按下载量换算45

windsurf

20.78%
按下载量换算36

Antigravity

16.63%
按下载量换算29

trae

12.71%
按下载量换算22

OpenCode

7.97%
按下载量换算14

Gemini CLI

3.59%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills