Write copy that sells — landing page, headline, product description, email, ad, social post, app-store listing, newsletter. Use whenever the text has to make someone act rather than just inform.
Installs into .claude/skills of the current project.
Are you the author of Marketing Copy?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ivanvp91-marketing-copy)
---
name: marketing-copy
description: Write copy that sells — landing page, headline, product description, email, ad, social post, app-store listing, newsletter. Use whenever the text has to make someone act rather than just inform.
description_ru: Написать продающий текст — лендинг, заголовок, описание продукта, письмо, объявление, пост, карточку в сторе, рассылку. Всегда, когда текст должен побудить к действию, а не просто сообщить.
triggers: копирайт, копирайтинг, copywriting, headline, слоган, tagline, реклама, объявление, рассылка, текст для лендинга, описание продукта, product description
---
# Marketing copy
## 1. Gather before writing
- **Product**: what it literally does. If it is in this repo, read the README and the actual features — never invent capabilities.
- **Reader**: who they are, what they are trying to do, what they use today.
- **Pain**: the specific frustration in their words, not "inefficiency".
- **Proof**: numbers, integrations, customers, guarantees — whatever is real.
- **One action**: the single thing this piece should cause.
If proof or audience is unknown, ask — or write it and flag the assumptions. Never fabricate metrics, testimonials or logos.
## 2. Lead with the outcome
The reader's first question is "what do I get". Answer it in the first line. The mechanism ("AI-powered", "built on X") is support, not the headline. Test any sentence: could a competitor say the same? Then it says nothing — replace it with something only you can claim.
## 3. Landing page skeleton
1. **Headline** — the outcome, ≤ 10 words.
2. **Subhead** — who it is for and how it works, one sentence.
3. **Primary CTA** — a verb phrase describing what happens next (`Start free`, not `Learn more`).
4. **Proof strip** — numbers, logos, one hard result.
5. **Three benefits** — each a benefit heading with one supporting line; feature named, outcome first.
6. **Objection handling** — price, migration, lock-in, security, "will it work for me".
7. **Close** — repeat the CTA with the outcome restated.
## 4. Sentence craft
- Short sentences. Concrete nouns. Active verbs. Second person.
- Specific beats superlative: "deploys in 40 seconds" over "blazing fast".
- Cut: "revolutionary", "seamless", "cutting-edge", "solution", "empower", "unlock", "in today's world".
- Read it aloud — if you would not say it to a colleague, rewrite it.
- Match the register the audience already uses; developers distrust adjectives, executives want outcomes and risk.
## 5. Format for the channel
Email: one idea, subject ≤ 45 chars, first line visible in preview, one CTA. Ad: headline does the work, no setup. Social: first line stops the scroll, no link in the first sentence. App store: first three lines are all most people read.
## What not to do
- No claims you cannot support, no fake urgency, no invented social proof.
- Do not write about the company; write about the reader.
- Do not stack three CTAs — one page, one action.
## Answer format
The copy itself, ready to paste, labelled by slot (Headline / Subhead / CTA / …). Then: 2–3 headline alternatives with different angles, and a list of every assumption or number that needs confirming.