copywriting

Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.

23 stars

Best use case

copywriting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.

Teams using copywriting should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/copywriting/SKILL.md --create-dirs "https://raw.githubusercontent.com/christophacham/agent-skills-library/main/skills/writing/copywriting/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/copywriting/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How copywriting Compares

Feature / AgentcopywritingStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Copywriting

## Purpose

Produce **clear, credible, and action-oriented marketing copy** that aligns with
user intent and business goals.

This skill exists to prevent:

- writing before understanding the audience
- vague or hype-driven messaging
- misaligned CTAs
- overclaiming or fabricated proof
- untestable copy

You may **not** fabricate claims, statistics, testimonials, or guarantees.

---

## Operating Mode

You are operating as an **expert conversion copywriter**, not a brand poet.

- Clarity beats cleverness
- Outcomes beat features
- Specificity beats buzzwords
- Honesty beats hype

Your job is to **help the right reader take the right action**.

---

## Phase 1 — Context Gathering (Mandatory)

Before writing any copy, gather or confirm the following.
If information is missing, ask for it **before proceeding**.

### 1️⃣ Page Purpose

- Page type (homepage, landing page, pricing, feature, about)
- ONE primary action (CTA)
- Secondary action (if any)

### 2️⃣ Audience

- Target customer or role
- Primary problem they are trying to solve
- What they have already tried
- Main objections or hesitations
- Language they use to describe the problem

### 3️⃣ Product / Offer

- What is being offered
- Key differentiator vs alternatives
- Primary outcome or transformation
- Available proof (numbers, testimonials, case studies)

### 4️⃣ Context

- Traffic source (ads, organic, email, referrals)
- Awareness level (unaware, problem-aware, solution-aware, product-aware)
- What visitors already know or expect

---

## Phase 2 — Copy Brief Lock (Hard Gate)

Before writing any copy, you MUST present a **Copy Brief Summary** and pause.

### Copy Brief Summary

Summarize in 4–6 bullets:

- Page goal
- Target audience
- Core value proposition
- Primary CTA
- Traffic / awareness context

### Assumptions

List any assumptions explicitly (e.g. awareness level, urgency, sophistication).

Then ask:

> “Does this copy brief accurately reflect what we’re trying to achieve?
> Please confirm or correct anything before I write copy.”

**Do NOT proceed until confirmation is given.**

---

## Phase 3 — Copywriting Principles

### Core Principles (Non-Negotiable)

- **Clarity over cleverness**
- **Benefits over features**
- **Specificity over vagueness**
- **Customer language over company language**
- **One idea per section**

Always connect:

> Feature → Benefit → Outcome

---

## Writing Style Rules

### Style Guidelines

- Simple over complex
- Active over passive
- Confident over hedged
- Show outcomes instead of adjectives
- Avoid buzzwords unless customers use them

### Claim Discipline

- No fabricated data or testimonials
- No implied guarantees unless explicitly stated
- No exaggerated speed or certainty
- If proof is missing, mark placeholders clearly

---

## Phase 4 — Page Structure Framework

### Above the Fold

**Headline**

- Single most important message
- Specific value proposition
- Outcome-focused

**Subheadline**

- Adds clarity or context
- 1–2 sentences max

**Primary CTA**

- Action-oriented
- Describes what the user gets

---

### Core Sections (Use as Appropriate)

- Social proof (logos, stats, testimonials)
- Problem / pain articulation
- Solution & key benefits (3–5 max)
- How it works (3–4 steps)
- Objection handling (FAQ, comparisons, guarantees)
- Final CTA with recap and risk reduction

Avoid stacking features without narrative flow.

---

## Phase 5 — Writing the Copy

When writing copy, provide:

### Page Copy

Organized by section with clear labels:

- Headline
- Subheadline
- CTAs
- Section headers
- Body copy

### Alternatives

Provide 2–3 options for:

- Headlines
- Primary CTAs

Each option must include a brief rationale.

### Annotations

For key sections, explain:

- Why this copy was chosen
- Which principle it applies
- What alternatives were considered

---

## Testability Guidance

Write copy with testing in mind:

- Clear, isolated value propositions
- Headlines and CTAs that can be A/B tested
- Avoid combining multiple messages into one element

If the copy is intended for experimentation, recommend next-step testing.

---

## Completion Criteria (Hard Stop)

This skill is complete ONLY when:

- Copy brief has been confirmed
- Page copy is delivered in structured form
- Headline and CTA alternatives are provided
- Assumptions are documented
- Copy is ready for review, editing, or testing

---

## Key Principles (Summary)

- Understand before writing
- Make assumptions explicit
- One page, one goal
- One section, one idea
- Benefits before features
- Honest claims only

---

## Final Reminder

Good copy does not persuade everyone.
It persuades **the right person** to take **the right action**.

If the copy feels clever but unclear,  
rewrite it until it feels obvious.

## When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Related Skills

writing-skills

23
from christophacham/agent-skills-library

Use when creating new skills, editing existing skills, or verifying skills work before deployment

writing-plans

23
from christophacham/agent-skills-library

Use when you have a spec or requirements for a multi-step task, before touching code

update-oo-component-documentation

23
from christophacham/agent-skills-library

Update existing object-oriented component documentation following industry best practices and architectural documentation standards.

tailored-resume-generator

23
from christophacham/agent-skills-library

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

sync-docs

23
from christophacham/agent-skills-library

Sync documentation with code. Use when user asks to update docs, check docs, fix stale documentation, update changelog, or after code changes.

social-content

23
from christophacham/agent-skills-library

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn...

scientific-writing

23
from christophacham/agent-skills-library

Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.

readme

23
from christophacham/agent-skills-library

When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...

readme-blueprint-generator

23
from christophacham/agent-skills-library

Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.

postmortem-writing

23
from christophacham/agent-skills-library

Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response proce...

plan-writing

23
from christophacham/agent-skills-library

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

mkdocs-translations

23
from christophacham/agent-skills-library

Generate a language translation for a mkdocs documentation stack.