Token导航 LogoToken导航TokenDH.com
AI 工具只读github未标认证来源可访问clear审计通过

eos-styleEOS 风格

Agent Skill

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

总安装

729

周安装

31

GitHub Stars

68

下载量

255
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

总体评价:[强/需要修改/主要问题]

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

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

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