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," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
- License 许可
- MIT
- 最近更新
- 2026-08-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- copywriting
- license
- MIT
- metadata
- { "author": "Alireza Rezvani", "updated": 1772755200000, "version": "1.0.0", "category": "marketing" }
- description
- 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," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
02 资源文件 3
- 参考文档references/copy-frameworks.md7.3 KB
- 参考文档references/natural-transitions.md5.1 KB
- 脚本scripts/headline_scorer.py9.1 KB
03 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 .claude/product-marketing-context.md exists, 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
- Simple over complex — "Use" not "utilize," "help" not "facilitate"
- Specific over vague — Avoid "streamline," "optimize," "innovative"
- Active over passive — "We generate reports" not "Reports are generated"
- Confident over qualified — Remove "almost," "very," "really"
- Show over tell — Describe the outcome instead of using adverbs
- Honest over sensational — Never fabricate statistics or testimonials
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}"
Score every headline candidate with the bundled scorer before picking one:
python3 scripts/headline_scorer.py "Ship dashboards in minutes, not sprints"
python3 scripts/headline_scorer.py --file headlines.txt --json # batch-score a list
It rates 0-100 across 6 dimensions (length, specificity, power words, clarity, emotional pull, format). Write 5-10 candidates, score them all, present the top 2-3 with their scores and dimension breakdowns — never present a sub-60 headline as the primary recommendation.
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
| Section | Purpose |
|---|---|
| Social Proof | Build credibility (logos, stats, testimonials) |
| Problem/Pain | Show you understand their situation |
| Solution/Benefits | Connect to outcomes (3-5 key benefits) |
| How It Works | Reduce perceived complexity (3-4 steps) |
| Objection Handling | FAQ, comparisons, guarantees |
| Final CTA | Recap 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
Proactive Triggers
Surface these issues WITHOUT being asked when you notice them in context:
- Copy opens with "We" or the company name → Flag it immediately; reframe to lead with the customer's outcome or problem.
- Value proposition is vague (e.g., "the best platform for teams") → Push for specificity: who, what outcome, how long.
- Features are listed without benefits → Add "which means..." bridges before delivering the draft.
- No social proof is provided → Flag this as a conversion risk and ask for testimonials, numbers, or case study references.
- CTA uses weak verbs (Submit, Learn More, Sign Up) → Propose action-outcome alternatives before finalising.
Output Artifacts
| When you ask for... | You get... |
|---|---|
| Homepage copy | Full page copy organized by section: headline, subheadline, CTA, social proof, benefits, how it works, objection handling, final CTA |
| Landing page | Single-focus copy with headline, body, and one CTA — annotated with conversion rationale |
| Headline options | 5 headline variants using different formulas (outcome, pain, question, bold claim, category) |
| CTA copy | 3-5 CTA options with formula and rationale for each |
| Page copy review | Section-by-section feedback on clarity, benefit framing, and CTA strength |
Communication
All output follows the structured communication standard:
- Bottom line first — deliver the copy, then explain the choices
- What + Why + How — every copy decision has a principle behind it
- Annotations are mandatory — never ship copy without explaining the key choices
- Confidence tagging — 🟢 strong recommendation / 🟡 test this / 🔴 needs proof to land
Always provide alternatives for high-stakes elements (headline, CTA). Never deliver one option and call it done.
Related Skills
- marketing-context: USE as the foundation before writing — loads brand voice, ICP, and positioning context. NOT a substitute for this skill.
- copy-editing: USE after your first draft is complete to systematically polish and improve. NOT for writing new copy from scratch.
- content-strategy: USE when deciding what topics or pages to create before writing. NOT for the writing itself.
- social-content: USE when adapting finished copy for social platforms. NOT for long-form page copy.
- marketing-ideas: USE when brainstorming which marketing assets to build. NOT for writing the copy for those assets.
- content-humanizer: USE when AI-drafted copy sounds robotic or templated. NOT for strategic decisions.
- ab-test-setup: USE to design experiments testing copy variants. NOT for writing the copy itself.
- email-sequence: USE for email copywriting specifically. NOT for page or landing page copy.
04 同仓库更多 Skills
syllabus
Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.
research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research, deepread for evidence-first reading of supplied documents) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.
pulse
Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.
patent
Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
notebooklm
Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.
litreview
Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed/OpenAlex (or Consensus) query.