Token导航 LogoToken导航

Agent Skill · AI 工具

eos-usage(EOS 使用情况)

eos-usage 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 Codex、Claude、Cursor、Gemini CLI 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

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

总安装 549周安装 22GitHub Stars 65下载 178核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

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

语法准确性:[干净/小问题/重大错误] 最常见的错误类型:[错误类别] 需要更正: [最高优先级修复] [第二优先] [第三优先] 指南 这些规则并未涵盖所有逗号用法 - 重点关注所描述的特定模式 规则 2(连续逗号)是某些指南中的一种风格选择; Strunk & White 的倡导者 有些片段是为了创意写作的效果而故意的 技术写作对于冒号和列表可能有不同的约定 $参数 每周安装量 22 存储库 Neurofoo/Agent Skill GitHub 之星 65 第一次看到 2天前 安全审计 Gen Agent Trust Hub 通行证 套接字通行证 斯尼克通行证

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

eos-usage 怎么安装?

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

eos-usage 支持哪些 AI 工具?

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

eos-usage 需要什么权限?

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

eos-usage 是免费的吗?

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

eos-usage 用的人多吗?

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

eos-usage 安全吗?

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

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

值得选的地方

  • 同时适配 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-usage

EOS 使用情况 · 本页

54965只读MIT通过

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

SKILL.md 原文

Elements of Style: 11 Rules of Usage

Review writing against Strunk & White's 11 elementary rules of usage from Chapter I.

Instructions

Analyze the provided text for grammatical and mechanical errors. Flag specific violations with line numbers or quotes where possible.

Output Format

Text Under Review: [title or brief description]


Usage Review

#RuleStatusIssues Found
1Form possessive singular with 'sPass/Needs Work/N/A[issues]
2Use serial commaPass/Needs Work/N/A[issues]
3Enclose parenthetic expressions in commasPass/Needs Work/N/A[issues]
4Comma before conjunction + independent clausePass/Needs Work/N/A[issues]
5No comma splicePass/Needs Work/N/A[issues]
6No sentence fragmentsPass/Needs Work/N/A[issues]
7Use colon to introduce lists/appositivesPass/Needs Work/N/A[issues]
8Use dash for abrupt breaksPass/Needs Work/N/A[issues]
9Subject-verb agreementPass/Needs Work/N/A[issues]
10Proper pronoun casePass/Needs Work/N/A[issues]
11Dangling modifiersPass/Needs Work/N/A[issues]

Errors Found

Rule 5: Comma Splices

LocationErrorCorrection
[line/quote]"It is cold, we should go inside""It is cold; we should go inside" OR "It is cold, so we should go inside"

Rule 6: Sentence Fragments

LocationFragmentSuggested Fix
[line/quote][fragment][complete sentence]

Rule 11: Dangling Modifiers

LocationErrorCorrection
[line/quote]"Walking down the street, the trees were beautiful""Walking down the street, I noticed the beautiful trees"

Rule Reference

  1. Form the possessive singular by adding 's — Charles's friend, Burns's poems, the witch's malice. Exceptions: ancient proper names ending in -es or -is (Jesus', Moses'), and common idioms (for conscience' sake).
  2. In a series of three or more, use a comma after each term except the last — red, white, and blue. The serial comma prevents ambiguity.
  3. Enclose parenthetic expressions between commas — "The best way to see a country, unless you are pressed for time, is to travel on foot." If the interruption is slight, commas may be omitted.
  4. Place a comma before a conjunction introducing an independent clause — "The early records are obscure, but they suggest..." This rule applies when both clauses are independent (could stand alone).
  5. Do not join independent clauses with a comma — This error is the "comma splice." Wrong: "It is cold, we should go inside." Right: "It is cold; we should go inside" or "It is cold. We should go inside."
  6. Do not break sentences in two — Avoid sentence fragments. "I met them on a Cunard liner many years ago. Coming home from Liverpool to New York." The second part should not stand alone.
  7. Use a colon after an independent clause to introduce a list, appositive, amplification, or illustrative quotation — "The situation is perilous: our enemies are many, our supplies few."
  8. Use a dash to set off an abrupt break or to announce a long appositive or summary — "His first thought on getting out of bed—if he had any thought at all—was to get back in again." Use sparingly; frequent dashes give writing a breathless quality.
  9. The subject and verb must agree in number — "The bittersweet flavor of youth—its trials, its joys, its adventures, its challenges—are not soon forgotten" is wrong; use "is."
  10. Use the proper case of pronoun — "between you and I" is wrong; use "between you and me." In compound constructions, test each pronoun alone.
  11. A participial phrase at the beginning of a sentence must refer to the grammatical subject — "Walking down the street, the trees were beautiful" is wrong (trees weren't walking). Fix: "Walking down the street, I noticed the beautiful trees."

Summary

Grammar Accuracy: [Clean/Minor Issues/Significant Errors]

Most Common Error Type: [error category]

Corrections Needed:

  1. [Highest priority fix]
  2. [Second priority]
  3. [Third priority]

Guidelines

  • Not all comma usage is covered by these rules—focus on the specific patterns described
  • Rule 2 (serial comma) is a style choice in some guides; Strunk & White advocate for it
  • Some fragments are intentional for effect in creative writing
  • Technical writing may have different conventions for colons and lists

$ARGUMENTS

平台分布

Claude Code

30.3%
按下载量换算54

Antigravity

25.33%
按下载量换算45

windsurf

18.75%
按下载量换算33

trae

12.56%
按下载量换算22

OpenCode

7.77%
按下载量换算14

Gemini CLI

3.55%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills