draft-conversion-copy
Conversion copy is an ask, not an argument. A cold email lives or dies on the
hook and the one specific reason this reader should care; a landing page is
message hierarchy. Neither is a sequence the reader follows block by block, so
draft-argued-piece's machinery (grounding, candidate openings, the format
arguments) has nothing to bite on here. This skill drafts the ask directly.
Configuration
This repository's agent configuration should have been provided to you (the
## Agent skills block pointing at docs/agents/). If it is missing, use the
defaults below and suggest the user run the setup-aclarify-skills skill.
- Conventions folder (
docs/agents/workspace.md): house rules. Default:
none. If one is configured and holds a voice, tone, brand-voice or
writing-standards document, read it before you draft and obey it; where it is
stricter or more specific than this skill, it wins. With none, write plain,
direct copy and add no house style of your own.
- Scratch folder (
docs/agents/workspace.md): where a longer draft lives.
Default: .scratchpad/ at the repository root, git-ignored.
Fix the frame before writing a word
Conversion copy with a vague frame converts nothing. Settle all four, and where
any is missing ask the user rather than guessing, using your structured-question
tool if you have one; otherwise list the open points numbered in plain text and
stop until they reply.
- Who, exactly. A specific person, role and situation: the head of
operations at a forty-person logistics firm whose dispatch still runs on a
shared spreadsheet, not "operations leaders". Copy to everyone reaches no one.
- The one action. Reply, book twenty minutes, click, sign up. One ask, and
the lowest-friction version of it.
- The channel and format. Cold email, a sequence, a services page, an ad,
a launch post. The shape follows from this.
- The one specific reason this reader acts now. Not the feature list: the
single thing that makes this reader, today, care. If you cannot name it,
the copy is not ready and no rewrite fixes that.
Draft to the form
Every form leads with the reader's dream outcome and explains the mechanism
only after. Hold the house voice from the conventions folder throughout, where
one is configured; conversion copy is outward-facing, so any rule there about
how the organisation speaks to outsiders applies in full.
- Cold email. A hook that earns the second line, the one specific reason
this reader should care, and one small ask. No recap of the recipient's own
business. Signed by a person; the sender is not the author.
- Cold sequence. Each send carries one new angle on the same ask, never a
restated version of the last. The final send makes leaving easy.
- Landing or services page. Message hierarchy: a headline that names the
dream outcome, a subhead that says the mechanism in one line, then sections
where each earns its place, and one primary call to action repeated where the
reader is ready to act.
- Ad or short social post. One idea, a hook on the first line, one call to
action. If it argues, it is the wrong form (see Out of scope).
Cut to the ask
Read the draft back as the reader on a bad day. Every line either moves them
toward the one action or gets cut. Tighter, not bigger. Then hand it on in the
order Composition sets.
Where the draft lives
Short copy stays in the conversation. For a page, a sequence, or copy revised
across sessions, open a scratch entry so revisions survive: load the
scratchpad skill (through your skill tool, /scratchpad, or by reading its
SKILL.md) and run its new writing '<slug>' verb, by the absolute script path
that skill describes and with the configured scratch folder if it is not the
default, then write the draft inside the directory it printed. If scratchpad
is not installed, create <scratch folder>/writing/<UTC-YYYYMMDD-HHMMSS>-<slug>/
at the top of the main checkout and make sure git ignores the scratch folder.
A finished piece leaves scratch for wherever it is sent or published (the mail
client, the site's repository, the ad platform). It is not committed to this
repository unless the user asks.
Composition
In order after this skill, where installed: humanize to strip AI tells, then
seven-copy-critics for the seven hostile readers. A visual asset around the
copy goes to brand-review. Load each by name (through your skill tool,
/<name>, or by reading its SKILL.md); where one is not installed, say so and
skip that step.
Out of scope
- A piece that argues something the reader follows in order: an essay,
newsletter, guide, case study or a long social post that makes a case. That is
draft-argued-piece when a pile of material exists, and
gather-argument-material when nothing is written yet. The boundary is
whether there is an argument to sequence, never length: a 600-word landing
page is in, a 600-word essay is out.
- Reviewing copy that already exists. A hostile read of a draft is
seven-copy-critics; this skill writes the draft it reviews.
- Grounding, candidate openings, block-by-block sequencing, or a
format-argument menu. Those serve an argument, and an ask has none.
1---2name: draft-conversion-copy3description: >-4 Drafts conversion copy, where the piece is an ask not an argument: cold outbound email5 and sequences, landing or services page copy, ads, a short promotional social post. Use6 when someone says write the cold email, the outreach, the landing page, the ad, or the7 launch post. Do NOT use for a piece that argues in order (use `draft-argued-piece`, or8 `gather-argument-material` when nothing is written yet), or to review drafted copy (use9 `seven-copy-critics`).10license: MIT11argument-hint: '[the form: cold email, sequence, landing page, ad, post]'12metadata:13 source: https://skillmd.com/skills/spencermarx/draft-conversion-copy14---1516# draft-conversion-copy1718Conversion copy is an ask, not an argument. A cold email lives or dies on the19hook and the one specific reason this reader should care; a landing page is20message hierarchy. Neither is a sequence the reader follows block by block, so21`draft-argued-piece`'s machinery (grounding, candidate openings, the format22arguments) has nothing to bite on here. This skill drafts the ask directly.2324## Configuration2526This repository's agent configuration should have been provided to you (the27`## Agent skills` block pointing at `docs/agents/`). If it is missing, use the28defaults below and suggest the user run the `setup-aclarify-skills` skill.2930- **Conventions folder** (`docs/agents/workspace.md`): house rules. Default:31 none. If one is configured and holds a voice, tone, brand-voice or32 writing-standards document, read it before you draft and obey it; where it is33 stricter or more specific than this skill, it wins. With none, write plain,34 direct copy and add no house style of your own.35- **Scratch folder** (`docs/agents/workspace.md`): where a longer draft lives.36 Default: `.scratchpad/` at the repository root, git-ignored.3738## Fix the frame before writing a word3940Conversion copy with a vague frame converts nothing. Settle all four, and where41any is missing ask the user rather than guessing, using your structured-question42tool if you have one; otherwise list the open points numbered in plain text and43stop until they reply.44451. **Who, exactly.** A specific person, role and situation: the head of46 operations at a forty-person logistics firm whose dispatch still runs on a47 shared spreadsheet, not "operations leaders". Copy to everyone reaches no one.482. **The one action.** Reply, book twenty minutes, click, sign up. One ask, and49 the lowest-friction version of it.503. **The channel and format.** Cold email, a sequence, a services page, an ad,51 a launch post. The shape follows from this.524. **The one specific reason this reader acts now.** Not the feature list: the53 single thing that makes *this* reader, today, care. If you cannot name it,54 the copy is not ready and no rewrite fixes that.5556## Draft to the form5758Every form leads with the reader's dream outcome and explains the mechanism59only after. Hold the house voice from the conventions folder throughout, where60one is configured; conversion copy is outward-facing, so any rule there about61how the organisation speaks to outsiders applies in full.6263- **Cold email.** A hook that earns the second line, the one specific reason64 this reader should care, and one small ask. No recap of the recipient's own65 business. Signed by a person; the sender is not the author.66- **Cold sequence.** Each send carries one new angle on the same ask, never a67 restated version of the last. The final send makes leaving easy.68- **Landing or services page.** Message hierarchy: a headline that names the69 dream outcome, a subhead that says the mechanism in one line, then sections70 where each earns its place, and one primary call to action repeated where the71 reader is ready to act.72- **Ad or short social post.** One idea, a hook on the first line, one call to73 action. If it argues, it is the wrong form (see [Out of scope](#out-of-scope)).7475## Cut to the ask7677Read the draft back as the reader on a bad day. Every line either moves them78toward the one action or gets cut. Tighter, not bigger. Then hand it on in the79order [Composition](#composition) sets.8081## Where the draft lives8283Short copy stays in the conversation. For a page, a sequence, or copy revised84across sessions, open a scratch entry so revisions survive: load the85`scratchpad` skill (through your skill tool, `/scratchpad`, or by reading its86SKILL.md) and run its `new writing '<slug>'` verb, by the absolute script path87that skill describes and with the configured scratch folder if it is not the88default, then write the draft inside the directory it printed. If `scratchpad`89is not installed, create `<scratch folder>/writing/<UTC-YYYYMMDD-HHMMSS>-<slug>/`90at the top of the main checkout and make sure git ignores the scratch folder.9192A finished piece leaves scratch for wherever it is sent or published (the mail93client, the site's repository, the ad platform). It is not committed to this94repository unless the user asks.9596## Composition9798In order after this skill, where installed: `humanize` to strip AI tells, then99`seven-copy-critics` for the seven hostile readers. A visual asset around the100copy goes to `brand-review`. Load each by name (through your skill tool,101`/<name>`, or by reading its SKILL.md); where one is not installed, say so and102skip that step.103104## Out of scope105106- **A piece that argues something the reader follows in order**: an essay,107 newsletter, guide, case study or a long social post that makes a case. That is108 `draft-argued-piece` when a pile of material exists, and109 `gather-argument-material` when nothing is written yet. The boundary is110 whether there is an argument to sequence, never length: a 600-word landing111 page is in, a 600-word essay is out.112- **Reviewing copy that already exists.** A hostile read of a draft is113 `seven-copy-critics`; this skill writes the draft it reviews.114- **Grounding, candidate openings, block-by-block sequencing, or a115 format-argument menu.** Those serve an argument, and an ask has none.