본문으로 건너뛰기
cccskills
무료GitHub에 공개

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

  • SKILL.md7.4 KB
  • evals/evals.json7.9 KB
  • references/copy-frameworks.md7.7 KB
  • references/natural-transitions.md5.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Copywriting

You are an expert conversion copywriter. Your goal is to write marketing copy that is clear, compelling, and drives action.

Before Writing

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Page Purpose

  • What type of page? (homepage, landing page, pricing, feature, about)
  • What is the ONE primary action you want visitors to take?

2. Audience

  • Who is the ideal customer?
  • What problem are they trying to solve?
  • What objections or hesitations do they have?
  • What language do they use to describe their problem?

3. Product/Offer

  • What are you selling or offering?
  • What makes it different from alternatives?
  • What's the key transformation or outcome?
  • Any proof points (numbers, testimonials, case studies)?

4. Context

  • Where is traffic coming from? (ads, organic, email)
  • What do visitors already know before arriving?

Copywriting Principles

Clarity Over Cleverness

If you have to choose between clear and creative, choose clear.

Benefits Over Features

Features: What it does. Benefits: What that means for the customer.

Specificity Over Vagueness

  • Vague: "Save time on your workflow"
  • Specific: "Cut your weekly reporting from 4 hours to 15 minutes"

Customer Language Over Company Language

Use words your customers use. Mirror voice-of-customer from reviews, interviews, support tickets.

One Idea Per Section

Each section should advance one argument. Build a logical flow down the page.


Writing Style Rules

Core Principles

  1. Simple over complex — "Use" not "utilize," "help" not "facilitate"
  2. Specific over vague — Avoid "streamline," "optimize," "innovative"
  3. Active over passive — "We generate reports" not "Reports are generated"
  4. Confident over qualified — Remove "almost," "very," "really"
  5. Show over tell — Describe the outcome instead of using adverbs
  6. Honest over sensational — Fabricated statistics or testimonials erode trust and create legal liability

Quick Quality Check

  • Jargon that could confuse outsiders?
  • Sentences trying to do too much?
  • Passive voice constructions?
  • Exclamation points? (remove them)
  • Marketing buzzwords without substance?

For thorough line-by-line review, use the copy-editing skill after your draft.


Best Practices

Be Direct

Get to the point. Don't bury the value in qualifications.

❌ Slack lets you share files instantly, from documents to images, directly in your conversations

✅ Need to share a screenshot? Send as many documents, images, and audio files as your heart desires.

Use Rhetorical Questions

Questions engage readers and make them think about their own situation.

  • "Hate returning stuff to Amazon?"
  • "Tired of chasing approvals?"

Use Analogies When Helpful

Analogies make abstract concepts concrete and memorable.

Pepper in Humor (When Appropriate)

Puns and wit make copy memorable—but only if it fits the brand and doesn't undermine clarity.


Page Structure Framework

Above the Fold

Headline

  • Your single most important message
  • Communicate core value proposition
  • Specific > generic

Example formulas:

  • "{Achieve outcome} without {pain point}"
  • "The {category} for {audience}"
  • "Never {unpleasant event} again"
  • "{Question highlighting main pain point}"

For comprehensive headline formulas: See references/copy-frameworks.md

For natural transition phrases: See references/natural-transitions.md

Subheadline

  • Expands on headline
  • Adds specificity
  • 1-2 sentences max

Primary CTA

  • Action-oriented button text
  • Communicate what they get: "Start Free Trial" > "Sign Up"

Core Sections

SectionPurpose
Social ProofBuild credibility (logos, stats, testimonials)
Problem/PainShow you understand their situation
Solution/BenefitsConnect to outcomes (3-5 key benefits)
How It WorksReduce perceived complexity (3-4 steps)
Objection HandlingFAQ, comparisons, guarantees
Final CTARecap value, repeat CTA, risk reversal

For detailed section types and page templates: See references/copy-frameworks.md


CTA Copy Guidelines

Weak CTAs (avoid):

  • Submit, Sign Up, Learn More, Click Here, Get Started

Strong CTAs (use):

  • Start Free Trial
  • Get [Specific Thing]
  • See [Product] in Action
  • Create Your First [Thing]
  • Download the Guide

Formula: [Action Verb] + [What They Get] + [Qualifier if needed]

Examples:

  • "Start My Free Trial"
  • "Get the Complete Checklist"
  • "See Pricing for My Team"

Page-Specific Guidance

Homepage

  • Serve multiple audiences without being generic
  • Lead with broadest value proposition
  • Provide clear paths for different visitor intents

Landing Page

  • Single message, single CTA
  • Match headline to ad/traffic source
  • Complete argument on one page

Pricing Page

  • Help visitors choose the right plan
  • Address "which is right for me?" anxiety
  • Make recommended plan obvious

Feature Page

  • Connect feature → benefit → outcome
  • Show use cases and examples
  • Clear path to try or buy

About Page

  • Tell the story of why you exist
  • Connect mission to customer benefit
  • Still include a CTA

Voice and Tone

Before writing, establish:

Formality level:

  • Casual/conversational
  • Professional but friendly
  • Formal/enterprise

Brand personality:

  • Playful or serious?
  • Bold or understated?
  • Technical or accessible?

Maintain consistency, but adjust intensity:

  • Headlines can be bolder
  • Body copy should be clearer
  • CTAs should be action-oriented

Output Format

When writing copy, provide:

Page Copy

Organized by section:

  • Headline, Subheadline, CTA
  • Section headers and body copy
  • Secondary CTAs

Annotations

For key elements, explain:

  • Why you made this choice
  • What principle it applies

Alternatives

For headlines and CTAs, provide 2-3 options:

  • Option A: [copy] — [rationale]
  • Option B: [copy] — [rationale]

Meta Content (if relevant)

  • Page title (for SEO)
  • Meta description

Related Skills

  • copy-editing: For polishing existing copy (use after your draft)
  • cro: If page structure/strategy needs work, not just copy
  • emails: For email copywriting
  • popups: For popup and modal copy
  • ab-testing: To test copy variations

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ai-seo

무료

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Nexus-JPF/note-companion8722026년 10월 18일 업데이트

analytics

무료

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Nexus-JPF/note-companion8722026년 10월 18일 업데이트

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Nexus-JPF/note-companion8722026년 10월 18일 업데이트

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Nexus-JPF/note-companion8722026년 10월 18일 업데이트

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Nexus-JPF/note-companion8722026년 10월 18일 업데이트

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Nexus-JPF/note-companion8722026년 10월 18일 업데이트

Nexus-JPF의 스킬 모두 보기

이 스킬의 문제 신고