Use copy-editing when a page or email already has a draft, or when older copy contains stale facts. It reviews one dimension at a time and checks that later edits have not damaged earlier improvements. The objective is a better version of the original message, not an unrelated rewrite.
Install and invoke
Run this in your project terminal to install only this skill for Claude Code:
npx skills add coreyhaines31/marketingskills --skill copy-editing -a claude-code
Node.js and npx must be available. For Codex, replace -a claude-code with -a codex. In the agent conversation, explicitly ask it to use copy-editing and supply your material. The installation command belongs in the terminal, not in your content brief.
Give the agent the whole draft
Supply the page, intended reader, and desired action. Ask it to read .agents/product-marketing.md for brand voice when available. Mark pricing, product limitations, or other fixed wording explicitly.
Example brief:
Use copy-editing on landing.md without replacing the whole concept.
Readers are studio owners; the goal is a demo booking. Preserve product scope and the terms in pricing.md.
First identify the five biggest comprehension problems with original text, replacement, and reason. Then review with the seven-pass method.
Flag unsupported claims instead of adding customers or figures.
The early passes check understanding and consistent voice. Later ones connect features to reader benefits, inspect evidence, improve specificity, and address emotion and hesitation. The order matters: a more exciting headline must not undo the accuracy established earlier. Send an exaggerated improvement back for revision.
Review the effect of each change
Request explanations, not only a clean replacement document. Splitting a long sentence, replacing internal terminology, or clarifying a button can help. Inventing a percentage, refund policy, or free trial to make a line more concrete cannot. Where proof is missing, prefer a narrower claim you can support.
Put the result into the real page. Check that the heading and body still promise the same thing, the primary action remains clear, and important conditions have not disappeared. Review the change log against product names, prices, quotations, and eligibility terms. A refresh also needs working links and examples that still match the current product.
The skill offers simulated specialist scoring as an additional review tool. Use those scores to locate weaknesses, not as evidence of customer approval or permission to publish. Ask which sentence caused the concern and how the proposed change helps. A typo correction need not run the entire process. If audience and structure are fundamentally unclear, resolve the writing brief before continuing to polish individual words.
Edit in passes without losing the original facts
The official seven-sweep approach starts with clarity, then voice and tone. Next ask “so what?” of each claim, check proof and specificity, and finally examine emotional relevance and barriers to action. “Make it more persuasive” bundles all these decisions together and makes it hard to assess the result. For each pass, request a four-column review: original sentence, problem, proposed replacement, and reason. Accept changes selectively.
Suppose a product page says “the leading all-in-one solution” without explaining the job it performs. Add the work situation and who benefits first, then look for publishable customer evidence. If none exists, state a real capability rather than converting a vague adjective into an invented statistic. An effective instruction is: “Run clarity and proof sweeps only. Preserve pricing and product promises. Mark unsupported statements as questions for me instead of rewriting them as facts.”
Compare the edited page section by section with the original. Does the CTA still go to the right destination? Has the voice changed unexpectedly? Did a legal or product condition disappear in the cleanup? If the entire page puts information in the wrong order, return to structure first; line editing alone cannot make a buried answer easy to find.
Example: edit a renewal notice without changing terms
A renewal email is drafted, but customers say it sounds like a collection warning. Give the skill the draft, actual renewal date, billing terms, and voice guidance. Ask: “Use copy-editing for clarity, tone, proof, and risk sweeps only. Preserve the amount and date. Flag any sentence that could imply immediate loss of access. Give line-by-line recommendations, not a new promotion.”
Verify that no edit alters the underlying facts. Automatic and manual renewal must not be conflated, and the agent cannot guess a grace period after failed payment. A reader should understand the amount, charge date, where to view or change the plan, and whom to contact. If softer language hides an important condition at the bottom, the edit has failed; move the condition into a visible position before polishing tone.
What the public demo can show
A third-party developer built a paste/upload interface for the seven-pass editing workflow, but the public page does not show a complete before-and-after artifact. To evaluate the method, use copy you are allowed to share and inspect each pass: which sentences changed, why, and whether the author's meaning survived. Keep sensitive client drafts in a controlled workspace. The interface alone does not establish quality with real customers.