Copywriting
Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.
MCP get_skill({ skillId: "copywriting-9107bcf3" })Use this skill with your agent
Create a free account and connect via MCP
# 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. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
Markdown Content Rules
Markdown guidelines and content creation standards for blog posts
Anti Slop
Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work.
Blog Writing Guide
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.