skills/halbert-copy-editor/SKILL.md
Edit and punch up sales copy, marketing emails, landing pages, ads, and any persuasive writing using the Halbert Copywriting Method.
npx skillsauth add arndvs/ctrlshft halbert-copy-editorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Output "Read Halbert Copy Editor skill." to chat to acknowledge you read this file.
Core principle: The goal is a "greased slide" — once a reader starts, they should fall effortlessly from one line to the next until they have an uncontrollable urge to act. Every edit either removes friction or adds pull.
Before editing anything, identify the request type and choose the right path.
Trigger: User pastes copy and asks to improve, edit, review, or rewrite it — or gives no specific instruction. Run all 4 stages in sequence.
Trigger: User specifies what kind of help they want. Skip to that stage.
| User says… | Jump to | |---|---| | "Hard to read" / "too dense" / "format this" | Stage 1 | | "Confusing" / "unclear" / "clean this up" | Stage 2 | | "Boring" / "people stop reading" / "needs flow" | Stage 3 | | "Needs more punch" / "make it sell harder" / "punchier" | Stage 4 |
Even on a targeted fix, quickly scan the other stages for any glaring issues and flag them at the end — but don't rewrite what wasn't asked for.
Goal: Make the copy look easy to read before the prospect reads a word.
Goal: Polish until any reader falls through the copy without tripping.
Read the entire piece aloud. Every stumble is a fix. Mark all rough spots before touching anything — edit in complete passes, never spot-fix and restart.
Find every: I, he, she, it, they, them, one, this, that (used as a reference). Ask: is it crystal clear what this refers to? If not, replace with the actual name or a more powerful descriptor (e.g. "The Prince of Print" instead of "he").
Delete or replace ~90% of "that" uses:
Replace any word a 6th-grader might not know. Aim for 6th-grade reading level or below for broad audiences. Use a thesaurus to simplify, not complicate. Never make readers feel uneducated.
Flag any word used more than once per page. Find a simple synonym via thesaurus. Per John Carlton: don't use the same verb twice on a single page.
When copy jumps abruptly between unrelated points, bridge with:
Moving on… / Anyway, / However, / Also, / Plus, / With that said,
Goal: Inject momentum so readers feel they'll miss something if they stop.
End sentences/paragraphs so the next thought feels mandatory. Techniques:
Don't overdo it. A mix of cliffhangers, incomplete thoughts, and high notes is the goal — too many cliffhangers feels cheap.
Write complete sentences that are incomplete thoughts. The reader finishes a sentence and still wants to know: what happened? why? what does that mean?
The surprise/punchline/key benefit must land at the end of the sentence — just like a comedian's punchline. Reorder sentences that bury the payoff.
Good copy has natural rhythm — rising and falling, short and long. If you have to stop for breath mid-sentence, it's too long. If every sentence ends on a cliffhanger, back off.
Goal: Maximize the emotional pull and remove everything that weakens it.
Order of emphasis, weakest to strongest:
Italics → "Quotes" → Underlining → Bold → ALL CAPS → Highlighting → High-Contrast Color → Moving/Flashing Text
Use sparingly. Emphasize only what's genuinely big news. Don't bold everything or nothing stands out.
Replace flat words with charged ones. Build two lists from the National Enquirer:
Swap while editing: "upset" → "livid"; "rare" → "impossible to find"; "problem" → "crisis."
Remove words that weaken claims: like, some, mostly, partially, could, may, possibly. Ask: does this qualifier make the statement more accurate? If not, cut it. Compare: "This may work" vs. "This WILL work."
Words ending in "-ly" that try to amplify (very, extremely, absolutely, incredibly) often signal a weak phrase underneath. Eliminate the adverb and rewrite: "the room is very messy" → "the room looked like a hurricane came through."
Use one or two industry-specific terms to signal expertise, then immediately explain them in plain English. This builds trust without losing readers.
Find every question or objection a reader will naturally have. Move the answer to just before the point where the question arises — never after. Common pre-emptions:
Read the copy pretending you are a busy, self-important reader. After each sentence ask: "So what? Why should I care?" Cut or rewrite everything that can't pass this test. Be ruthless.
Swap words that feel like work or responsibility: | Avoid | Replace with | |-------|-------------| | teach / learn | show you / let you in on / hand you the key | | work | discover / get / unlock | | complicated technique | simple trick / shortcut / formula | | leader / responsibility | [reframe as personal benefit] |
Except in stories, use present progressive ("-ing" verbs) to create a sense of ongoing movement and mild urgency:
"The formula has helped copywriters…" → "The formula is helping copywriters…"
During drafting, use "because" to explain everything. During editing, cut most "because" constructions by breaking them into separate sentences. The reasoning flows naturally without the word.
Full edit:
Targeted fix:
Use this sequence for each full editing pass:
| Rule | Application | |------|-------------| | Write like a friend talking, not a professor writing | Conversational tone throughout | | Brevity ≠ short copy — it means no wasted words | Cut anything that doesn't add desire or momentum | | Grammar is a tool, not a god | Break rules when it sounds better out loud | | Long copy is fine; long-winded copy is not | Keep moving from one exciting point to the next | | Never give the reader a safe stopping point | Every paragraph should make them feel like the next one has something they need | | Editing takes as long as writing | Budget 1/3 of total project time to editing | | Multiple passes, not one perfect pass | Each pass catches more; get faster over time |
development
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
development
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
tools
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
testing
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.