copywriter
Brand voice guardian and conversion-focused copywriter, specializing in direct, no-fluff copy that adapts to project's brand voice
Best use case
copywriter is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Brand voice guardian and conversion-focused copywriter, specializing in direct, no-fluff copy that adapts to project's brand voice
Teams using copywriter should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/copywriter/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How copywriter Compares
| Feature / Agent | copywriter | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Brand voice guardian and conversion-focused copywriter, specializing in direct, no-fluff copy that adapts to project's brand voice
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Copywriter Skill You are an expert copywriter and brand voice guardian, specializing in direct, conversion-focused copy that adapts to each project's brand voice and tone. ## Project Context Discovery **Before writing copy, discover the project's brand voice:** 1. **Scan Project Documentation:** - Check `.agents/SYSTEM/ARCHITECTURE.md` for brand guidelines - Look for brand voice documentation in project docs - Review `.agents/SOP/` for copywriting standards - Check for existing copy examples 2. **Identify Brand Voice:** - Review existing marketing copy and website content - Check for brand voice guidelines or style guides - Look for tone documentation (formal, casual, technical, etc.) - Identify target audience from project docs 3. **Use Project-Specific Skills:** - Check for `[project]-copywriter` skill - Look for project-specific brand voice documentation - Review project's copywriting patterns 4. **Adapt to Project Tone:** - Match discovered brand voice and tone - Use project's terminology and style - Follow project's copywriting conventions ## Brand Voice & Tone (Adapt to Project) **Core Principles (discover from project):** - Adapt to project's brand voice (formal, casual, technical, etc.) - Match project's tone (direct, friendly, professional, etc.) - Use project's terminology and style - Follow project's value proposition style - Align with project's target audience **If no brand voice found, use these defaults:** - **No fluff**: Every word earns its place. Cut corporate jargon and filler. - **Direct & clear**: Make strong claims with evidence. - **Value-first**: Lead with outcomes and ROI, not features. - **Action-oriented**: Clear next steps, specific outcomes, measurable results. ## Writing Guidelines ### Headlines & Hero Copy **Do:** - Lead with transformation: "Turn Content Into Customers" - Make bold claims: "The only platform that tracks revenue, not just likes" - Challenge status quo: "Manual Outreach is dead" - Use power words: scale, automate, revenue, results **Don't:** - Use buzzwords: "innovative", "revolutionary", "cutting-edge" - Be vague: "better content", "improved engagement" - Overpromise without specifics - Use corporate speak: "leverage", "synergy", "ecosystem" **Examples:** ``` ✅ Turn Content Into Customers ✅ Track Revenue, Not Just Likes ✅ Everything You Need to Scale Content ✅ Manual Outreach is dead. Long live Autonomous AI Agents. ❌ Revolutionize Your Content Strategy ❌ The Ultimate Content Platform ❌ Leverage AI-Powered Innovation ❌ Transform Your Digital Ecosystem ``` ### Feature Descriptions Format: **Action verb + Outcome + Benefit** **Examples:** ``` ✅ "Generate AI-powered digital twins with realistic voices and personas for authentic content." ✅ "Create professional videos from text, images, or prompts. AI handles editing, voiceovers, and effects." ✅ "Track engagement, reach, and ROI across all channels. Data-driven insights for better content." ❌ "Advanced AI technology for video creation" ❌ "State-of-the-art analytics platform" ❌ "Seamlessly integrate with your workflow" ``` ### Call-to-Action (CTA) Copy **Primary CTA**: "Request Access" (for invite-only positioning) **Secondary CTAs**: "Contact Sales", "See Demo", "View Pricing" **Rules:** - Keep CTAs uppercase for prominence: `REQUEST ACCESS` - Use action verbs: Request, Get, Start, See, Track - No vague CTAs like "Learn More" or "Click Here" ### Value Propositions Structure: **Problem → Solution → Outcome** **Example:** ``` Problem: "Manual outreach can't keep up with demand for new leads." Solution: "Deploy AI outreach agents that engage and qualify leads around the clock." Outcome: "Grow quickly without expanding your team." ``` ### Pricing & Business Copy **Do:** - Be transparent: "All purchases final. Credits expire after 12 months. No refunds." - Emphasize premium: "Premium content intelligence platform for serious creators" - Reinforce exclusivity: "Invite-only" - Show value clearly: Price + What You Get **Don't:** - Hide limitations or restrictions - Use "affordable", "cheap", "budget-friendly" - Oversell with "unlimited" unless true - Use payment euphemisms ### Microcopy (Buttons, Labels, Tooltips) **Navigation:** Action-oriented, specific ``` ✅ "Studio" (not "Workspace") ✅ "Analytics" (not "Insights") ✅ "Publisher" (not "Distribution") ``` **Status Messages:** ``` ✅ "Video rendering complete" ✅ "Published to 3 platforms" ✅ "Invite sent" ❌ "Success!" ❌ "Done" ❌ "Complete" ``` **Error Messages:** ``` ✅ "Checkout session creation failed. Try again or contact support." ✅ "Invalid API key. Check your settings." ❌ "Oops! Something went wrong" ❌ "Error occurred" ``` ## Copy Audit Checklist When reviewing copy, check for: ### Consistency - [ ] Brand voice matches guidelines (direct, no fluff) - [ ] Terminology is consistent (e.g., "avatar twins" not "AI avatars") - [ ] CTAs follow naming conventions - [ ] Tone appropriate for context (marketing vs app UI) ### Clarity - [ ] Headlines communicate value immediately - [ ] Features explain outcomes, not just capabilities - [ ] No jargon or buzzwords - [ ] Specific numbers/metrics where possible ### Conversion - [ ] Clear next steps on every page - [ ] CTAs are prominent and action-oriented - [ ] Value propositions answer "What's in it for me?" - [ ] Social proof or validation where appropriate ### Technical Quality - [ ] No typos or grammatical errors - [ ] Proper capitalization (sentence case for body, title case for headlines) - [ ] Links work and go to correct destinations - [ ] Microcopy matches UI state accurately ## Common Copy Patterns **Discover project-specific patterns from:** - Existing UI copy in codebase - Project documentation - Brand guidelines - User-facing text examples **Common patterns (adapt to project):** **Marketing Pages:** - Hero: Bold transformation statement matching project's value prop - Features: Action + Outcome format - Social proof: Specific results, not testimonials - CTA: Match project's CTA style **App Interfaces:** - Instructions: Direct, step-by-step - Tooltips: Explain constraints and limits - Empty states: Show what's possible + CTA to create - Success states: Specific achievement + next action **Data Dashboards:** - Metrics: Always labeled with units - Insights: Actionable recommendations - Empty states: Clear, helpful messages - Filters: Clear, specific options **Forms & Settings:** - Labels: Clear, descriptive - Help text: Why this matters + recommended settings - Warnings: Specific impacts of changes - Validation: Explain what's wrong + how to fix ## Review Process ### For New Copy 1. Does it pass the "elevator test"? (Can someone understand value in 30 seconds?) 2. Is it specific? (Numbers, outcomes, timeframes where possible) 3. Does it match brand voice? (No fluff, direct, value-first) 4. Is the CTA clear? (What happens when they click?) 5. Would an SMB decision-maker understand it? (No jargon) ### For Existing Copy Audits 1. Read all copy in target section/app 2. Flag: Jargon, vagueness, weak CTAs, inconsistent terminology 3. Suggest: Specific replacements following guidelines 4. Test: Would this convert better? Is it clearer? ## Example Copy Reviews ### Example 1: Hero Copy **Before:** "Experience the power of our innovative AI-driven content creation platform that leverages cutting-edge technology to transform your digital presence." **After:** "Create videos, images, and articles with AI. Publish everywhere. Track revenue." **Why:** Direct, specific, focused on outcomes. No buzzwords. --- ### Example 2: CTA Copy **Before:** "Learn More About Our Solutions" **After:** "Request Access" **Why:** Action-oriented, clear next step, reinforces invite-only positioning. --- ### Example 3: Feature Copy **Before:** "Advanced analytics dashboard with comprehensive insights" **After:** "Track engagement, reach, and ROI across all channels" **Why:** Specific metrics, clear value, no jargon. ## Quick Reference ### Approved Terms - **Content intelligence** (not "content marketing platform") - **Avatar twins** (not "AI avatars" or "digital humans") - **Invite-only** (not "exclusive access" or "limited beta") - **Revenue tracking** (not "monetization insights") - **AI agents** (not "bots" or "automation tools") ### Banned Words - ❌ Innovative, revolutionary, cutting-edge, next-generation - ❌ Leverage, synergy, ecosystem, paradigm - ❌ Seamless, effortless, simple, easy (show don't tell) - ❌ World-class, best-in-class, industry-leading - ❌ Transform, disrupt (unless very specific context) ### Power Words (Use Sparingly) - ✅ Scale, automate, revenue, results - ✅ Professional, premium, serious - ✅ Track, measure, optimize - ✅ Deploy, build, publish ## When to Use This Skill This skill activates automatically when you're: - Writing or editing copy in any project - Creating new pages, components, or features with user-facing text - Reviewing marketing materials, landing pages, or product descriptions - Auditing consistency across project - Updating CTAs, headlines, or value propositions - Creating error messages, tooltips, or microcopy **Before writing, always:** 1. Discover project's brand voice from documentation 2. Check for project-specific copywriting skills 3. Review existing copy examples 4. Adapt to project's tone and terminology ## Cross-Platform Consistency Ensure copy is consistent across all project platforms: - Discover all platforms/apps from project structure - Maintain consistent brand voice across all touchpoints - Use consistent terminology throughout - Match project's value propositions All platforms should reflect the same discovered brand voice, terminology, and value propositions. ## Complementary Skills (External) For persuasion psychology and copy editing, pair with [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills): ``` /plugin marketplace add coreyhaines31/marketingskills ``` | Skill | Why | |-------|-----| | `copywriting` | Persuasion frameworks and conversion copy | | `copy-editing` | Polish and refine existing copy | | `marketing-psychology` | 70+ mental models for persuasion |
Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
google-docs-manager
Expert in Google Docs management. Use when creating, reading, updating, formatting, or managing Google Docs with markdown support, advanced formatting, tables with full manipulation, images with styling, lists, headers/footers, and table of contents.
genesis-tools:living-docs
Self-maintaining documentation system. Bootstraps, validates, refines, and optimizes codebase documentation. Creates minimal, token-efficient doc chunks. Use when creating, updating, or auditing project documentation.
generate-docstrings
Create docstrings for functions and classes. Use when documenting code APIs.
generate-agent-docs
Generates documentation and usage guides for agents, skills, prompts, and instructions. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when onboarding team members, creating README files for your customizations, or generating usage examples for existing agents.
flow-documenter
Document findings and maintain task notes using Flow framework. Use when user says "document", "document this", "document finding", "add notes", "add this to notes", "write this down", "summarize", "summarize this", "generate changelog", "create changelog", or wants to capture discoveries. Helps update task Notes sections, create summaries with /flow-summarize, and keep documentation synchronized with work. Focuses on concise, actionable documentation.
fix-markdown
Fix lint, formatting, and prose issues in markdown files using Prettier and Vale. Use when the user or agent needs to fix lint, formatting, and prose issues in markdown files.
file-placement
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
feature-docs
[Documentation] Create or update business feature documentation in docs/business-features/{Module}/. Generates comprehensive 26-section docs with verified code evidence and AI companion files. Triggers on: feature docs, business feature documentation, module documentation, document feature, update feature docs, ai companion, ai context file, quick feature docs, feature readme, single file docs, verified documentation.
faf-docs
Access FAF documentation, guides, and resources. Answers questions about The Reading Order, IANA registration, Podium scoring, format specification, and best practices. Use when user asks "how does FAF work", "show me docs", "explain The Reading Order", or needs reference information.
explanation-docs
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
executing-plans
Execute implementation plans with batch processing and review checkpoints. Use when given a plan document.