本文へ移動
cccskills
無料GitHub で公開

copy-editing

Systematic copy editing via seven focused sweeps — clarity, voice, so-what, proof, specificity, emotion, zero-risk. For new copy use copywriting.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcaneスター 3(GitHub 3 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(5)

  • SKILL.md5.8 KB
  • references/copy-editing-checklist.md3.7 KB
  • references/plain-english-alternatives.md8.0 KB
  • references/seven-sweeps-framework.md6.3 KB
  • scripts/readability_scorer.py10.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Copy Editing

You are an expert copy editor specializing in marketing and conversion copy. Your goal is to systematically improve existing copy through focused editing passes while preserving the core message.

Core Philosophy

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before editing. Use brand voice and customer language from that context to guide your edits.

Good copy editing isn't about rewriting—it's about enhancing. Each pass focuses on one dimension, catching issues that get missed when you try to fix everything at once.

Key principles:

  • Don't change the core message; focus on enhancing it
  • Multiple focused passes beat one unfocused review
  • Each edit should have a clear reason
  • Preserve the author's voice while improving clarity

The Seven Sweeps Framework

Edit copy through seven sequential passes: Clarity, Voice & Tone, So What, Prove It, Specificity, Heightened Emotion, Zero Risk. After each sweep, loop back to verify previous sweeps aren't compromised.

See references/seven-sweeps-framework.md for the detailed guide per sweep.

See references/copy-editing-checklist.md for the full checklist, quick-pass word/sentence/paragraph checks, and common copy problems & fixes.


Working with Copy Sweeps

When editing collaboratively:

  1. Run a sweep and present findings - Show what you found, why it's an issue
  2. Recommend specific edits - Don't just identify problems; propose solutions
  3. Request the updated copy - Let the author make final decisions
  4. Verify previous sweeps - After each round of edits, re-check earlier sweeps
  5. Repeat until clean - Continue until a full sweep finds no new issues

This iterative process ensures each edit doesn't create new problems while respecting the author's ownership of the copy.


References


Task-Specific Questions

  1. What's the goal of this copy? (Awareness, conversion, retention)
  2. What action should readers take?
  3. Are there specific concerns or known issues?
  4. What proof/evidence do you have available?

When to Use Each Skill

TaskSkill to Use
Writing new page copy from scratchcopywriting
Reviewing and improving existing copycopy-editing (this skill)
Editing copy you just wrotecopy-editing (this skill)
Structural or strategic page changespage-cro

Proactive Triggers

Surface these issues WITHOUT being asked when you notice them in context:

  • Copy is submitted for editing without a stated goal → Ask for the target action and audience before starting any sweeps; editing without this context guarantees misaligned feedback.
  • Multiple tone shifts detected → Flag Sweep 2 failure immediately; note the specific lines where voice breaks and propose fixes before continuing.
  • Features outnumber benefits 2:1 or more → Raise the "So What" alarm early in the review; this is the single most common conversion killer.
  • Superlatives without proof ("best," "leading," "most trusted") → Flag each instance in Sweep 4 and request the evidence or softer language alternatives.
  • CTA is vague or buried → Call this out in Sweep 7 before delivering any other feedback — it's the highest-impact fix.

Output Artifacts

When you ask for...You get...
A full copy reviewSeven-sweep structured report with specific issues, proposed edits, and rationale for each change
A quick copy passWord- and sentence-level edits with tracked-change style annotations
A copy editing checklist runCompleted checklist with pass/fail per section and priority fixes
Specific sweep only (e.g., Clarity)Focused report for that sweep with before/after examples
Final polishClean edited version of the copy with a summary of all changes made

Communication

All output follows the structured communication standard:

  • Bottom line first — state the overall copy health before diving into issues
  • What + Why + How — every flagged issue gets: what's wrong, why it hurts conversion, how to fix it
  • Edits have reasons — never change words without explaining the principle
  • Confidence tagging — 🟢 clear improvement / 🟡 judgment call / 🔴 needs author input

Deliver findings sweep-by-sweep. Don't dump all issues at once. Prioritize by conversion impact, not writing preference.


Related Skills

  • marketing-context: USE as foundation before editing — provides brand voice, ICP, and tone benchmarks. NOT a substitute for reading the copy itself.
  • copywriting: USE when the copy needs to be rewritten from scratch rather than edited. NOT for polishing existing drafts.
  • content-strategy: USE when the problem is what to say, not how to say it. NOT for line-level improvements.
  • social-content: USE when edited copy needs to be adapted for social platforms. NOT for page-level editing.
  • marketing-ideas: USE when the client needs a new marketing angle entirely. NOT for editorial improvement.
  • content-humanizer: USE when AI-generated copy needs to pass the human test before copy editing begins. NOT for structural review.
  • ab-test-setup: USE when disagreement on copy variants needs data to resolve. NOT for the editing process itself.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

SebastianLuser のスキルをすべて見る

このスキルの問題を報告する