Token导航 LogoToken导航

Agent Skill · 研究检索

copy-editor(文案编辑)

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

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

总安装 1,053周安装 43GitHub Stars 37下载 337核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill copy-editor

这个 Skill 是做什么的

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

通用文案编辑工具,检查语法、风格与清晰度,支持项目定制风格指南。分四阶段操作:语境分析、语言润色、结构优化与一致性核查。调用时提供完整文本与可选读者类型(人类/LLM),返回修订标记或直接输出。适用于博客、文档与广告等多种场景,保持专业性与可读性平衡。

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

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

copy-editor 怎么安装?

在终端执行 npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill copy-edito…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

copy-editor 支持哪些 AI 工具?

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

copy-editor 需要什么权限?

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

copy-editor 是免费的吗?

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

copy-editor 用的人多吗?

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

copy-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调用外部服务未明确有提醒
copy-editor

文案编辑 · 本页

1,05337需要联网未明确通过

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

SKILL.md 原文

Copy Editor

A general-purpose copy editing skill that reviews and edits text for grammar, style, and clarity. Supports custom project style guides with a comprehensive default fallback.

When to Use

  • Reviewing marketing copy, landing pages, or ad text
  • Editing blog posts, articles, or thought leadership pieces
  • Polishing documentation or technical writing
  • Improving email campaigns or newsletters
  • Refining product descriptions or UI text
  • Any business writing that needs professional polish

Methodology

Follow these four phases sequentially for thorough copy review.

Phase 1: Context Analysis

Before editing, understand the document:

  1. Document Type: Marketing copy, blog post, documentation, email, etc.
  2. Target Audience: Technical, general, executive, customer-facing
  3. Intended Tone: Formal, conversational, persuasive, informative
  4. Purpose: Inform, persuade, instruct, engage

Note these factors as they influence which style rules apply. Marketing copy allows more creative freedom than documentation.

Phase 2: Style Guide Resolution

Locate the applicable style guide in this order:

  1. Voice DNA: Check for .claude/voice-dna.md (personal voice rules)
  2. Brand voice: Check for docs/brand-voice.md or .claude/brand-voice.md
  3. Project root: Check for STYLE_GUIDE.md
  4. Claude directory: Check for .claude/style-guide.md
  5. Docs folder: Check for docs/style-guide.md
  6. Default fallback: Use references/DEFAULT_STYLE_GUIDE.md from this skill

Voice DNA and brand voice files take precedence over generic style guides. Apply their banned phrases and writing rules as hard constraints.

# Search for project style guide
glob "STYLE_GUIDE.md" || glob ".claude/style-guide.md" || glob "docs/style-guide.md"

If a project style guide exists, prioritize its rules. The default guide provides universal best practices for cases not covered.

Phase 3: Line-by-Line Review

Systematically review the copy for:

Grammar & Mechanics

  • Subject-verb agreement
  • Punctuation (commas, semicolons, apostrophes)
  • Capitalization consistency
  • Number formatting
  • Spelling and typos

Voice & Clarity

  • Active vs. passive voice (prefer active)
  • Sentence length and readability
  • Jargon and unnecessary complexity
  • Redundant words and phrases
  • Parallel structure in lists

Style Adherence

  • Consistency with style guide rules
  • Tone appropriate for audience
  • Brand voice alignment (if applicable)
  • Formatting conventions

Content Quality

  • Logical flow and transitions
  • Clear headlines and subheadings
  • Effective calls-to-action
  • Accurate claims and statements

AI Writing Tells (see references/AI_WRITING_TELLS.md)

  • Vocabulary clusters (delve, landscape, pivotal, robust, etc.)
  • Formulaic phrases ("In today's...", "In conclusion...")
  • Vague attributions ("some experts", "widely regarded")
  • Structural patterns (mechanical balance, essay format)
  • Sycophantic phrases ("I hope this helps")
  • Negation-assertion pattern ("This isn't X. This is Y.") - fatal
  • Engagement bait ("Let that sink in", "Read that again")
  • AI cringe terms ("Supercharge", "Unlock", "Future-proof")
  • Generic insider claims ("Here's what nobody tells you")

Phase 4: Structured Report

Present findings in this format:

## Copy Review Report

**Document**: [filename or description]
**Word Count**: [count]
**Issues Found**: [total count]

### Summary
[1-2 sentence overview of document quality and main areas for improvement]

### Issues by Category

#### Grammar & Mechanics ([count])
| Location | Original | Issue | Suggested Fix |
|----------|----------|-------|---------------|
| Line X | "exact quote" | [issue type] | "corrected text" |

#### Voice & Clarity ([count])
| Location | Original | Issue | Suggested Fix |
|----------|----------|-------|---------------|
| Line X | "exact quote" | [issue type] | "corrected text" |

#### Style Guide Violations ([count])
| Location | Original | Rule Violated | Suggested Fix |
|----------|----------|---------------|---------------|
| Line X | "exact quote" | [rule reference] | "corrected text" |

#### AI Writing Tells ([count])
| Location | Original | Pattern Type | Suggested Fix |
|----------|----------|--------------|---------------|
| Line X | "exact quote" | [vocabulary/phrase/structure/attribution] | "corrected text" |

### Recurring Patterns
- [Pattern 1]: Appears X times - [recommendation]
- [Pattern 2]: Appears X times - [recommendation]

### Top 3 Recommendations
1. [Most impactful improvement]
2. [Second priority]
3. [Third priority]

### Style Guide Compliance
- [x] Active voice preference
- [ ] Number formatting (issues found)
- [x] Capitalization rules
- [ ] [Other applicable rules...]

### AI Writing Check
- [ ] No AI vocabulary clusters
- [ ] No formulaic phrases
- [ ] Specific attributions (not "some experts")
- [ ] Natural structure (not essay format)

Guiding Principles

  1. Quote exactly: Always show the original text verbatim
  2. Cite rules: Reference specific style guide rules when applicable
  3. Preserve voice: Maintain the author's style while improving clarity
  4. Prioritize impact: Focus on issues that affect comprehension first
  5. Be constructive: Frame suggestions positively, explain the "why"
  6. Note ambiguity: When rules conflict or are unclear, explain options

Output Options

Based on user request, provide:

  • Full report: Complete analysis with all categories
  • Quick scan: Top 5 most important issues only
  • Category focus: Deep dive on specific area (grammar, style, etc.)
  • Inline edits: Apply fixes directly with Edit tool (with user permission)

Example Usage

User: Review my landing page copy for issues
Assistant: I'll use the copy-editor skill to review your landing page.

[Executes Phase 1-4, produces structured report]
User: Quick grammar check on this email
Assistant: I'll do a quick scan focusing on grammar and mechanics.

[Produces abbreviated report with top issues]

平台分布

Codex

38.18%
按下载量换算129

Claude

32.73%
按下载量换算110

Cursor

17.45%
按下载量换算59

Gemini CLI

9.35%
按下载量换算32

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills