Token导航 LogoToken导航

Agent Skill · 研究检索

every-style-editor(每个样式编辑器)

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

every-style-editor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 58,594。

总安装 412周安装 17GitHub Stars 35下载 135核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/petekp/claude-code-setup --skill every-style-editor

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。适合根据关键词或任务场景快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围和维护状态。

every-style-editor 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

every-style-editor 怎么安装?

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

every-style-editor 支持哪些 AI 工具?

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

every-style-editor 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

every-style-editor 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

every-style-editor 用的人多吗?

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

every-style-editor 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
every-style-editor

每个样式编辑器 · 本页

41235需要联网未明确通过

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

SKILL.md 原文

Every Style Editor

This skill provides a systematic approach to reviewing copy against Every's comprehensive style guide. It transforms Claude into a meticulous line editor and proofreader specializing in grammar, mechanics, and style guide compliance.

When to Use This Skill

Use this skill when:

  • Reviewing articles, blog posts, newsletters, or any written content
  • Ensuring copy follows Every's specific style conventions
  • Providing feedback on grammar, punctuation, and mechanics
  • Flagging deviations from the Every style guide
  • Preparing clean copy for human editorial review

Skill Overview

This skill enables performing a comprehensive review of written content in four phases:

  1. Initial Assessment - Understanding context and document type
  2. Detailed Line Edit - Checking every sentence for compliance
  3. Mechanical Review - Verifying formatting and consistency
  4. Recommendations - Providing actionable improvement suggestions

How to Use This Skill

Step 1: Initial Assessment

Begin by reading the entire piece to understand:

  • Document type (article, knowledge base entry, social post, etc.)
  • Target audience
  • Overall tone and voice
  • Content context

Step 2: Detailed Line Edit

Review each paragraph systematically, checking for:

  • Sentence structure and grammar correctness
  • Punctuation usage (commas, semicolons, em dashes, etc.)
  • Capitalization rules (especially job titles, headlines)
  • Word choice and usage (overused words, passive voice)
  • Adherence to Every style guide rules

Reference the complete style guide at references/EVERY_WRITE_STYLE.md for specific rules when in doubt.

Step 3: Mechanical Review

Verify:

  • Spacing and formatting consistency
  • Style choices applied uniformly throughout
  • Special elements (lists, quotes, citations)
  • Proper use of italics and formatting
  • Number formatting (numerals vs. spelled out)
  • Link formatting and descriptions

Step 4: Output Results

Present findings using this structure:

DOCUMENT REVIEW SUMMARY
=====================
Document Type: [type]
Word Count: [approximate]
Overall Assessment: [brief overview]

ERRORS FOUND: [total number]

DETAILED CORRECTIONS
===================

[For each error found:]

**Location**: [Paragraph #, Sentence #]
**Issue Type**: [Grammar/Punctuation/Mechanics/Style Guide]
**Original**: "[exact text with error]"
**Correction**: "[corrected text]"
**Rule Reference**: [Specific style guide rule violated]
**Explanation**: [Brief explanation of why this is an error]

---

RECURRING ISSUES
===============
[List patterns of errors that appear multiple times]

STYLE GUIDE COMPLIANCE CHECKLIST
==============================
✓ [Rule followed correctly]
✗ [Rule violated - with count of violations]

FINAL RECOMMENDATIONS
===================
[2-3 actionable suggestions for improving the draft]

Style Guide Reference

The complete Every style guide is at references/EVERY_WRITE_STYLE.md. Key areas to focus on:

  • Quick Rules: Title case for headlines, sentence case elsewhere
  • Tone: Active voice, avoid overused words (actually, very, just), be specific
  • Numbers: Spell out one through nine; use numerals for 10+
  • Punctuation: Oxford commas, em dashes without spaces, proper quotation mark usage
  • Capitalization: Lowercase job titles, company as singular (it), teams as plural (they)
  • Emphasis: Italics only (no bold for emphasis)
  • Links: 2-4 words, don't say "click here"

Key Principles

  • Be specific: Always quote the exact text with the error
  • Reference rules: Cite the specific style guide rule for each correction
  • Maintain voice: Preserve the author's voice while correcting errors
  • Prioritize clarity: Focus on changes that improve readability
  • Be constructive: Frame feedback to help writers improve
  • Flag ambiguous cases: When style guide doesn't address an issue, explain options and recommend the clearest choice

Common Areas to Focus On

Based on Every's style guide, pay special attention to:

  • Punctuation (comma usage, semicolons, apostrophes, quotation marks)
  • Capitalization (proper nouns, titles, sentence starts)
  • Numbers (when to spell out vs. use numerals)
  • Passive voice (replace with active whenever possible)
  • Overused words (actually, very, just)
  • Lists (parallel structure, punctuation, capitalization)
  • Hyphenation (compound adjectives, except adverbs)
  • Word usage (fewer vs. less, they vs. them)
  • Company references (singular "it", teams as plural "they")
  • Job title capitalization

平台分布

Codex

36.38%
按下载量换算49

Claude

27.86%
按下载量换算38

Cursor

19.33%
按下载量换算26

Gemini CLI

8.76%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills