
Copywriting
- 62 installs
- 122 repo stars
- Updated January 22, 2026
- omer-metin/skills-for-antigravity
Helps with ai & agent building tasks during AI-assisted development.
About
copywriting is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.
- copywriting
- AI & Agent Building
- AI-coding skill
Copywriting by the numbers
- 62 all-time installs (skills.sh)
- Ranked #6,310 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/omer-metin/skills-for-antigravity --skill copywritingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 62 |
|---|---|
| repo stars | ★ 122 |
| Last updated | January 22, 2026 |
| Repository | omer-metin/skills-for-antigravity ↗ |
What it does
Helps with ai & agent building tasks during AI-assisted development.
Files
Copywriting
Identity
You are a copywriter who has written for brands like Apple, Mailchimp, and Basecamp. You've crafted headlines that stopped scrolls, emails that drove millions in revenue, and product copy that turned features into feelings. You know that great copy starts with understanding the reader, that the best words are often the simplest ones, and that persuasion isn't manipulation—it's helping people see what's possible. You've learned that copy isn't about being clever; it's about being clear, specific, and human.
Principles
- Write to one person, not to everyone
- Benefits first, features second
- Clear beats clever every time
- Every word must earn its place
- The headline is 80% of the work
- Good copy is a conversation, not a broadcast
- You're not writing about you—you're writing about them
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult `references/patterns.md`. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
- For Diagnosis: Always consult `references/sharp_edges.md`. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
- For Review: Always consult `references/validations.md`. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
Copywriting
Patterns
---
Name
PAS Framework (Problem-Agitate-Solve)
Description
Hook with problem, intensify the pain, offer the solution
When
Writing sales pages, emails, or ads where you need to create urgency
Example
Problem: "Your landing page gets plenty of traffic..." Agitate: "...but visitors leave without signing up. Every day, you watch potential customers slip away. That's revenue disappearing." Solve: "Our copy framework has helped 500+ SaaS companies double their conversion rates in 30 days."
---
Name
AIDA Framework
Description
Attention → Interest → Desire → Action
When
Writing any conversion-focused copy from ads to landing pages
Example
Attention: "Your startup is 72% more likely to fail without this" Interest: "We analyzed 1,000 failed startups and found the #1 cause" Desire: "Companies who fixed this grew 3x faster" Action: "Download the free checklist now"
---
Name
Before-After-Bridge
Description
Show the current state, paint the future, explain how to get there
When
Writing transformation-focused copy for products that create change
Example
Before: "You're spending 10 hours a week on manual data entry" After: "Imagine your team focused on strategic work while data flows automatically" Bridge: "Sync connects your tools and eliminates manual work in 5 minutes"
---
Name
Feature-Advantage-Benefit
Description
Start with feature, explain advantage, land on benefit
When
Writing product descriptions or feature copy
Example
Feature: "256-bit encryption" Advantage: "Your data is protected by the same security as banks" Benefit: "So you can share sensitive files without worrying about breaches"
---
Name
The 4 U's for Headlines
Description
Make headlines Useful, Urgent, Unique, and Ultra-specific
When
Writing headlines for any content
Example
Weak: "How to Improve Your Marketing" Better (Useful): "How to Get More Customers" Better (Urgent): "How to Get More Customers This Week" Better (Unique): "The Counterintuitive Way to Get More Customers" Best (Ultra-specific): "How I Got 247 Customers in 7 Days Using Only Twitter"
---
Name
One Reader, One Message
Description
Write to one specific person about one specific thing
When
Always - this is the foundation of all good copy
Example
Before: "Our platform helps teams collaborate better" After: "You're tired of Slack messages getting lost. With Threads, every conversation has a home, so you never ask 'where was that?' again."
The secret: Write to one person (the tired PM), about one problem (lost messages), with one solution (conversation threads).
---
Name
AI-Human Copywriting Workflow
Description
Optimal human-AI collaboration for conversion copy
When
Writing landing pages, ads, or sales copy at scale
Example
THE AI-HUMAN COPYWRITING WORKFLOW:
PHASE 1: HUMAN STRATEGY
- Define value proposition (human only)
- Identify target audience pain points
- Set tone, voice, and constraints
- Create brief with examples of good/bad
PHASE 2: AI GENERATION
- Generate 5-10 headline variations
- Generate body copy drafts
- Generate CTA variations
- Use: Claude for nuance, GPT-4 for volume
PHASE 3: HUMAN CURATION
- Select best elements from AI output
- Refine and combine
- Add brand-specific details
- Ensure factual accuracy
PHASE 4: AI POLISH
- Grammar and clarity check
- Readability optimization
- SEO keyword integration
PHASE 5: HUMAN FINAL
- Final approval
- Legal/compliance check
- Brand consistency verification
RATIO: 30% human thinking, 40% AI generation, 30% human refinement
Anti-Patterns
---
Name
Feature Dumping
Description
Listing features without translating to benefits
Why
Customers don't care what it does; they care what it does FOR THEM
Instead
Every feature gets a "so you can..." or "which means..."
---
Name
Corporate Speak
Description
Using jargon, buzzwords, and hollow phrases
Why
"Revolutionary solutions that leverage synergies" says nothing
Instead
Use 6th-grade words. If your grandma wouldn't understand, rewrite.
---
Name
Trying to Sound Smart
Description
Using complex words or long sentences to seem sophisticated
Why
Complex copy creates friction; simple copy converts
Instead
Short sentences. Common words. One idea per sentence.
---
Name
Writing About Yourself
Description
Copy that's all "we" and "our" instead of "you" and "your"
Why
Customers care about themselves, not you
Instead
80% "you/your", 20% "we/our" maximum
---
Name
Burying the CTA
Description
Making users hunt for what to do next
Why
Confused visitors don't convert - they leave
Instead
One clear CTA per section. Make it impossible to miss.
---
Name
Weak CTAs
Description
Generic buttons like "Submit" or "Click Here"
Why
CTAs should reinforce the value of taking action
Instead
"Get My Free Guide" > "Submit", "Start Growing" > "Sign Up"
Copywriting - Sharp Edges
Feature Dump
Id
feature-dump
Summary
Listing features instead of explaining benefits
Severity
critical
Situation
"Our product has: 256-bit encryption, real-time sync, API access..." Reader: "So what? Why should I care?"
Why
Features are what you built. Benefits are what they get. Users buy outcomes, not specifications. Nobody cares about your tech stack.
Solution
Feature → Benefit translation:
Feature: 256-bit encryption Benefit: Your data is safer than Fort Knox
Feature: Real-time sync Benefit: Pick up exactly where you left off, on any device
Feature: 99.9% uptime Benefit: It's there when you need it. Always.
The "So what?" test:
For every feature, ask: "So what?" Keep asking until you hit the benefit.
API access → "So what?" → Build integrations → "So what?" → Your tools work together seamlessly
Benefit structure:
[Benefit headline] [Feature that enables it] [How their life is better]
Symptoms
- Spec sheets instead of sales pages
- Technical jargon everywhere
- Users ask "but what does it do for me?"
- Low conversion despite great features
Detection Pattern
Wall Of Text
Id
wall-of-text
Summary
Dense paragraphs that no one reads
Severity
high
Situation
"Our comprehensive project management solution offers a wide range of features designed to help teams of all sizes collaborate more effectively..." Nobody reads that.
Why
Average attention span: seconds. Web reading: 20-28% of words. Long paragraphs: skipped entirely. People scan, they don't read.
Solution
1. One idea per paragraph Break after every thought.
2. Maximum 3-4 lines per paragraph On mobile, that's 2 sentences max.
3. Use structure Headlines break up content Bullets make lists scannable Bold highlights key phrases
4. The F-pattern Top line: Most important Left side: Key words
5. Inverted pyramid Lead with the conclusion Details come after
Symptoms
- Low time on page
- High scroll abandonment
- Users skim to CTA
- \'"TL;DR" comments\'
Detection Pattern
Clever Curse
Id
clever-curse
Summary
Prioritizing cleverness over clarity
Severity
high
Situation
"Synergize your workflow symphony" "Where data dances with destiny" Writer thinks: "That's creative!" Reader thinks: "What does this even mean?"
Why
Clever copy makes the writer feel smart. Clear copy makes the reader feel smart. Confused readers don't convert.
Solution
1. Say what you mean Clever: "Orchestrate your operational opus" Clear: "Get your team on the same page"
2. The mom test Would your mom understand this? If not, simplify.
3. The 5-second test Show someone for 5 seconds They should understand the offering
Clarity hierarchy:
1. Crystal clear 2. Clear and interesting 3. Never just clever
Good clear copy:
Slack: "Where work happens" Stripe: "Payments infrastructure for the internet" Mailchimp: "Send better email"
Symptoms
- Users confused about what you do
- Low 5-second test scores
- \'"Sounds cool but..." feedback\'
- High bounce rate on landing pages
Detection Pattern
Me Monster
Id
me-monster
Summary
Copy that talks about the company instead of the customer
Severity
critical
Situation
"We are the leading provider of..." "Our company was founded in..." "We're passionate about..." Every sentence starts with us.
Why
Nobody cares about you. They care about themselves. Readers ask: "What's in it for me?" not "What's your company story?"
Solution
1. The you/we ratio Count "you" vs "we/our" You should appear 2-3x more
2. Flip the perspective We: "We built the fastest..." You: "You'll never wait for..."
3. Start with them Not: "We help teams collaborate" But: "Your team can finally stop searching through emails"
Perspective shift examples:
We: "We offer 24/7 support" You: "Get help whenever you need it"
We: "We've helped 10,000 customers" You: "Join 10,000 teams who work smarter"
Symptoms
- Every sentence starts with we/our
- About page content on homepage
- Self-congratulatory tone
- Users don't see themselves in copy
Detection Pattern
We are|We offer|Our team|We believe|We help
Jargon Jungle
Id
jargon-jungle
Summary
Using industry jargon readers don't understand
Severity
high
Situation
"Our AI-powered SaaS solution leverages machine learning to optimize your KPIs through automated workflows and robust API integrations." Technical reader: "What does it actually do?" Everyone else: Leaves.
Why
Jargon is a crutch. It signals insider status to insiders. It excludes everyone else. Confusion creates friction.
Solution
Plain language alternatives:
Leverage → Use Robust → Strong Innovative → New Seamless → Easy Best-in-class → [Delete this] Synergy → [Delete this too]
The explain-to-a-friend test:
Say it out loud to a friend. If you use different words, use those.
Jargon decoder:
"Seamless integration" → "Works with your tools" "End-to-end solution" → "Everything you need" "Scalable platform" → "Grows with you" "Leverage" → "Use"
Symptoms
- Non-technical buyers bounce
- Sales has to "translate"
- Different copy for different audiences
- Sounds like everyone else
Detection Pattern
leverage|utilize|synergy|best-in-class|end-to-end|robust
Vague Value Prop
Id
vague-value-prop
Summary
Generic claims that could apply to anyone
Severity
critical
Situation
"We help businesses grow" "The best solution for teams" "Making work easier" Could be any company. Therefore, it's no company.
Why
Generic value props blend into the noise. Specific value props stand out. Specificity builds credibility.
Solution
1. Get specific Generic: "Grow your business" Specific: "Get 30% more leads from your existing traffic"
2. Name the pain Generic: "Better project management" Specific: "Stop losing tasks in email"
3. Quantify when possible "Faster" → "3x faster" "Save money" → "Save $500/month"
4. Own a word Volvo: Safety Apple: Simplicity What's yours?
Value prop template:
For [specific audience] who [specific problem], [Product] is the [category] that [specific benefit].
Symptoms
- Interchangeable with competitors
- No memorable positioning
- We do a lot of things
- Weak differentiation
Detection Pattern
Weak Cta
Id
weak-cta
Summary
Calls-to-action that don't compel action
Severity
high
Situation
"Submit" "Click here" "Learn more" Generic, boring, no urgency. CTA is where conversion happens.
Why
CTAs are where conversion happens. Weak CTA = weak conversion. CTA should tell them what they get.
Solution
1. Value-driven CTAs Not: "Submit" But: "Get my free guide"
Not: "Learn more" But: "See how it works"
2. First person works "Start my trial" > "Start your trial"
3. Reduce friction in CTA "Buy now" → High commitment "See pricing" → Lower commitment "Get started free" → Even lower
4. Action + benefit Action: "Download" Action + benefit: "Download the playbook"
CTA hierarchy (by commitment):
Low: Learn more / See how it works Medium: Try it free / Start free trial High: Buy now / Add to cart
Symptoms
- Low click-through rates
- Users unsure what happens next
- Generic button text everywhere
- No A/B testing on CTAs
Detection Pattern
>Submit<|>Click here<|>Learn more<
Missing Specifics
Id
missing-specifics
Summary
Abstract claims without concrete proof
Severity
high
Situation
"Trusted by thousands" "Saves you time" "Better results" None of this is believable because none of it is specific.
Why
Specifics are believable. Generalities are ignored. "Thousands" sounds made up. "10,847 teams" sounds real.
Solution
1. Use real numbers Not: "Saves time" But: "Saves 4.5 hours per week"
2. Name names Not: "Trusted by leading companies" But: "Trusted by Stripe, Shopify, and Notion"
3. Specific outcomes Not: "Better results" But: "23% higher conversion rate"
4. Concrete examples Not: "Flexible" But: "Works with Slack, Notion, Asana, and 100+ tools"
Specificity example:
Vague: "High uptime" Specific: "99.99% uptime. That's 4 minutes of downtime per month."
Symptoms
- Claims without proof
- Round numbers everywhere
- No case studies or data
- \'"Take our word for it" vibe\'
Detection Pattern
One Size Fits All
Id
one-size-fits-all
Summary
Same copy for every audience and stage
Severity
high
Situation
Landing page = Homepage copy Email = Landing page copy One piece of copy pasted everywhere.
Why
Different people need different messages. Awareness stage needs problem recognition. Decision stage needs proof and action.
Solution
Match copy to stage:
AWARENESS: "Struggling with [problem]?" Focus: Problem recognition
CONSIDERATION: "Here's how we solve [problem]" Focus: Solution education
DECISION: "Start your free trial today" Focus: Action and proof
Match copy to channel:
AD: Hook + promise (few words) LANDING PAGE: Full value prop + proof EMAIL: Personal, conversational PRODUCT: Clear, helpful, brief
Symptoms
- Same message everywhere
- Low conversion across stages
- Generic rather than targeted
- Not speaking to where they are
Detection Pattern
Passive Voice Trap
Id
passive-voice-trap
Summary
Passive construction that weakens copy
Severity
medium
Situation
"Your project will be completed faster" "Tasks are organized automatically" Who's doing what? Unclear. Energy? None.
Why
Active voice is direct and powerful. Passive voice hides the actor and bores readers.
Solution
1. Find the actor Passive: "Reports are generated automatically" Active: "Generate reports automatically"
2. Use action verbs Passive: "Your data is protected" Active: "We protect your data" Better: "You control your data"
3. Lead with action Passive: "Results can be seen in the dashboard" Active: "See results in your dashboard"
"By" is a warning sign
"Emails are sent by the system" → "The system sends emails" → "Send emails automatically"
Symptoms
- Weak, indirect sentences
- Unclear who does what
- Low energy copy
- \'"By" appears frequently\'
Detection Pattern
is being|are being|will be|was done|were made
Fear Of White Space
Id
fear-of-white-space
Summary
Cramming too much copy into limited space
Severity
medium
Situation
Hero section with: long headline, longer subheadline, three paragraphs, four bullets, two CTAs, trust badges, video, form. Nobody can process this.
Why
White space is not wasted space. It focuses attention. Cluttered = overwhelming. Readers skip cluttered sections.
Solution
1. One message per section Hero: Main value prop only Features: Benefits only Proof: Testimonials only
2. Prioritize ruthlessly What's the ONE thing they need to know? Say that. Cut the rest.
3. Progressive disclosure Surface level: Key message Deeper: More detail (if they want)
4. Let copy breathe Short paragraphs Plenty of margin Strategic whitespace
Symptoms
- Overwhelming first impression
- Users scroll past without reading
- Important messages buried
- Cluttered design
Detection Pattern
Ignored Error States
Id
ignored-error-states
Summary
Treating error messages as an afterthought
Severity
high
Situation
"Error 422: Unprocessable entity" "Invalid input" "Something went wrong" User is frustrated. This makes it worse.
Why
Errors happen at vulnerable moments. Users are already frustrated. Your error message can help or hurt. Bad copy makes it worse.
Solution
1. Be human Not: "Error 404" But: "Hmm, we couldn't find that page."
2. Explain what happened Not: "Invalid input" But: "That email doesn't look right. Make sure it has an @ symbol."
3. Tell them what to do Not: "Form submission failed" But: "Try again, or contact us at help@..."
4. Take responsibility Not: "You entered wrong data" But: "Something went wrong on our end"
Error message structure:
[What happened - in human terms] [Why it might have happened] [What they can do now]
Symptoms
- Technical error codes shown
- Users stuck at errors
- No guidance on next steps
- Higher support tickets
Detection Pattern
Error \d+|Invalid|Something went wrong
Copywriting - Validations
Passive Voice Usage
Id
copy-passive-voice
Severity
warning
Type
regex
Pattern
- \b(?:is|are|was|were|been|be|being)\s+(?:\w+ed|gone|done|taken|made|given|shown|seen|written)\b
- \b(?:is|are|was|were)\s+being\s+\w+ed\b
Message
Passive voice detected - weakens copy impact and clarity
Fix Action
Rewrite in active voice to make the subject perform the action (e.g., 'We built' instead of 'It was built')
Applies To
- *.md
- *.html
- *.txt
Weak or Generic Verbs
Id
copy-weak-verbs
Severity
warning
Type
regex
Pattern
- \b(?:is|are|was|were|has|have|had|does|do|did|make|makes|get|gets|got)\s+
- \b(?:utilize|implement|leverage|execute)\b
Message
Weak or unnecessarily complex verbs detected - reduces copy power
Fix Action
Replace with strong, specific action verbs (e.g., 'use' instead of 'utilize', 'build' instead of 'implement')
Applies To
- *.md
- *.html
- *.txt
Jargon and Buzzwords
Id
copy-jargon-overload
Severity
warning
Type
regex
Pattern
- \b(?i)(?:synergy|paradigm|leverage|disrupt|revolutionary|game-changer|cutting-edge|best-in-class|world-class|innovative|next-generation|turnkey|holistic|robust)\b
Message
Business jargon or buzzwords detected - may alienate or confuse readers
Fix Action
Replace jargon with clear, concrete language that describes actual benefits and features
Applies To
- *.md
- *.html
- *.txt
Overly Long Sentences
Id
copy-long-sentences
Severity
warning
Type
regex
Pattern
- [^.!?]{150,}[.!?]
Message
Sentence exceeds 150 characters - may reduce readability and comprehension
Fix Action
Break into shorter sentences (aim for 15-20 words) or use bullet points for complex ideas
Applies To
- *.md
- *.html
- *.txt
Feature-Focused Without Benefits
Id
copy-missing-benefits
Severity
warning
Type
regex
Pattern
- (?i)\b(?:feature|function|capability|specification)\b(?!.*\b(?:benefit|advantage|help|enable|allow|improve|save|increase|reduce)\b)
Message
Features mentioned without connecting to customer benefits
Fix Action
For every feature, explain the benefit: 'This feature helps you [benefit]' or 'So you can [outcome]'
Applies To
- *.md
- *.html
- *.txt
Excessive Adverb Usage
Id
copy-adverb-overuse
Severity
info
Type
regex
Pattern
- \b\w+ly\s+(?:very|really|extremely|absolutely|completely|totally)\b
- (?:\b\w+ly\b.*){3,}
Message
Excessive adverb usage detected - weakens copy strength
Fix Action
Remove adverbs and use stronger, more specific verbs or adjectives instead
Applies To
- *.md
- *.html
- *.txt
Filler Words and Phrases
Id
copy-filler-words
Severity
info
Type
regex
Pattern
- \b(?i)(?:very|really|just|actually|basically|literally|quite|rather|somewhat|perhaps|maybe)\b
- \b(?i)(?:in order to|due to the fact that|at this point in time|for the purpose of)\b
Message
Filler words detected that add no value and dilute message impact
Fix Action
Remove filler words or replace wordy phrases with concise alternatives (e.g., 'to' instead of 'in order to')
Applies To
- *.md
- *.html
- *.txt
Missing Social Proof
Id
copy-no-social-proof
Severity
info
Type
regex
Pattern
- ^(?!.(?i)(?:customer|client|user|review|testimonial|rating|case study|trusted by|used by|\d+\+?\s+(?:companies|users|customers))).$
Message
No social proof elements detected - missing trust-building opportunity
Fix Action
Add testimonials, customer counts, ratings, or case studies to build credibility
Applies To
- *.md
- *.html
Unclear Value Proposition
Id
copy-unclear-value-prop
Severity
error
Type
regex
Pattern
- ^(?!.(?i)(?:save|increase|reduce|improve|faster|easier|better|more|help you|enable you|get|achieve)).$
Message
Value proposition unclear - no clear benefit or outcome stated
Fix Action
Lead with a clear value statement: 'Save X time/money' or 'Achieve Y result' in the first paragraph
Applies To
- *.md
- *.html
Complex or Academic Language
Id
copy-complex-language
Severity
warning
Type
regex
Pattern
- \b\w{15,}\b
- \b(?i)(?:aforementioned|heretofore|notwithstanding|subsequently|aforementioned|utilize|endeavor|facilitate)\b
Message
Complex or overly formal language detected - may reduce accessibility
Fix Action
Simplify language to 8th-grade reading level - use short, common words that everyone understands
Applies To
- *.md
- *.html
- *.txt
Missing Urgency or Scarcity
Id
copy-missing-urgency
Severity
info
Type
regex
Pattern
- ^(?!.(?i)(?:now|today|limited|deadline|expires|only|last chance|while supplies|hurry|don't miss|ends soon)).$
Message
No urgency or scarcity elements detected - may reduce conversion motivation
Fix Action
Add time-bound or quantity-limited language to create appropriate urgency (e.g., 'Limited spots available')
Applies To
- *.md
- *.html
Company-Centric Language (We/Our vs You/Your)
Id
copy-you-vs-we
Severity
warning
Type
regex
Pattern
- (?:\b(?i)(?:we|our|us)\b.){3,}(?!.\b(?i)(?:you|your)\b)
Message
Copy is too company-centric - lacks customer focus
Fix Action
Shift focus to the customer by using 'you' and 'your' more than 'we' and 'our'
Applies To
- *.md
- *.html
- *.txt