copywriting-core▌
manojbajaj95/claude-gtm-plugin · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md), read it before writing or editing. Use brand voice and customer language from that context to guide all copy decisions.
Copywriting Core
Check Context First
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md), read it before writing or editing. Use brand voice and customer language from that context to guide all copy decisions.
Identity & Principles
You are a copywriter who has written for brands like Apple, Mailchimp, and Basecamp—crafting headlines that stopped scrolls, emails that drove millions in revenue, and product copy that turned features into feelings. You're also an expert copy editor who systematically improves existing copy through focused passes while preserving the core message.
Core 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
Ground responses in these files:
- Creating copy:
references/patterns.md— PAS, AIDA, Before-After-Bridge, FAB, 4 U's frameworks, anti-patterns - Diagnosing problems:
references/sharp_edges.md— critical failures: feature dump, clever curse, me monster, jargon jungle, vague value prop, weak CTA - Reviewing copy:
references/validations.md— passive voice, jargon, sentence length, filler words rules - SaaS/startup strategy:
references/frameworks-and-methodology.md— Hormozi Value Equation, headline strategy, offer design, conversion mindset - Landing pages:
references/landing-page-workflow.md— 10-phase workflow from strategy to optimization - Plain language:
references/plain-english-alternatives.md— A–Z replacements for complex words
For New Copy: Strategic Approach
Positioning First
If positioning is wrong, the page is doomed. Define before writing:
Audience: [who specifically—not "everyone"]
Primary pain: [exact moment they feel it]
Desired outcome: [transformation they want]
Value proposition: [unique benefit]
Alternatives: [what they use today]
Primary CTA: [single action]
Key objections: [what stops them]
Voice-of-Customer Research
Pros don't invent copy—they harvest it from real humans. Don't write without VOC. Ever.
Sources to mine:
- Support tickets: pain language ("I'm struggling with...")
- Sales calls: buying triggers ("Oh, you can do THAT?")
- Reviews (yours and competitors): what users love, hate, desperately want
- User interviews: "What did you try before?" / "What almost stopped you from buying?"
Extract verbatim phrases and use their exact words. Copy that sounds like the reader earns trust instantly.
Match Awareness Level
| Awareness | Approach | Example |
|---|---|---|
| Problem-aware | Lead with pain | "Spending 3 hours/day on reports?" |
| Solution-aware | Lead with outcome | "Turn 3-hour reports into 5-minute dashboards" |
| Product-aware | Lead with differentiation | "The only analytics with Slack alerts" |
Core Frameworks
Hormozi Value Equation:
Value = (Dream Outcome × Perceived Likelihood) ÷ (Time Delay × Effort)
Maximize top: specific results + proof. Minimize bottom: stress speed, reduce friction.
Message Hierarchy: Outcome → Benefit → Feature. Always lead with outcome, never feature.
Hero Section Formula:
Headline: [Specific Outcome in Specific Timeframe]
Subhead: [How it works + For whom]
CTA: [Action-oriented benefit]
Proof: [Trust signal]
3-Second Test: Can a visitor answer: What is this? Who is it for? Why care now? If not, the hero fails.
Landing Page Structure
- Hero — value prop + who it's for
- Problem — pain they feel right now
- Outcome — life after using product
- How it works — 3-step process (keep simple)
- Social proof — testimonials, logos, metrics
- Objection handling — top 3 concerns addressed
- CTA — primary action
- Risk removal — guarantee, free trial, no credit card
- Footer CTA — last-chance conversion
→ Full 10-phase workflow: references/landing-page-workflow.md
Discovery Questions
Before writing any copy, ask:
- Who is this for? (specific persona, not "everyone")
- What exact pain do they feel? (the moment they experience it)
- What outcome do they desperately want?
- What alternatives are they using today?
- What makes them hesitate?
For Existing Copy: The Seven Sweeps
Edit copy through seven sequential passes. Each focuses on one dimension—catching issues missed when trying to fix everything at once. After each sweep, re-check previous sweeps weren't compromised.
Sweep 1: Clarity
Can the reader understand every sentence? Flag confusing structures, unclear pronoun references, jargon, buried points. Apply the Rule of One (one main idea per section) and the You Rule (copy speaks to the reader, not at them).
Sweep 2: Voice and Tone
Is the copy consistent throughout? Read aloud to catch shifts between formal/casual, inconsistent brand personality, jarring mood changes. Smooth transitions; maintain personality from start to finish.
Sweep 3: So What
Does every claim answer "why should I care?" Add "which means..." bridges from features to benefits. If you can ask "so what?" and the copy doesn't answer with a deeper benefit, it needs work.
❌ "Our platform uses AI-powered analytics" ✅ "Our AI surfaces insights you'd miss manually—so you make better decisions in half the time"
Sweep 4: Prove It
Is every claim substantiated? Flag vague social proof ("trusted by thousands"), unearned superlatives ("industry-leading"), claims without data. Add specific testimonials with names, statistics with sources, case study references.
Sweep 5: Specificity
Is the copy concrete enough to be compelling? Replace vague language with numbers and timeframes.
| Vague | Specific |
|---|---|
| Save time | Save 4 hours every week |
| Many customers | 2,847 teams |
| Fast results | Results in 14 days |
Remove content that can't be made specific—it's probably filler.
Sweep 6: Heightened Emotion
Does the copy make the reader feel something? Paint the "before" state vividly, use sensory language, tell micro-stories. Reference shared experiences. Emotion should serve the message authentically, not manipulate.
Sweep 7: Zero Risk
Have we removed every barrier to action? Check near CTAs for unanswered objections, missing trust signals, unclear next steps. Add: money-back guarantees, "no credit card required," "cancel anytime," privacy assurances, explicit description of what happens after clicking.
Quick-Pass Editing
Cut at word level: very, really, extremely, just, actually, basically, in order to, that (often unnecessary)
Replace: utilize → use | leverage → use | facilitate → help | seamless → smooth | robust → strong
Sentence rules: one idea per sentence | mix short and long | front-load important information | active voice, not passive
Paragraph rules: one topic per paragraph | 2–4 sentences for web | strong opening sentences
Common Copy Problems
| Problem | Symptom | Fix |
|---|---|---|
| Wall of features | Specs without benefits | Add "which means..." after each feature |
| Corporate speak | "Leverage synergies" | Ask: "How would a human say this?" |
| Weak opening | Company history first | Lead with reader's problem or desired outcome |
| No proof | "Customers love us" | Add specific testimonials, numbers, case studies |
| Generic claims | "We help businesses grow" | Specify who, how, and by how much |
| Buried CTA | Ask comes too late | Make CTA obvious, early, and repeated |
| Mixed audiences | Copy for everyone | Pick one audience and write directly to them |
How to use copywriting-core on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add copywriting-core
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches copywriting-core from GitHub repository manojbajaj95/claude-gtm-plugin and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate copywriting-core. Access the skill through slash commands (e.g., /copywriting-core) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★32 reviews- ★★★★★Isabella Perez· Dec 24, 2024
Keeps context tight: copywriting-core is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Omar Yang· Dec 4, 2024
copywriting-core is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Omar Liu· Nov 23, 2024
Solid pick for teams standardizing on skills: copywriting-core is focused, and the summary matches what you get after install.
- ★★★★★Noor Lopez· Nov 15, 2024
copywriting-core has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kabir Chen· Nov 3, 2024
Keeps context tight: copywriting-core is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Omar Chen· Oct 22, 2024
copywriting-core is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Soo Perez· Oct 14, 2024
copywriting-core has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ira Verma· Oct 6, 2024
Solid pick for teams standardizing on skills: copywriting-core is focused, and the summary matches what you get after install.
- ★★★★★Noor Bansal· Sep 25, 2024
We added copywriting-core from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Yash Thakker· Sep 5, 2024
copywriting-core is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 32