Token导航 LogoToken导航

Agent Skill · AI 工具

eos-style(EOS 风格)

eos-style 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

eos-style 是AI 工具类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在AI 工具类的 2,536 个 Skill 里排第 1,424。

总安装 729周安装 31GitHub Stars 68下载 255核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

AI 工具类 Skill 用来扩展助手本身的能力,例如接模型、接检索、接外部服务。

总体评价:[强/需要修改/主要问题] 三大改进: [最具影响力的改变] [第二优先] [第三优先] 指南 关注模式,而不是孤立的实例 为了达到效果,某些规则可能会被故意打破——请注意,这似乎是故意的 “需要改进”是指一种违规行为,而不是单一实例 技术或专业写作可以合法使用术语 创意写作可能会故意打破声音规则 $参数 每周安装量 31 存储库 Neurofoo/Agent Skill GitHub 之星 68 第一次看到 3天前 安全审计 Gen Agent Trust Hub 通行证 套接字通行证 斯尼克通行证

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

eos-style 怎么安装?

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

eos-style 支持哪些 AI 工具?

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

eos-style 需要什么权限?

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

eos-style 是免费的吗?

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

eos-style 用的人多吗?

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

eos-style 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

AI 工具类 Skill 对比

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

执行计划 · Codex、Claude

1,515,336173,110只读MIT通过
verification-before-completion

完成前的验证 · Codex、Claude

1,319,472173,121权限未标注MIT通过
subagent-driven-development

子 Agent 驱动开发 · Codex、Claude

1,312,416173,138只读MIT通过
copy-editing

复制编辑 · Codex、Claude

1,209,57625,632只读MIT通过
paywall-upgrade-cro

付费专区升级 cro · Codex、Claude

1,030,17625,617只读MIT通过
eos-style

EOS 风格 · 本页

72968只读MIT通过

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

SKILL.md 原文

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

#PrincipleStatusNotes
1Place yourself in the backgroundPass/Needs Work/N/A[specific feedback]
2Write naturallyPass/Needs Work/N/A[specific feedback]
3Work from suitable designPass/Needs Work/N/A[specific feedback]
4Write with nouns and verbsPass/Needs Work/N/A[specific feedback]
5Revise and rewritePass/Needs Work/N/A[specific feedback]
6Don't overwritePass/Needs Work/N/A[specific feedback]
7Don't overstatePass/Needs Work/N/A[specific feedback]
8Avoid qualifiersPass/Needs Work/N/A[specific feedback]
9Don't affect breezinessPass/Needs Work/N/A[specific feedback]
10Use orthodox spellingPass/Needs Work/N/A[specific feedback]
11Don't explain too muchPass/Needs Work/N/A[specific feedback]
12Don't construct awkward adverbsPass/Needs Work/N/A[specific feedback]
13Make sure speakers are clearPass/Needs Work/N/A[specific feedback]
14Avoid fancy wordsPass/Needs Work/N/A[specific feedback]
15Use dialect sparinglyPass/Needs Work/N/A[specific feedback]
16Be clearPass/Needs Work/N/A[specific feedback]
17Don't inject opinionPass/Needs Work/N/A[specific feedback]
18Use figures of speech sparinglyPass/Needs Work/N/A[specific feedback]
19Don't sacrifice clarity for shortcutsPass/Needs Work/N/A[specific feedback]
20Avoid foreign languagesPass/Needs Work/N/A[specific feedback]
21Prefer standard to offbeatPass/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.
  2. Write naturally — Don't consciously imitate others or force an affected style. Write as you would speak to an intelligent friend.
  3. Work from suitable design — Plan your piece. Know your scope and structure before writing extensively.
  4. Write with nouns and verbs — These give writing strength. Adjectives and adverbs are not your principal weapons.
  5. Revise and rewrite — Good writing is rewriting. Don't expect first drafts to be final.
  6. Don't overwrite — Avoid ornate, flowery prose. Rich prose is hard to digest.
  7. Don't overstate — Avoid superlatives and exaggeration. A single overstatement can undermine your credibility.
  8. Avoid qualifiers — Words like "very," "rather," "quite," "pretty," and "little" weaken prose.
  9. Don't affect breeziness — Forced casualness and flip remarks suggest the writer values cleverness over substance.
  10. Use orthodox spelling — Follow standard conventions unless you have good reason not to.
  11. Don't explain too much — Trust the reader. Avoid excessive adverbs after "said" and over-explanatory dialogue tags.
  12. Don't construct awkward adverbs — Avoid forcing "-ly" onto words that don't take it naturally.
  13. Make sure speakers are clear — In dialogue, readers must always know who is speaking.
  14. Avoid fancy words — Prefer the plain word to the fancy one. "Home" not "domicile."
  15. Use dialect sparingly — The best dialect writers use minimal deviation from standard language.
  16. Be clear — Clarity is the foundation. Muddiness is not depth; obscurity is not profundity.
  17. Don't inject opinion — Keep personal opinions out unless they serve the work. They mark the egoist.
  18. Use figures of speech sparingly — Metaphors and similes need space. Constant comparison exhausts the reader.
  19. Don't sacrifice clarity for shortcuts — Strong, precise words are better than clever abbreviations.
  20. Avoid foreign languages — Write in English. Foreign phrases can seem pretentious.
  21. 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

平台分布

Claude Code

28%
按下载量换算71

Antigravity

22.31%
按下载量换算57

windsurf

17.37%
按下载量换算44

trae

14.34%
按下载量换算37

OpenCode

7.71%
按下载量换算20

Gemini CLI

3.43%
按下载量换算9

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills